Package: at
Version: 3.1.10
When testing packages with my development version of piuparts, which now
builds a minimal chroot (i.e., removes as many packages as possible), I
ran into the following problem in at: it creates a file
in /var/spool/cron/atjobs in its postinst, and removes it in its postrm
(when the package is purged), but this can break removal and purging of
cron.
The problem manifests itself in the following sequence:
* Install at, cron (apt-get install at cron). The .SEQ file is
created.
* Remove at at, cron (dpkg --remove at cron). All is fine so
far.
* Purge cron (dpkg --purge cron). .SEQ still exists. Errors
happen.
Here's the error output from the last step:
[EMAIL PROTECTED]:/# dpkg --purge cron
(Reading database ... 8188 files and directories currently installed.)
Removing cron ...
Purging configuration files for cron ...
dpkg - warning: while removing cron, directory `/var/spool/cron' not
empty so not removed.
Note that this works if at is purged before cron, but there's no
guarantee that will happen.
The easiest fix for this would probably be to keep the .SEQ file
outside /var/spool/cron, but I don't know how big a change that would
be.
If you'd prefer to mark this as "wontfix", on the assumption that few
people ever remove at and cron, and anyway it's a specific sequence
that's required, then that's fine by me. For piuparts testing, I can
deal with this by adding an ignore rule for /var/spool/cron.
--
There's a reason why "release manager" is abbreviated "rm".
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
