On Sun, Feb 26, 2023 at 5:56 PM Maxwell G <maxwell(a)gtmx.me> 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.
Is python3.11 already available in epel9-next (or rather, CentOS
Stream 9 or whatever it's called now)? I'm not sure how to check ...
If yes, then what's the process for submitting builds for epel9-next?
Do koji's on-demand side-tags work there?
I don't think I've ever submitted an update for an "epel-next" branch
before, sorry if these are questions with obvious answers :)
Fabio