Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14356] cronstamp jobs are not performed with bumped version of dcron
Date: Wed, 01 Dec 2021 21:17:42 +0000	[thread overview]
Message-ID: <bug-14356-163-bpJdZsjyMw@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-14356-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=14356

--- Comment #5 from Peter Seiderer <ps.report@gmx.net> ---
(In reply to Dominique Tronche from comment #4)

Any updates on this one? I can confirm the changed behavior/failure for the
default /etc/cron.d/system @hourly entry (did not run the test longer),
can confirm that the offending commit seems to be [1] (upstream issue already
exists [2], dating back to May 2018)...

[1]
https://github.com/dubiousjim/dcron/commit/f048a83da348c1d62204fcbdf407b7abf33e3db0

[2] https://github.com/dubiousjim/dcron/issues/15

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2021-12-01 21:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-17  9:50 [Buildroot] [Bug 14356] New: cronstamp jobs are not performed with bumped version of dcron bugzilla
2021-11-17  9:52 ` [Buildroot] [Bug 14356] " bugzilla
2021-11-17 20:20 ` bugzilla
2021-11-18 12:32 ` bugzilla
2021-11-18 12:34 ` bugzilla
2021-12-01 21:17 ` bugzilla [this message]
2023-05-05 14:15 ` bugzilla
2023-05-06 15:21 ` bugzilla

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-14356-163-bpJdZsjyMw@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@uclibc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox