fixed -1 0.9.6-1 thanks I agree with your concern about lock-out from the cron job not running. Unfortunately, shield-purge (which does the actual work when called by the cron job) also had a stack of problems in 0.9.2 that could lead to the same result. I did try my best to get fixes in for wheezy; unfortunately 0.9.6-1 didn't get sponsor attention before freeze (several of these issues were fixed in 0.9.2-4 for squeeze and never got attention.)
Looking through the git history, I think I can take patches designed for 0.9.2-4, apply against 0.9.2-3.3, and manage not to break the upgrade to 0.9.6-1. This should be doable via unstable. Technically it would be an NMU, based on "not changing anything besides the bug," but I think it would match freeze policy under "fixes for severity: important bugs in packages of priority: optional or extra, only when this can be done via unstable." Of course, once I actually go to implement it (quilt-managed patches in 1.0 packages, ew) I may find I'm staring at a brick wall. I'd appreciate a commitment from someone to sponsor before I put in the work, though. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
