As this bug will not arise in normal operation (run-parts ignores cron
jobs with a dot in the filename[0]), this doesn't seem worth asking
for a release exception. A version that fixes this bug and also
patches the rules file to make sure the bug actually arises would seem
a little perverse, given
Control: tag -1 - patch
On 2013-02-03 21:31, Jonathan Niehof wrote:
As this bug will not arise in normal operation (run-parts ignores cron
jobs with a dot in the filename[0]), this doesn't seem worth asking
for a release exception. A version that fixes this bug and also
OK, didn't notice this
Followup-For: Bug #563065
Control: tag -1 patch
Hi,
I'm adding a small patch that actually backports pam_shield.cron from
0.9.6 as found in experimental. This exits with 0 if the package was
removed.
I plan to NMU libpam-shield in a few days with this patch and hope we
can still get this fix
Are you offering to sponsor an upload, or simply declaring an NMU?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: libpam-shield
Version: 0.9.2-3.2
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts piuparts.d.o
Hi,
during a test with piuparts I noticed your packages cronjob exits with
errorcode 1 after the package has been removed.
From the attached log (scroll to the
5 matches
Mail list logo
