Bug 2323769 - Please branch and build etckeeper in epel10
Summary: Please branch and build etckeeper in epel10
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: etckeeper
Version: epel10
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Thomas Moschny
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 2323770
Blocks: EPELPackagersSIG
TreeView+ depends on / blocked
 
Reported: 2024-11-05 02:43 UTC by Michel Lind
Modified: 2025-07-21 00:48 UTC (History)
5 users (show)

Fixed In Version: etckeeper-1.18.22-3.el10_1 etckeeper-1.18.22-3.el10_0
Clone Of:
Environment:
Last Closed: 2025-07-21 00:22:39 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Michel Lind 2024-11-05 02:43:13 UTC
Please branch and build etckeeper in epel10.

If you do not wish to maintain etckeeper in epel10,
or do not think you will be able to do this in a timely manner,
the EPEL Packagers SIG would be happy to be a co-maintainer of the package;
please add the epel-packagers-sig group through
https://src.fedoraproject.org/rpms/etckeeper/addgroup
and grant it commit access, or collaborator access on epel* branches.

I would also be happy to be a co-maintainer (FAS: salimma);
please add me through https://src.fedoraproject.org/rpms/etckeeper/adduser

Comment 1 Joe Cooper 2025-06-11 22:10:45 UTC
Any movement on this? Looks like there are folks willing to work on it. I'd also be willing to test and make a PR with any needed changes, or whatever, if no one else wants to do it. I'd rather not add it to my own repos if it's going to appear in EPEL some time soon or if I can do something to encourage it to appear in EPEL repos soon.

Comment 2 Collin 2025-06-16 20:46:16 UTC
I would also like to see etckeeper included in the epel10 repository.

Comment 3 Thomas Moschny 2025-06-17 16:17:57 UTC
Sorry folks for the delay, will look into it soon. But we need to check DNF compatibility...

Comment 4 Joe Cooper 2025-06-17 17:03:35 UTC
Fedora 40 (and onward) has `etckeeper` and `etckeeper-dnf` and they seem to work fine, though I haven't dug into it much, I see it doing the things I would expect on my Fedora systems, including committing changes before a dnf run. I believe EL10 was branched from Fedora 40. EL10 seems to have dnf 4.20, and I have a Fedora system with dnf 4.23 that works. I'll be quite surprised it the Fedora 40 package can't just be rebuilt for EL10. But, I'll give it a try tonight after work.

Comment 5 Fedora Update System 2025-07-15 12:34:00 UTC
FEDORA-EPEL-2025-2601cdaa8f (etckeeper-1.18.22-3.el10_1) has been submitted as an update to Fedora EPEL 10.1.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-2601cdaa8f

Comment 6 Fedora Update System 2025-07-16 01:46:15 UTC
FEDORA-EPEL-2025-2601cdaa8f has been pushed to the Fedora EPEL 10.1 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-2601cdaa8f

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2025-07-16 01:51:57 UTC
FEDORA-EPEL-2025-fe52c2607e has been pushed to the Fedora EPEL 10.0 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-fe52c2607e

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 8 Joe Cooper 2025-07-16 15:11:29 UTC
Thank you! 🎉

Comment 9 Fedora Update System 2025-07-21 00:22:39 UTC
FEDORA-EPEL-2025-2601cdaa8f (etckeeper-1.18.22-3.el10_1) has been pushed to the Fedora EPEL 10.1 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 10 Fedora Update System 2025-07-21 00:48:30 UTC
FEDORA-EPEL-2025-fe52c2607e (etckeeper-1.18.22-3.el10_0) has been pushed to the Fedora EPEL 10.0 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.