Please branch and build gi-docgen in epel9. If you do not wish to maintain gi-docgen in epel9, 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/gi-docgen/addgroup and grant it commit access, or collaborator access on epel* branches.
Thanks for reporting the missing adobe-source-code-pro-fonts dependency in bug 2072650. When that is available, I will gladly branch and build gi-docgen.
If I comment out the missing font dependencies (for testing purposes only), I get: > No matching package to install: 'python3dist(typogrify)' Would you care to file an EPEL9 request bug on python-typogrify too?
Done: https://bugzilla.redhat.com/show_bug.cgi?id=2072651
Looks like I can do this when RHEL 9.1 comes out with adobe-source-code-pro-fonts, then. Feel free to remind me if I forget.
Looks like adobe-source-code-pro-fonts is now available: http://mirror.stream.centos.org/9-stream/AppStream/x86_64/os/Packages/adobe-source-code-pro-fonts-2.030.1.050-12.el9.1.noarch.rpm
(In reply to Davide Cavalca from comment #5) > Looks like adobe-source-code-pro-fonts is now available: > http://mirror.stream.centos.org/9-stream/AppStream/x86_64/os/Packages/adobe- > source-code-pro-fonts-2.030.1.050-12.el9.1.noarch.rpm It looks like adobe-source-code-pro-fonts is not in RHEL yet, so I can’t build for epel9. I did try building for epel9-next, but I found that python3-typogrify is not installable because its dependency python3-smartypants is missing: https://src.fedoraproject.org/rpms/python-smartypants. Would you like to file the EPEL9 request for that one too?
Done: https://bugzilla.redhat.com/show_bug.cgi?id=2130608
FEDORA-EPEL-NEXT-2022-83de2d1a5d has been submitted as an update to Fedora EPEL 9 Next. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-NEXT-2022-83de2d1a5d
This bug will remain open until gi-docgen is in EPEL9 “proper.”
FEDORA-EPEL-NEXT-2022-83de2d1a5d has been pushed to the Fedora EPEL 9 Next testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-NEXT-2022-83de2d1a5d See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-NEXT-2022-83de2d1a5d has been pushed to the Fedora EPEL 9 Next stable repository. If problem still persists, please make note of it in this bug report.
Now buildable in epel9 proper. Scratch build in koji of the epel9-next version in epel9: https://koji.fedoraproject.org/koji/taskinfo?taskID=94218954
(In reply to Mattias Ellert from comment #12) > Now buildable in epel9 proper. > Scratch build in koji of the epel9-next version in epel9: > https://koji.fedoraproject.org/koji/taskinfo?taskID=94218954 Thank you for the heads-up. Branch requested: https://pagure.io/releng/fedora-scm-requests/issue/49142
Given the release of RHEL 9.1, this should be able to move forward now, right?
(In reply to Robert Scheck from comment #14) > Given the release of RHEL 9.1, this should be able to move forward now, > right? I noted in the comment above yours that I had requested the epel9 branch. That request was processed by this morning. I would have had a build in the EPEL9 testing repo today, but koji was having a meltdown. Expect a Bodhi update in the next day or so.
You are right, sorry for the double "heads up". And thanks for taking care! :)
(In reply to Robert Scheck from comment #16) > You are right, sorry for the double "heads up". And thanks for taking care! > :) No problem! I’m glad to have some help keeping an eye on things.
FEDORA-EPEL-2022-989476cd02 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-989476cd02
FEDORA-EPEL-2022-989476cd02 has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report.