From e81babf3fc6237e9cc032f9c29d3b6ac1cfe060a Mon Sep 17 00:00:00 2001 From: Ansgar Burchardt Date: Mon, 17 Jun 2013 20:17:53 +0200 Subject: [PATCH] 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. --- dak/new_security_install.py | 4 ---- 1 file changed, 4 deletions(-) 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)) -- 2.39.5