[re2] Block re2 update for F41

[Denis Arnaud]

The re2 package has been upgraded (to 2024-07-02) in Fedora Rawhide, triggering an update on Fedora 41: https://bodhi.fedoraproject.org/updates/FEDORA-2024-82d9eb51a1
This introduces an announced soname bump of the libre2.so library, and there are a few direct and indirect packages which need to be rebuilt.
But most of those rebuilds break, potentially because another unrelated issue with grpc.

Is it possible to block this F41 update (https://bodhi.fedoraproject.org/updates/FEDORA-2024-82d9eb51a1)?
As far as I can tell, it does not seem to have reached the F41 repositories yet (I just did a `dnf upgrade` on my Fedora Rawhide virtual machine, and the re2 update did not show up).

For reference:
* re2 source application in Fedora: https://src.fedoraproject.org/rpms/re2
* F41 update for re2: https://bodhi.fedoraproject.org/updates/FEDORA-2024-82d9eb51a1

List of direct dependencies:
```
$ fedrq wrsrc -Xs -F name re2
CuraEngine_grpc_definitions
bloaty
ceph
credentials-fetcher
dnsdist
grpc
libarrow
libphonenumber
mtxclient
nheko
onnxruntime
parlaylib
perl-re-engine-RE2
python-fb-re2
python-torchtext
qt5-qtwebengine
```

And some of those packages have, in turn, their own downstream dependencies.

If this mailing list is not the good one to post such a request, would you be so kind so to point me to the right procedure?
I read the doc (https://docs.fedoraproject.org/en-US/infra/releng_misc_guide/troubleshooting...), but could not spot the procedure in it.

Thanks!

Kind regards

Denis

[Kevin Fenzi]

On Wed, Aug 14, 2024 at 08:05:46AM GMT, Denis Arnaud wrote:
> The re2 package has been upgraded (to 2024-07-02) in Fedora Rawhide, triggering an update on Fedora 41: https://bodhi.fedoraproject.org/updates/FEDORA-2024-82d9eb51a1
> This introduces an announced soname bump of the libre2.so library, and there are a few direct and indirect packages which need to be rebuilt.
> But most of those rebuilds break, potentially because another unrelated issue with grpc.
>
> Is it possible to block this F41 update (https://bodhi.fedoraproject.org/updates/FEDORA-2024-82d9eb51a1)?
> As far as I can tell, it does not seem to have reached the F41 repositories yet (I just did a `dnf upgrade` on my Fedora Rawhide virtual machine, and the re2 update did not show up).

well, we just branched f41 off of rawhide yesterday.

It seems to be tagged for both rawhide and f41 currently:

-
➜  ~ koji latest-pkg f41 re2
Build                                     Tag                   Built by
----------------------------------------  --------------------  ----------------
re2-20240702-1.fc41                       f41                   denisarnaud
➜  ~ koji latest-pkg f42 re2
Build                                     Tag                   Built by
----------------------------------------  --------------------  ----------------
re2-20240702-1.fc41                       f42                   denisarnaud

So, we can untag it, but... the f41 branched compose finished and is
syncing out so it's already out there. ;(

Also, dependent packages may already have built against it.
> For reference:
> re2 source application in Fedora: https://src.fedoraproject.org/rpms/re2
> F41 update for re2: https://bodhi.fedoraproject.org/updates/FEDORA-2024-82d9eb51a1
>
> List of direct dependencies:
> $ fedrq wrsrc -Xs -F name re2
> CuraEngine_grpc_definitions
> bloaty
> ceph
> credentials-fetcher
> dnsdist
> grpc
> libarrow
> libphonenumber
> mtxclient
> nheko
> onnxruntime
> parlaylib
> perl-re-engine-RE2
> python-fb-re2
> python-torchtext
> qt5-qtwebengine
>
> And some of those packages have, in turn, their own downstream dependencies.
>
> If this mailing list is not the good one to post such a request, would you be so kind so to point me to the right procedure?
> I read the doc (https://docs.fedoraproject.org/en-US/infra/releng_misc_guide/troubleshooting...), but could not spot the procedure in it.

Process is normally to make a ticket:

https://pagure.io/releng/

We can discuss this on the devel list too...

kevin

[Denis Arnaud]

Thanks Kevin!

You are absolutely right: the parallel discussion on the devel mailing list
shows that most of the downstream packages have already been rebuilt
successfully, fortunately (thanks to the reactivity of the packagers!).

So, it's too late to block (untag) the re2 package, and many of the
dependent packages have nevertheless been already rebuilt.

Thanks to all for your reactivity!

Kr

D

On Wed 14 Aug 2024 at 18:41, Kevin Fenzi  wrote:
> On Wed, Aug 14, 2024 at 08:05:46AM GMT, Denis Arnaud wrote:
> > The re2 package has been upgraded (to 2024-07-02) in Fedora Rawhide,
>
> triggering an update on Fedora 41:
> https://bodhi.fedoraproject.org/updates/FEDORA-2024-82d9eb51a1
> > This introduces an announced soname bump of the libre2.so library, and
>
> there are a few direct and indirect packages which need to be rebuilt.
> > But most of those rebuilds break, potentially because another unrelated
>
> issue with grpc.
> > Is it possible to block this F41 update (
>
> https://bodhi.fedoraproject.org/updates/FEDORA-2024-82d9eb51a1)?
> > As far as I can tell, it does not seem to have reached the F41
>
> repositories yet (I just did a `dnf upgrade` on my Fedora Rawhide virtual
> machine, and the re2 update did not show up).
>
> well, we just branched f41 off of rawhide yesterday.
>
> It seems to be tagged for both rawhide and f41 currently:
>
> ➜  ~ koji latest-pkg f41 re2
> Build                                     Tag                   Built by
>
> re2-20240702-1.fc41                       f41                   denisarnaud
> ➜  ~ koji latest-pkg f42 re2
> Build                                     Tag                   Built by
>
> re2-20240702-1.fc41                       f42                   denisarnaud
>
> So, we can untag it, but... the f41 branched compose finished and is
> syncing out so it's already out there. ;(
>
> Also, dependent packages may already have built against it.
> > For reference:
> > re2 source application in Fedora:
>
> https://src.fedoraproject.org/rpms/re2
> > F41 update for re2:
>
> https://bodhi.fedoraproject.org/updates/FEDORA-2024-82d9eb51a1
> > List of direct dependencies:
> > $ fedrq wrsrc -Xs -F name re2
> > CuraEngine_grpc_definitions
> > bloaty
> > ceph
> > credentials-fetcher
> > dnsdist
> > grpc
> > libarrow
> > libphonenumber
> > mtxclient
> > nheko
> > onnxruntime
> > parlaylib
> > perl-re-engine-RE2
> > python-fb-re2
> > python-torchtext
> > qt5-qtwebengine
> >
> > And some of those packages have, in turn, their own downstream
>
> dependencies.
> > If this mailing list is not the good one to post such a request, would
>
> you be so kind so to point me to the right procedure?
> > I read the doc (
>
> https://docs.fedoraproject.org/en-US/infra/releng_misc_guide/troubleshooting...),
> but could not spot the procedure in it.
>
> Process is normally to make a ticket:
>
> https://pagure.io/releng/
>
> We can discuss this on the devel list too...
>
> kevin

[Kevin Fenzi]

On Wed, Aug 14, 2024 at 07:39:59PM GMT, Denis Arnaud wrote:
> Thanks Kevin!
>
> You are absolutely right: the parallel discussion on the devel mailing list
> shows that most of the downstream packages have already been rebuilt
> successfully, fortunately (thanks to the reactivity of the packagers!).
>
> So, it's too late to block (untag) the re2 package, and many of the
> dependent packages have nevertheless been already rebuilt.
>
> Thanks to all for your reactivity!

Happy to help...

Hope things are going well for you these days?

kevin
--
> Kr
>
> D
>
> On Wed 14 Aug 2024 at 18:41, Kevin Fenzi  wrote:
> > On Wed, Aug 14, 2024 at 08:05:46AM GMT, Denis Arnaud wrote:
> > > The re2 package has been upgraded (to 2024-07-02) in Fedora Rawhide,
> >
> > triggering an update on Fedora 41:
> > https://bodhi.fedoraproject.org/updates/FEDORA-2024-82d9eb51a1
> > > This introduces an announced soname bump of the libre2.so library, and
> >
> > there are a few direct and indirect packages which need to be rebuilt.
> > > But most of those rebuilds break, potentially because another unrelated
> >
> > issue with grpc.
> > > Is it possible to block this F41 update (
> >
> > https://bodhi.fedoraproject.org/updates/FEDORA-2024-82d9eb51a1)?
> > > As far as I can tell, it does not seem to have reached the F41
> >
> > repositories yet (I just did a `dnf upgrade` on my Fedora Rawhide virtual
> > machine, and the re2 update did not show up).
> >
> > well, we just branched f41 off of rawhide yesterday.
> >
> > It seems to be tagged for both rawhide and f41 currently:
> >
> > ➜  ~ koji latest-pkg f41 re2
> > Build                                     Tag                   Built by
> >
> > re2-20240702-1.fc41                       f41                   denisarnaud
> > ➜  ~ koji latest-pkg f42 re2
> > Build                                     Tag                   Built by
> >
> > re2-20240702-1.fc41                       f42                   denisarnaud
> >
> > So, we can untag it, but... the f41 branched compose finished and is
> > syncing out so it's already out there. ;(
> >
> > Also, dependent packages may already have built against it.
> > > For reference:
> > > re2 source application in Fedora:
> >
> > https://src.fedoraproject.org/rpms/re2
> > > F41 update for re2:
> >
> > https://bodhi.fedoraproject.org/updates/FEDORA-2024-82d9eb51a1
> > > List of direct dependencies:
> > > $ fedrq wrsrc -Xs -F name re2
> > > CuraEngine_grpc_definitions
> > > bloaty
> > > ceph
> > > credentials-fetcher
> > > dnsdist
> > > grpc
> > > libarrow
> > > libphonenumber
> > > mtxclient
> > > nheko
> > > onnxruntime
> > > parlaylib
> > > perl-re-engine-RE2
> > > python-fb-re2
> > > python-torchtext
> > > qt5-qtwebengine
> > >
> > > And some of those packages have, in turn, their own downstream
> >
> > dependencies.
> > > If this mailing list is not the good one to post such a request, would
> >
> > you be so kind so to point me to the right procedure?
> > > I read the doc (
> >
> > https://docs.fedoraproject.org/en-US/infra/releng_misc_guide/troubleshooting...),
> > but could not spot the procedure in it.
> >
> > Process is normally to make a ticket:
> >
> > https://pagure.io/releng/
> >
> > We can discuss this on the devel list too...
> >
> > kevin