On Sat, Oct 18, 2014 at 12:08:20PM -0700, Russ Allbery wrote: > Stephan Seitz <stse+deb...@fsing.rootsland.net> writes: > > Is this a release critical bug? As a testing user I now have problems > > using bcron. > > Given that this is a migration that's barely been started, I think it > would be best for bcron-run to continue to Provide cron for the jessie > release. Using the cron-daemon virtual package is clearly where we want > to end up, but it feels to me like there's too high of a risk of > regressing for bcron users in the next release by trying to do this now, > and I don't see any harm in bcron-run continuing to Provide cron for one > more release. There will be time after the release to do a more > coordinated transition. > > bcron-run should, of course, continue to provide cron-daemon as well.
Hi, I uploaded a new bcron version to unstable that reverts the change and adds Provides: cron-daemon just as you advise. Thanks, both. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141020122139.5835.qm...@ec3ff24b13f0cc.315fe32.mid.smarden.org
