On Tue, Nov 9, 2021 at 6:31 AM Miro Hrončok <mhron...@redhat.com> wrote:
> On 08. 11. 21 15:56, Troy Dawson wrote: > > > > On Mon, Nov 8, 2021 at 3:31 AM Neal Gompa <ngomp...@gmail.com > > <mailto:ngomp...@gmail.com>> wrote: > > > > On Mon, Nov 8, 2021 at 2:18 AM Remi Collet <fed...@famillecollet.com > > <mailto:fed...@famillecollet.com>> wrote: > > > > > > As both RHEL-9 Beta and CentOS 9 Stream are available, > > > what are the plan for EPEL-9 ? > > > > > > > > > I really this should be available ASAP to be > > > available to our users at GA time. > > > > EPEL 9 Next for CentOS Stream 9 is blocked on the migration of our > > s390x systems to z15[1], because currently all s390x builds fail[2]. > > Once that's taken care of, we'll launch EPEL 9 Next. > > > > [1]: https://pagure.io/fedora-infrastructure/issue/10302 > > <https://pagure.io/fedora-infrastructure/issue/10302> > > [2]: https://pagure.io/releng/issue/10360 > > <https://pagure.io/releng/issue/10360> > > > > > > Our current goal to have epel9-next completely available for > > maintainers/developers is December 1st. Basically one month after RHEL > 9 beta > > was released. > > > > We are hoping to have it available earlier, but as Neal pointed out, > we've got > > a (known) blocker with the build platform. And it's possible that once > that > > get's fixed there might be something else we weren't expecting. > > > > So, December 1st is our goal. When it is available, we will announce it > on as > > many channels as we can. > > Hello Troy. > > Is preparing specfiles in the epel9-next branches discouraged at this > point? Or > even shipping noarch packages with no arched EPEL-only deps? > > 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 > Another question I have is the branch structure. Will we start by building > from > the eple9-next branches and eventually fork them to epel9 branches once > EPEL 9 > exists as well? > > Yes, start by building on the epel9-next branches. When the time comes for epel9, there will be a one-time-only mass merge over, and mass rebuild. There was a Flock/Nest talk about that.[2] After that one time mass merge and rebuild, epel9 and epel9-next will be just like epel8 and epel8-next are now. Troy [1] - https://pagure.io/fedpkg/pull-request/453 [2] - https://www.youtube.com/watch?v=naxvolMewgA
_______________________________________________ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
