On Tue, 14 Feb 2023 at 10:46, Pavel Raiskup <prais...@redhat.com> wrote: > > On pátek 10. února 2023 11:38:25 CET Iñaki Ucar wrote: > > On Fri, 10 Feb 2023 at 11:35, Peter Robinson <pbrobin...@gmail.com> wrote: > > > > > > On Fri, Feb 10, 2023 at 10:27 AM Iñaki Ucar <iu...@fedoraproject.org> > > > wrote: > > > > > > > > On Fri, 10 Feb 2023 at 09:44, Jakub Kadlcik <jkadl...@redhat.com> wrote: > > > > > > > > > > Hello Tomas, > > > > > thank you for the announcement. > > > > > > > > > > We also branched Fedora 38 in Copr so that everybody can submit builds > > > > > for it by now. Also, all projects with the "Follow Fedora branching" > > > > > option configured in their project settings have F38 chroots > > > > > automatically enabled and they contain the last build results from > > > > > Fedora Rawhide before the branch. > > > > > > > > Is this still ongoing? I don't see F38 in my projects. > > > > > > I do in all of my packages, you should just need to do a git pull to > > > get the new branches. > > > > I meant in Copr. > > Just confirming - Copr branching is a two-phase process; we first link the > RPMs from rawhide to the branched release, and then we enable (when we know > the > chroot is building fine). > https://docs.pagure.org/copr.copr/how_to_manage_chroots.html#branching-process > > When Jakub announced, we just had those packages hardlinked, and RPMs > available > on backend. But the 38 chroots got enabled later (next day).
Ok, got it, thanks. -- Iñaki Úcar _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to 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/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
