Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 890319 - sys-process/systemd-cron-1.15.19-r1: stabilisation
Summary: sys-process/systemd-cron-1.15.19-r1: stabilisation
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Stabilization (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Richard Freeman
URL:
Whiteboard:
Keywords: CC-ARCHES, STABLEREQ
Depends on:
Blocks:
 
Reported: 2023-01-10 05:49 UTC by Sam James
Modified: 2023-02-10 20:41 UTC (History)
1 user (show)

See Also:
Package list:
sys-process/systemd-cron-1.15.19-r1
Runtime testing required: ---
nattka: sanity-check+


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sam James archtester Gentoo Infrastructure gentoo-dev Security 2023-01-10 05:49:56 UTC
Ready? Thanks.

Please remember to file stable bugs.
Comment 1 Richard Freeman gentoo-dev 2023-01-10 11:37:23 UTC
Thanks for the reminder.  I was hoping for an upstream merge of the mail patch so that is probably why I didn't set a reminder.

I see the package was updated this morning, so I'll make a note to put out a request in 30d.
Comment 2 Florian Schmaus gentoo-dev 2023-01-11 09:08:54 UTC
The recent change to the ebuild 885d5aef8f5e ("sys-process/systemd-cron: enable py3.11") seems trivial and would not justify waiting another 30 days. The ebuild itself is in ::gentoo since 2022-07-25. IMHO, systemd-cron-1.15.19-r1 could go stable right now.

FWIW, I was yesterday also about to fill a stable request for systemd-cron, to get an newer version of it on my stable servers. But then b.g.o was down.
Comment 3 Richard Freeman gentoo-dev 2023-01-11 12:34:39 UTC
(In reply to Florian Schmaus from comment #2)
> The recent change to the ebuild 885d5aef8f5e ("sys-process/systemd-cron:
> enable py3.11") seems trivial and would not justify waiting another 30 days.
> The ebuild itself is in ::gentoo since 2022-07-25. IMHO,
> systemd-cron-1.15.19-r1 could go stable right now.
> 

The whole point of the delay is to allow for testing, and since we just enabled a new version of python that presumably wouldn't have been tested previously.  Since 3.11 is stable that would expose stable users to a configuration that hasn't been flagged for testing previously.

I get that it is one of those things that people will have different views on.  If another dev wants to stabilize and deal with any problems, that is of course something they can do.  Otherwise I have a note on my calendar to take care of it in 30d, and assuming no issues come up I don't anticipate any delays there.
Comment 4 Larry the Git Cow gentoo-dev 2023-02-10 18:49:45 UTC
The bug has been referenced in the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3fd5f7d79258a6ab1f3483eda18c2838d63fb264

commit 3fd5f7d79258a6ab1f3483eda18c2838d63fb264
Author:     Richard Freeman <rich0@gentoo.org>
AuthorDate: 2023-02-10 18:48:55 +0000
Commit:     Richard Freeman <rich0@gentoo.org>
CommitDate: 2023-02-10 18:49:12 +0000

    sys-process/systemd-cron: stabilize 1.15.19-r1 for amd64
    
    Bug: https://bugs.gentoo.org/890319
    Signed-off-by: Richard Freeman <rich0@gentoo.org>

 sys-process/systemd-cron/systemd-cron-1.15.19-r1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
Comment 5 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2023-02-10 20:34:26 UTC
ppc64 done
Comment 6 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2023-02-10 20:34:28 UTC
ppc done
Comment 7 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2023-02-10 20:34:29 UTC
sparc done
Comment 8 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2023-02-10 20:36:47 UTC
arm64 done
Comment 9 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2023-02-10 20:41:13 UTC
x86 done
Comment 10 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2023-02-10 20:41:15 UTC
arm done

all arches done