On Wed, Aug 24, 2022 at 10:58 AM Iñaki Ucar <iu...@fedoraproject.org> wrote:
>
> On Wed, 24 Aug 2022 at 10:49, Petr Pisar <ppi...@redhat.com> wrote:
> >
> > V Tue, Aug 23, 2022 at 08:16:00PM +0200, Iñaki Ucar napsal(a):
> > > Hi all,
> > >
> > > We have a new R version sitting on a side tag (f37-build-side-55653)
> > > for a few weeks now, where packages are being rebuilt as time permits.
> > > Unfortunately, F37 is not rawhide anymore, so the question is whether
> > > this side tag could be safely merged both in F37 and rawhide when it
> > > is ready.
> > >
> > I think you can tag any package anywhere. Therefore should be possible to 
> > get
> > the same build into both Fedoras.
> >
> > However, it could be unsafe (e.g. a change in C toolchain to distribution
> > macros). To mitigate it I think you can rebuild the packages in a F38 side 
> > tag
> > without additional commits. Just follow the order which was used in F37 side
> > tag. The commits exist both in F37 and F38 git branches. F38 builds will get
> > unique release strings due to differing %dist tag.
>
> Thanks. The main issue is that there are circular dependencies, and it
> requires bootstrapping in some cases and disabling the checks in
> others, and then another pass to reenable everything. So if the
> rawhide rebuild can be based on the result of the F37 side tag, then
> bootstrapping etc. is not required, and the rebuild is fast and
> straightforward. More so if no commits are needed.

That might be possible, I'll look into it when it comes to that.
First the f37 update needs to be finished and submitted :)

Fabio
_______________________________________________
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

Reply via email to