Bug 2345929

Summary: Please branch and build libsecret in epel10
Product: [Fedora] Fedora Reporter: Romain Geissler <romain.geissler>
Component: libsecretAssignee: Kalev Lember <klember>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: rawhideCC: debarshir, dueno, gnome-sig, klember, ndegraef, stefw
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-02-27 10:27:44 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:
Bug Depends On:    
Bug Blocks: 2345928, 2355197    

Description Romain Geissler 2025-02-15 17:24:15 UTC
Hi,

Please branch and build libsecret in epel10.

Checking right now, it builds fine on EPEL 10 when using the rawhide branch content, see this scratch build: https://koji.fedoraproject.org/koji/taskinfo?taskID=129269563

Reproducible: Always

Comment 1 Romain Geissler 2025-02-24 22:46:20 UTC
If you do not wish to maintain libsecret in epel10,
or do not think you will be able to do this in a timely manner,
I would be happy to be a co-maintainer of the package (FAS romaingeissler1a);
please add me through https://src.fedoraproject.org/rpms/libsecret/adduser

Comment 2 Niels De Graef 2025-02-27 10:22:35 UTC
Looking at https://composes.stream.centos.org/stream-10/production/latest-CentOS-Stream/compose/AppStream/x86_64/os/Packages/ I'm not sure why there needs to be an epel branch if it's already going to be in c10s. I don't think epel10 can/should have an srpm with the same name as c10s?

Comment 3 Romain Geissler 2025-02-27 10:27:32 UTC
Ah you are right, I had not checked that it was already in CentOS.

I need it for a dependency tree of package eventually leading to this ticket, most likely the problem is that the dependency depends on a more recent libsecret, so I have to check how I deal with that. I need to check that later.

I will close this ticket.