Bug 2257936

Summary:	Please branch and build <package> in epel9 (or epel8, etc.)
Product:	[Fedora] Fedora	Reporter:	Bruno <bruno.vitorge>
Component:	Zim	Assignee:	Sandro <gui1ty>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	40	CC:	gui1ty, nixuser, oliver, otto.liljalaakso
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:	Zim-0.75.2-8.el9 Zim-0.75.2-10.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-03-09 01:13:30 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Bruno 2024-01-11 15:54:08 UTC

Please branch and build zim in epel9.

I would like to help to maintain but I do not have knowledge in packaging maintenance, sorry.


Reproducible: Always

Comment 1 Otto Liljalaakso 2024-01-12 11:59:27 UTC

Unfortunately, I (the primary maintainer) am not involved with EPEL, so I do not want, and also lack the knowledge, to maintain anything for EPEL. We would need a packager who wants to assume the responsibility for EPEL. Please ask around in EPEL mailing list or such for interest.

Comment 2 Bruno 2024-01-12 13:18:41 UTC

Thank you for your fast reply.
I will try to find someone.

Comment 3 Sandro 2024-01-17 21:34:21 UTC

I just built Zim locally for epel9. No changes to the spec file were required. I'd be willing to maintain the epel branches.

I already have commit access in dist-git for Zim. But only the main admin can request new branches. Otto, could you request the epel9 branch, please, and assign me (gui1ty) as maintainer for EPEL?

Comment 4 Otto Liljalaakso 2024-01-20 10:34:16 UTC

(In reply to Sandro from comment #3)
> I just built Zim locally for epel9. No changes to the spec file were
> required. I'd be willing to maintain the epel branches.
> 
> I already have commit access in dist-git for Zim. But only the main admin
> can request new branches. Otto, could you request the epel9 branch, please,
> and assign me (gui1ty) as maintainer for EPEL?

Great! Branch created and gui1ty assigned, please let me know if something does not work and you cannot fix it yourself. Since we now have a situation were only some maintainers are involved with EPEL, I suggest that in case you need to add some EPEL-specifics in the specfile, you let EPEL branches split from Fedora Rawhide, instead of adding RPM conditionals. Because I might be able to work with those conditionals.

Comment 5 Sandro 2024-01-20 11:26:55 UTC

(In reply to Otto Liljalaakso from comment #4)
> Great! Branch created and gui1ty assigned, please let me know if something
> does not work and you cannot fix it yourself. Since we now have a situation
> were only some maintainers are involved with EPEL, I suggest that in case
> you need to add some EPEL-specifics in the specfile, you let EPEL branches
> split from Fedora Rawhide, instead of adding RPM conditionals. Because I
> might be able to work with those conditionals.

Thank you! I'll get going. Merging rawhide into epel verbatim is what I'm planning on. If it doesn't build in epel, I'll sort that out in the branch and let those diverge. I should still be able to cherry pick where applicable.

I think we are on the same page here. ;)

Comment 6 Aoife Moloney 2024-02-15 23:09:46 UTC

This bug appears to have been reported against 'rawhide' during the Fedora Linux 40 development cycle.
Changing version to 40.

Comment 7 Fedora Update System 2024-02-29 09:31:28 UTC

FEDORA-EPEL-2024-b2f7922be6 (Zim-0.75.2-10.el8) has been submitted as an update to Fedora EPEL 8.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-b2f7922be6

Comment 8 Fedora Update System 2024-02-29 09:31:28 UTC

FEDORA-EPEL-2024-c396c0b92a (Zim-0.75.2-8.el9) has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-c396c0b92a

Comment 9 Fedora Update System 2024-03-01 02:05:12 UTC

FEDORA-EPEL-2024-c396c0b92a has been pushed to the Fedora EPEL 9 testing repository.

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

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

Comment 10 Fedora Update System 2024-03-01 02:12:57 UTC

FEDORA-EPEL-2024-b2f7922be6 has been pushed to the Fedora EPEL 8 testing repository.

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

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

Comment 11 Fedora Update System 2024-03-09 01:13:30 UTC

FEDORA-EPEL-2024-c396c0b92a (Zim-0.75.2-8.el9) has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 12 Fedora Update System 2024-03-09 01:36:40 UTC

FEDORA-EPEL-2024-b2f7922be6 (Zim-0.75.2-10.el8) has been pushed to the Fedora EPEL 8 stable repository.
If problem still persists, please make note of it in this bug report.