Hi,
systemd-cron has been fixed _today_ in unstable.
Can you please let apticron depends now on cron-daemon ?
You can also depends on cron | cron-daemon to specify that you prefer
the real cron if there were previously no cron-daemon installed.
I realize that depending on cron-daemon isn't a
Since it's systemd-cron's fault:
- the clean solution would be to depend on cron-daemon with a note
(changelog, Breaks:, whatever) that systemd-cron needs to be fixed
I have posted a proposal to merge systemd-crontab-generator into
systemd-cron to make it
POSIX Debian compliant. Both
On 09/01/2014 09:42 PM, Gian Piero Carrubba wrote:
Hi Lorenzo,
sorry I haven't still read the whole thread and all the related bug
reports, so I'm not giving an informed advice. Anyway, given I'm the one
to blame for the '--cron' option, I would like to explain the reasons
for some of the
On 08/31/2014 03:58 PM, Alexandre Detiste wrote:
I'm not a fan of systemd-cron(*); I was going to ask to switch the
dependency from cron to cron-daemon, but that wouldn't be feasible because
systemd-cron is a __broken__ replacement for cron (until bug 752376 is
fixed), so I proposed running
Then, the file /etc/crontab would then not contains theses standard
boilerplate lines anymore
17 ** * * rootcd / run-parts --report /etc/cron.hourly
25 6* * * roottest -x /usr/sbin/anacron || ( cd / run-parts
--report /etc/cron.daily )
47 6* * 7 root
On 09/01/2014 05:45 PM, Alexandre Detiste wrote:
Then, the file /etc/crontab would then not contains theses standard
boilerplate lines anymore
17 ** * * rootcd / run-parts --report /etc/cron.hourly
25 6* * * roottest -x /usr/sbin/anacron || ( cd / run-parts
--report
Hi Lorenzo,
sorry I haven't still read the whole thread and all the related bug
reports, so I'm not giving an informed advice. Anyway, given I'm the one
to blame for the '--cron' option, I would like to explain the reasons
for some of the choices.
* [Mon, Sep 01, 2014 at 04:55:09PM +0200]
I'm not a fan of systemd-cron(*); I was going to ask to switch the
dependency from cron to cron-daemon, but that wouldn't be feasible because
systemd-cron is a __broken__ replacement for cron (until bug 752376 is
fixed), so I proposed running apticron in cron.daily to work around that
Hi Lorenzo,
On Wed, Aug 27, 2014 at 02:29:20PM +0200, Lorenzo wrote:
On 08/27/2014 06:30 AM, Tiago Bortoletto Vaz wrote:
Hi Lorenzo,
Thanks for your detailed report, I was not aware of this issue.
However, I'm not sure if I understood your proposal. If we include the
old cron daily
On 08/27/2014 06:30 AM, Tiago Bortoletto Vaz wrote:
Hi Lorenzo,
Thanks for your detailed report, I was not aware of this issue.
However, I'm not sure if I understood your proposal. If we include the
old cron daily script we'll end with at least two issues which were
fixed by removing it. One
Hi Lorenzo,
Thanks for your detailed report, I was not aware of this issue.
However, I'm not sure if I understood your proposal. If we include the
old cron daily script we'll end with at least two issues which were
fixed by removing it. One is having two instances of apticron running
Package: apticron
Version: 1.1.56
Severity: wishlist
Dear Maintainer,
as a fix for bug 752506, bcron-run chose to provide cron-daemon rather
than cron, which looks correct to me.
Except that the new bcron-run and apticron don't work well together:
apt-get upgrade leaves me with the old version,
12 matches
Mail list logo
