public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Lars Wendler" <polynomial-c@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-process/cronie/files/, sys-process/cronie/
Date: Wed,  6 Apr 2022 07:16:38 +0000 (UTC)	[thread overview]
Message-ID: <1649229391.64ffabcdbbdd71f9a3328d252cb033e6579011b9.polynomial-c@gentoo> (raw)

commit:     64ffabcdbbdd71f9a3328d252cb033e6579011b9
Author:     Lars Wendler <polynomial-c <AT> gentoo <DOT> org>
AuthorDate: Wed Apr  6 07:14:55 2022 +0000
Commit:     Lars Wendler <polynomial-c <AT> gentoo <DOT> org>
CommitDate: Wed Apr  6 07:16:31 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=64ffabcd

sys-process/cronie: Revbump to fix 1-5 crontab entries regression

Thanks-to: Klemen Mihevc <solor <AT> outlook.com>
Closes: https://bugs.gentoo.org/836888
Signed-off-by: Lars Wendler <polynomial-c <AT> gentoo.org>

 ...ronie-1.6.0-r1.ebuild => cronie-1.6.0-r2.ebuild} |  1 +
 .../cronie-1.6.0-crontab_entries_regression.patch   | 21 +++++++++++++++++++++
 2 files changed, 22 insertions(+)

diff --git a/sys-process/cronie/cronie-1.6.0-r1.ebuild b/sys-process/cronie/cronie-1.6.0-r2.ebuild
similarity index 97%
rename from sys-process/cronie/cronie-1.6.0-r1.ebuild
rename to sys-process/cronie/cronie-1.6.0-r2.ebuild
index 93c845e1da39..6f15a911b057 100644
--- a/sys-process/cronie/cronie-1.6.0-r1.ebuild
+++ b/sys-process/cronie/cronie-1.6.0-r2.ebuild
@@ -33,6 +33,7 @@ S="${WORKDIR}/${PN}-${P}"
 
 PATCHES=(
 	"${FILESDIR}/${PN}-1.5.3-systemd.patch"
+	"${FILESDIR}/${P}-crontab_entries_regression.patch" #836888
 )
 
 src_prepare() {

diff --git a/sys-process/cronie/files/cronie-1.6.0-crontab_entries_regression.patch b/sys-process/cronie/files/cronie-1.6.0-crontab_entries_regression.patch
new file mode 100644
index 000000000000..160c03116415
--- /dev/null
+++ b/sys-process/cronie/files/cronie-1.6.0-crontab_entries_regression.patch
@@ -0,0 +1,21 @@
+From 62e53f1cdb9c1e12a01ee7814c92cd937d50328d Mon Sep 17 00:00:00 2001
+From: w30023233 <wangyuhang27@huawei.com>
+Date: Wed, 23 Mar 2022 15:40:01 +0800
+Subject: [PATCH] Fix regression in handling 1-5 crontab entries
+
+---
+ src/entry.c | 1 +
+ 1 file changed, 1 insertion(+)
+
+diff --git a/src/entry.c b/src/entry.c
+index e9e258b..bb7cb62 100644
+--- a/src/entry.c
++++ b/src/entry.c
+@@ -595,6 +595,7 @@ get_range(bitstr_t * bits, int low, int high, const char *names[],
+ 				return (EOF);
+ 
+ 			case R_RANGE:
++				unget_char(ch, file);
+ 				if (get_number(&num2, low, names, file) != EOF) {
+ 					state = R_RANGE_NUM2;
+ 					break;


             reply	other threads:[~2022-04-06  7:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-06  7:16 Lars Wendler [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-25 23:28 [gentoo-commits] repo/gentoo:master commit in: sys-process/cronie/files/, sys-process/cronie/ Sam James
2022-09-23  0:42 Sam James
2021-03-17 17:26 Lars Wendler
2020-11-03  6:49 Lars Wendler
2019-11-02  9:46 Lars Wendler
2019-03-17 11:10 Lars Wendler
2019-03-16 20:03 Lars Wendler
2016-07-02 12:24 Lars Wendler

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=1649229391.64ffabcdbbdd71f9a3328d252cb033e6579011b9.polynomial-c@gentoo \
    --to=polynomial-c@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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