From: Ansgar Burchardt Date: Mon, 17 Jun 2013 18:17:53 +0000 (+0200) Subject: new-security-install: run process-policy after we acquired the lock X-Git-Url: https://err.no/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=e81babf3fc6237e9cc032f9c29d3b6ac1cfe060a;p=dak new-security-install: run process-policy after we acquired the lock We don't want cron.unchecked to do anything while we run process-policy. Especially not running another process-policy process or moving files out of queue/accepted/ while we are installing files there. --- diff --git a/dak/new_security_install.py b/dak/new_security_install.py index 251f34fe..aa2928db 100755 --- a/dak/new_security_install.py +++ b/dak/new_security_install.py @@ -86,10 +86,6 @@ def sudo(arg, fn, exit): def do_Approve(): sudo("A", _do_Approve, True) def _do_Approve(): - # 1. use process-policy to go through the COMMENTS dir - spawn("dak process-policy embargoed") - spawn("dak process-policy unembargoed") - print "Locking unchecked" lockfile='/srv/security-master.debian.org/lock/unchecked.lock' spawn("lockfile -r42 {0}".format(lockfile))