sgallagh opened a new pull-request against the project: `pungi-fedora` that you are following:
``
Include cloud-server on BaseOS comps
``
To reply, visit the link below or just reply to this email
https://pagure.io/pungi-fedora/pull-request/1317
ngompa opened a new pull-request against the project: `pungi-fedora` that you are following:
``
Consolidate kiwibuild configuration
``
To reply, visit the link below or just reply to this email
https://pagure.io/pungi-fedora/pull-request/1316
yselkowitz opened a new pull-request against the project: `pungi-fedora` that you are following:
``
[eln] Sync from c10s, update signing key to F42
``
To reply, visit the link below or just reply to this email
https://pagure.io/pungi-fedora/pull-request/1315
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/troubleshootin…) but could not spot the procedure in it.
Thanks!
Kind regards
Denis
Some of you have probably noticed that Koji is a bit overloaded at the
moment. Well, that's my fault. Sorry about that. I'm writing up a
post-mortem on how it happened so we can all learn from my mistakes.
This time around, we coordinated with releng to update the Rawhide tag
we trigger on as part of the branching event. That's good! We're not
getting forgotten anymore! The problem is that when all of the Rawhide
builds were re-tagged for the new trigger (f42), we suddenly enqueued
all of those builds again, resulting in a mass rebuild.
In the past, this was sort of quietly avoided because two things were different:
1. The trigger tag wasn't updated until after the mass-tag had been
completed, mainly because we weren't coordinating properly.
2. We implemented a new "pause" feature in ELNBuildSync (aka EBS) that
allows us to leave messages on the message queue instead of processing
them immediately. In the past, this meant that we would have read and
`DROP`ped the messages for the Rawhide re-tag.
So with the combination of those two events, what happened this time
is that we unpaused EBS and it immediately read through the list of
re-tagging messages and promptly enqueued every ELN package for
rebuild.
There's a long discussion[1] in the ELN Matrix channel about what we
can do to avoid this problem in the future, but right now I think that
the simplest answer will be "just don't update the tag we listen for
until after the mass-retagging". We're looking into ways we can
automate this to avoid it being a manual process, but that's the basic
idea.
[1] https://matrix.to/#/#eln:fedoraproject.org
yselkowitz opened a new pull-request against the project: `pungi-fedora` that you are following:
``
[eln] Consolidate packages
``
To reply, visit the link below or just reply to this email
https://pagure.io/pungi-fedora/pull-request/1313
Dear all,
You are kindly invited to the meeting:
Fedora Release Engineering on 2024-08-13 from 12:00:00 to 13:00:00 US/Eastern
At fedora-meeting-3(a)irc.libera.chat
The meeting will be about:
Fedora Release Engineering weekly meeting
Source: https://calendar.fedoraproject.org//meeting/10679/
jnsamyak opened a new pull-request against the project: `pungi-fedora` that you are following:
``
Branch Fedora 41 from Rawhide
``
To reply, visit the link below or just reply to this email
https://pagure.io/pungi-fedora/pull-request/1310
jnsamyak opened a new pull-request against the project: `pungi-fedora` that you are following:
``
Rawhide is now F42
``
To reply, visit the link below or just reply to this email
https://pagure.io/pungi-fedora/pull-request/1311
adamwill opened a new pull-request against the project: `pungi-fedora` that you are following:
``
composes: keep metadata where it won't be garbage collected
``
To reply, visit the link below or just reply to this email
https://pagure.io/pungi-fedora/pull-request/1312