Bug 2308768

Summary: Please branch and build python-coverage in epel10
Product: [Fedora] Fedora EPEL Reporter: Kaleb KEITHLEY <kkeithle>
Component: python-coverageAssignee: Kaleb KEITHLEY <kkeithle>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: epel10CC: aurelien, carl, gauret, mrunge, mrunge, spotrh, xavier
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-09-23 15:40:55 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: 2303880, 1914423, 2308761, 2311680    

Description Kaleb KEITHLEY 2024-08-30 21:05:52 UTC
Please branch and build python-coverage in epel10.

If you do not wish to maintain python-coverage 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/python-coverage/addgroup
and grant it commit access, or collaborator access on epel* branches.

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

Comment 1 Kaleb KEITHLEY 2024-09-09 13:03:01 UTC
bump

Comment 2 Kaleb KEITHLEY 2024-09-09 16:02:51 UTC
Aurélien or Matthias???

Would either of you please build in epel10. Or grant epel-pkgrs-sig the privs to build it?

Thanks

Comment 3 Carl George 🎩 2024-09-10 01:25:18 UTC
As a gentle reminder for anyone looking to work on this, it's perfectly fine for python-coverage to be added to EPEL 10, but it should not be a BuildRequirement blocker for any other packages.  The packaging guidelines state that code coverage tools should not be run during package builds.

https://docs.fedoraproject.org/en-US/packaging-guidelines/Python/#_linters

Packages that have a BuildRequirement for python-coverage should attempt to remove it, either by invoking their tests differently, patching the source code, or both.  This applies to both Fedora and EPEL, and has the nice side effect of making the package easier to bring to new EPEL versions.  If you need assistance with this, feel free to ask for help in the matrix channels #python:fedoraproject.org and/or #epel:fedoraproject.org.

Comment 4 Matthias Runge 2024-09-10 05:51:17 UTC
I have added you Kaleb to the package. Since I don't have the time to work on extra packages, I removed myself.

Comment 5 Kaleb KEITHLEY 2024-09-13 19:52:09 UTC
(In reply to Carl George 🤠 from comment #3)
> As a gentle reminder for anyone looking to work on this, it's perfectly fine
> for python-coverage to be added to EPEL 10, but it should not be a
> BuildRequirement blocker for any other packages.

attempt to scratch build python-zope-interface fails without it, although it does not, itself, have an explicit BR for it.

e.g. https://kojipkgs.fedoraproject.org/work/tasks/5106/123355106/root.log (while it lasts)

Is there some implicit python voodoo that could be generating the BR?

Comment 6 Carl George 🎩 2024-09-14 00:11:36 UTC
Yes.

https://docs.fedoraproject.org/en-US/packaging-guidelines/Python/#Automatically-generated-dependencies

I believe if you remove this line (either with sed or a patch) a build should work without coverage available.

https://github.com/zopefoundation/zope.interface/blob/7.0.3/setup.py#L84