Hi, Thanks for you bug report.
It's already fixed in git, but review/testing is welcome. http://anonscm.debian.org/cgit/collab-maint/systemd-cron.git/commit/?id=a615388da700ec1124a60973e8a05e47d03c654c |"IRL, this would result into one nag-email a week only if | systemd-cron had been replaced by vixie cron or anacron | python3 is not installed | an MTA has been configured" +++ b/debian/systemd-cron.cron.weekly @@ -0,0 +1,4 @@ +#!/bin/sh +test -x /usr/bin/python3 || exit 0 +test -x /lib/systemd-cron/remove_stale_stamps || exit 0 +exec /lib/systemd-cron/remove_stale_stamps Cheers, Alexandre Le mercredi 3 juin 2015 12:19:59, vous avez écrit : > Package: systemd-cron > Version: 1.5.2-1 > Severity: important > User: [email protected] > 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 _______________________________________________ Pkg-systemd-maintainers mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
