On Tue, Mar 11, 2025 at 5:01 PM Fabio Valentini wrote:
>
> Hi all,
>
> It's this time of the year again. Looks like there's quite a few
> updates that were submitted to Fedora 41 but not to Fedora 42 and / or
> Rawhide.
>
> Some seem to be either caused by confusion about the ongoing freeze,
> but
On Tue, Mar 11, 2025 at 8:32 PM Michael Catanzaro wrote:
>
> I'm pretty concerned that we have no automation to catch these
> problems. Would we have even noticed if not for you manually checking
> and complaining here on devel@?
Probably not. Which is why I do this kind of thing twice a year :)
I'm pretty concerned that we have no automation to catch these
problems. Would we have even noticed if not for you manually checking
and complaining here on devel@?
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an e
On 2025/03/11 17:17, Fabio Valentini wrote:
On Tue, Mar 11, 2025 at 5:12 PM Michael J Gruber wrote:
Given the many packit related ones - does packit have a concept of
"follow Fedora release branching" (like COPR), or do packit users have
to update their config after a branch event?
Many projec
On Tue, Mar 11, 2025 at 5:12 PM Michael J Gruber wrote:
>
> Fabio Valentini venit, vidit, dixit 2025-03-11 17:01:15:
> > Hi all,
> >
> > It's this time of the year again. Looks like there's quite a few
> > updates that were submitted to Fedora 41 but not to Fedora 42 and / or
> > Rawhide.
> >
> >
Fabio Valentini venit, vidit, dixit 2025-03-11 17:01:15:
> Hi all,
>
> It's this time of the year again. Looks like there's quite a few
> updates that were submitted to Fedora 41 but not to Fedora 42 and / or
> Rawhide.
>
> Some seem to be either caused by confusion about the ongoing freeze,
> bu
Hi all,
It's this time of the year again. Looks like there's quite a few
updates that were submitted to Fedora 41 but not to Fedora 42 and / or
Rawhide.
Some seem to be either caused by confusion about the ongoing freeze,
but a lot are just ... missing. And packit seems to be a major
offender her
