Bug#787611: systemd-cron: cronjob exits with error after package removal

[Andreas Beckmann]

Package: systemd-cron
Version: 1.5.2-1
Severity: important
User: debian-qa at lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your packages cronjob exits with
error after the package has been removed.

>From the attached log (scroll to the bottom...):

0m45.0s DEBUG: Starting command: ['chroot', '/tmp/piupartss/tmpvWuoaF', '/etc/cron.weekly/systemd-cron']
0m45.0s DUMP: 
  chroot: failed to run command `/etc/cron.weekly/systemd-cron': No such file or directory
0m45.0s ERROR: Command failed (status=127): ['chroot', '/tmp/piupartss/tmpvWuoaF', '/etc/cron.weekly/systemd-cron']

The cronjob is a python3 script.
At the time this script was run, systemd-cron as well as python3 were removed
(but systemd-cron was not purged), so the needed interpreter was not found
any more, resulting in cron spewing errors.

cheers,

Andreas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: systemd-cron_1.5.2-1.log.gz
Type: application/gzip
Size: 9418 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20150603/c342ffd2/attachment.bin>