Bug#902015: systemd-cron: fails to upgrade from 'wheezy' - trying to overwrite /usr/bin/crontab
alexandre.detiste at gmail.com
Fri Jun 29 07:44:57 BST 2018
I feel like the severity of this bug is much too high,
as it only concerns bcron-run versus systemd-cron;
not vixie cron (the santdard implementation) vs systemd-cron.
I don't see how to cleanly solve it.
Should any cron implemnetation & breaks against
all the other cron implementation ?
Or better against virtual package cron-deamon ?
Also, why a bug between wheezy and jessie should affect a package in
the next release ?
"Your package has been marked for autoremoval from testing."
BTW: anyone interrested into this can upload a new version and
take car of it; I only ever power on my dev- computer once in a moon
when I have to rip new CD's.
2018-06-21 15:40 GMT+02:00 Andreas Beckmann <anbe at debian.org>:
> Package: systemd-cron
> Version: 1.3.1+ds1-2
> Severity: serious
> User: debian-qa at lists.debian.org
> Usertags: piuparts
> during a test with piuparts I noticed your package fails to upgrade from
> It installed fine in 'wheezy', then the upgrade to 'jessie' fails
> because it tries to overwrite other packages files without declaring a
> Breaks+Replaces relation.
> See policy 7.6 at
> From the attached log (scroll to the bottom...):
> Selecting previously unselected package systemd-cron.
> Preparing to unpack .../systemd-cron_1.3.1+ds1-2_all.deb ...
> Unpacking systemd-cron (1.3.1+ds1-2) ...
> dpkg: error processing archive /var/cache/apt/archives/systemd-cron_1.3.1+ds1-2_all.deb (--unpack):
> trying to overwrite '/usr/bin/crontab', which is also in package bcron-run 0.09-13
> Errors were encountered while processing:
More information about the Pkg-systemd-maintainers