Doesn't seem to be a python-domdf-python-tools component in Fedora EPEL. Could it be built for epel10? I could help if you'd like to add me. Reproducible: Always
(In reply to Dan Radez from comment #0) > Doesn't seem to be a python-domdf-python-tools component in Fedora EPEL. > Could it be built for epel10? > I could help if you'd like to add me. > > Reproducible: Always That's probably why the ebranch tool put it in 'Fedora' instead of 'Fedora EPEL' I've seen this happen in a couple other packages that I asked for an EPEL10 build. (Maybe a separate ticket needs to be filed to get it added to 'Fedora EPEL' ??? It should build in EPEL10 regardless of the bugzilla component. At least I can do a scratch build in EPEL10. (Which fails due to missing dependencies.)
(In reply to Kaleb KEITHLEY from comment #1) > (In reply to Dan Radez from comment #0) > > Doesn't seem to be a python-domdf-python-tools component in Fedora EPEL. > > Could it be built for epel10? > > I could help if you'd like to add me. > > > > Reproducible: Always > > That's probably why the ebranch tool put it in 'Fedora' instead of 'Fedora > EPEL' I've seen this happen in a couple other packages that I asked for an > EPEL10 build. > Ignore that. I was thinking I had opened this BZ (with the ebranch tool) but I was mistaken.
If you do not wish to maintain python-domdf-python-tools 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-jaraco-packaging/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-domdf-python-tools/adduser
scratch build https://koji.fedoraproject.org/koji/taskinfo?taskID=125592793
Okay, so there's two people and the EPEL SIG who are willing to co-maintain this package. Who would like to be the primary EPEL maintainer and Bugzilla assignee? I'd prefer for that to be an actual person and not the epel-packagers-sig, as I don't think anyone triages bugs for the epel-packagers-sig. Also, note the test dependency cycle with python-coincidence. Someone will also need to maintain that and handle bootstrapping the packages in a sidetag (python-domdf-python-tools without tests -> python-coincidence -> python-domdf-python-tools with tests) like I did in Fedora.
I don't want to be a "co-maintainer", i.e. I don't want all EPEL bzs assigned to me as I've just found that that co-maintainers implies bz assignment. Not do I want to be responsible for epel8 and epel9 builds if someone decides they want those. I am willing to "own" the epel10 builds if you want to give me the committer or collaborator bit.
Since we don't seem to be getting anywhere.... I will co-maintain the package for epel.
Thanks. @kkeithle is now a co-maintainer and the epel Bugzilla assignee.
FEDORA-EPEL-2024-1d7e334d71 (python-domdf-python-tools-3.9.0-1.el10_0) has been submitted as an update to Fedora EPEL 10.0. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-1d7e334d71
FEDORA-EPEL-2024-1d7e334d71 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-2024-1d7e334d71 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2024-1d7e334d71 (python-domdf-python-tools-3.9.0-1.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.