On 09. 11. 21 16:07, Troy Dawson wrote:
If you can get them branched for epel9-next, you can work on them.
Currently a fedpkg that understands epel9-next needs to be built. I used this
pull request [1] and it worked, at least it requested the branch.
The people on the rel-eng team that do the branches need to have their
fedscm-admin updated with the correct patches. I'm told that should happen
today or tomorrow.
If your package is a noarch, and you manage to get it built (koji loves to put
srpm builds on s390x), then yes, run it through bodhi and it should do it's
normal thing and packages will arrive in the epel9-next-testing, and epel9-next
repos
I got:
DEBUG util.py:444: No match for group package "epel-release"
DEBUG util.py:444: No match for group package "epel-rpm-macros"
Hence, my package dd not build, because
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-NEXT-2021-341875060f is not
yet stable and I'm blocked on https://bugzilla.redhat.com/show_bug.cgi?id=2001034
Other than that, it seems to build fine.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
_______________________________________________
epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
