On Tue Feb 28, 2023 at 23:44 +0100, Fabio Valentini wrote: > On Sun, Feb 26, 2023 at 5:56 PM Maxwell G <maxwell@xxxxxxx> wrote: > > > > I think the intention was to push this to epel9-next first, but then I > > accidentally opened the last two PRs against epel9 instead of > > epel9-next. FTR, python3.11 won't be available until ~May when 9.2 comes > > out, so we can't yet built this in epel9 proper. Can you confirm that > > you'd like this in epel9-next? I think giving this some time to incubate > > in epel9-next definitely makes sense. > > If it helps, sure ... though there aren't really any Rust packages in > epel9-next, so the impact will be small (and the packages won't get > much testing, either). > We can build cargo2rpm v0.1.2 and rust-packaging v24 in epel9-next > first, and merge to epel9 once the dependencies are available. Right; it's possible to build for epel9-next and then merge back to epel9 and rebuild once RHEL 9.2 that will include python3.11 is released. If you or others will use and test this in epel9-next, then I think it's worth it. > Is python3.11 already available in epel9-next (or rather, CentOS > Stream 9 or whatever it's called now)? Yes, python3.11 is available in CentOS Stream 9 and thus available in the epel9-next buildroot. CentOS Stream 9 is a preview of the next RHEL 9 minor release. > I'm not sure how to check ... You can use fedrq, another repoquerying tool, or spin up a CentOS Stream container to search. ``` $ fedrq pkgs -Sb c9s python3.11 python3.11-devel python3.11-pytest python3.11-3.11.2-2.el9.x86_64 python3.11-devel-3.11.2-2.el9.x86_64 python3.11-pytest-7.2.0-1.el9.noarch ``` > If yes, then what's the process for submitting builds for epel9-next? > Do koji's on-demand side-tags work there? You can run `fedpkg build` or `fedpkg request-side-tag` on the epel9-next distgit branch just as you can anywhere else. `epel9-next` is a separate Koji build target that includes packages from CentOS Stream 9, packages from regular epel9, and packages specifically built for epel9-next. It has its own Bodhi release. > I don't think I've ever submitted an update for an "epel-next" branch > before, sorry if these are questions with obvious answers :) Don't worry about it :). The concept of EPEL Next is a bit confusing. -- Best, Maxwell G (@gotmax23) Pronouns: He/They _______________________________________________ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
