Re: Migration from cron to cron-daemon?
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
Re: Migration from cron to cron-daemon?
On 2014-10-16 Stephan Seitz stse+deb...@fsing.rootsland.net wrote:
Is there currently a migration from „cron” to „cron-daemon” as virtual
package?
New packages like brcon-run don’t provide cron anymore but cron-daemon.
And many packages like exim4-base or mgetty-fax haven’t changed their
dependencies (and other packages their recommends).
Some packages have already bug reports for this case. But shouldn’t this
be a reason for a mass bug filling?
Hello,
to give a little bit of backstory:
cron is the real package, cron-daemon is the virtual package name
according to
https://www.debian.org/doc/packaging-manuals/virtual-package-names-list.txt.
This has not changed.
Up until recently there were exactly two packages providing the virtual
package cron-daemon in Debian, cron and systemd-cron. And the latter
provided the virtual package without having the complete functionality
as required by policy, most notably no support for /etc/etc/cron.d,
and even incomplete support for /etc/etc/cron.{daily,weekly,hourly}.
See #752376. Which is why packages that used policy mandated
cron functionality depended on cron instead of the virtual package.
Now systemd-cron is supposed to be fixed and bcron was changed in
August to provide the virtual package instead of cron which is why
there are new bug reports cropping up.
cu Andreas
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
--
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/20141018060725.ga3...@downhill.g.la
Re: Migration from cron to cron-daemon?
On Sat, Oct 18, 2014 at 08:07:25AM +0200, Andreas Metzler wrote: Now systemd-cron is supposed to be fixed and bcron was changed in August to provide the virtual package instead of cron which is why there are new bug reports cropping up. So, if I want to write bug reports, what is now the correct expression for cron? cron-daemon|cron? Is this a release critical bug? As a testing user I now have problems using bcron. Shade and sweet water! Stephan -- | Stephan Seitz E-Mail: s...@fsing.rootsland.net | | Public Keys: http://fsing.rootsland.net/~stse/keys.html | smime.p7s Description: S/MIME cryptographic signature
Re: Migration from cron to cron-daemon?
Stephan Seitz writes: So, if I want to write bug reports, what is now the correct expression for cron? cron-daemon|cron? Don't overthink it. If you are having a problem with cron type reportbug cron and follow instructions. -- John Hasler jhas...@newsguy.com Elmwood, WI USA -- 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/877fzxjmqp@thumper.dhh.gt.org
Re: Migration from cron to cron-daemon?
Stephan Seitz stse+deb...@fsing.rootsland.net writes: On Sat, Oct 18, 2014 at 08:07:25AM +0200, Andreas Metzler wrote: Now systemd-cron is supposed to be fixed and bcron was changed in August to provide the virtual package instead of cron which is why there are new bug reports cropping up. So, if I want to write bug reports, what is now the correct expression for cron? cron-daemon|cron? There are still a *lot* of packages that depend on cron rather than cron-daemon. See: http://users.teledisnet.be/ade15809/cron-daemon.html I think this would be a good thing to fix, but it's rather late to do this for jessie. 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. -- Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/ -- 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/87r3y5dwm3@hope.eyrie.org
Re: Migration from cron to cron-daemon?
On Thu, Oct 16, 2014 at 12:18 PM, Stephan Seitz
stse+deb...@fsing.rootsland.net wrote:
Hi!
I sent the attached message to debian-release, but I was told to ask in
debian-devel.
So here is the mail.
Shade and sweet water!
Stephan
--
| Stephan Seitz E-Mail: s...@fsing.rootsland.net |
| Public Keys: http://fsing.rootsland.net/~stse/keys.html |
-- Forwarded message --
From: Stephan Seitz stse+deb...@fsing.rootsland.net
To: debian-rele...@lists.debian.org
Cc:
Date: Thu, 16 Oct 2014 15:21:59 +0200
Subject: Migration from cron to cron-daemon?
Hi!
Is there currently a migration from „cron” to „cron-daemon” as virtual
package?
New packages like brcon-run don’t provide cron anymore but cron-daemon. And
many packages like exim4-base or mgetty-fax haven’t changed their
dependencies (and other packages their recommends).
Some packages have already bug reports for this case. But shouldn’t this be
a reason for a mass bug filling?
Getting a little bit off topic, is there a way for a package to depend
on the /etc/cron.{hourly,daily,etc} files being executed, but not
depend on the actual full crontab implementation?
This would allow for a more minimal cron daemon on certain setups (or
no cron daemon, plus the systemd glue that has appeared,
systemd-cron).
Thanks,
--
Cameron Norman
--
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/calzwfrjqvltrj9z1brcoedbsqyfrjzkgajcqctqzq17m2...@mail.gmail.com
Migration from cron to cron-daemon?
Hi! I sent the attached message to debian-release, but I was told to ask in debian-devel. So here is the mail. Shade and sweet water! Stephan -- | Stephan Seitz E-Mail: s...@fsing.rootsland.net | | Public Keys: http://fsing.rootsland.net/~stse/keys.html | ---BeginMessage--- Hi! Is there currently a migration from „cron” to „cron-daemon” as virtual package? New packages like brcon-run don’t provide cron anymore but cron-daemon. And many packages like exim4-base or mgetty-fax haven’t changed their dependencies (and other packages their recommends). Some packages have already bug reports for this case. But shouldn’t this be a reason for a mass bug filling? Shade and sweet water! Stephan -- | Stephan Seitz E-Mail: s...@fsing.rootsland.net | | Public Keys: http://fsing.rootsland.net/~stse/keys.html | smime.p7s Description: S/MIME cryptographic signature ---End Message--- smime.p7s Description: S/MIME cryptographic signature
