On Thu, Apr 14, 2022 at 4:34 PM Tom Stellard <tstellar@xxxxxxxxxx> wrote: > > On 4/13/22 17:48, Fabio Valentini wrote: > > On Sat, Apr 9, 2022 at 12:48 PM Fabio Valentini <decathorpe@xxxxxxxxx> wrote: > >> > >> Hi all, > >> > >> Looks like there's a little bit of a mess around LLVM 14 / GCC / > >> annobin updates brewing in f36-updates-testing. > >> > >> Right now, there's *two* updates in "testing" state that contain > >> builds of annobin: > >> > >> - https://bodhi.fedoraproject.org/updates/FEDORA-2022-c43760a865 > >> - https://bodhi.fedoraproject.org/updates/FEDORA-2022-3dd2ddf4ab > > > > And, lo and behold, now there's a third update for annobin: > > https://bodhi.fedoraproject.org/updates/FEDORA-2022-3dd2ddf4ab > > > > The update for LLVM 14 was pushed to stable due to a freeze exception, > > but the GCC+annobin update is still in "testing". > > And now there's a new version of annobin in an additional update. > > > > Please, given that we're *this close* to F36 release, coordinate > > better on updates for such "unimportant packages" as the default > > compiler toolchain .. > > > > Is there some way for Bodhi to warn about this kind of problem or a > CI test that could be added to prevent these updates from being pushed > to testing? This is a common problem that happens (not just to annobin) > when there is an LLVM update. Even if maintainers are aware of the update, > it can be easy to forget that it's there especially if it sits for a while. This is actually mostly a problem for multi-build updates that have been created from side tags. They aren't obsoleted / superseded when a newer build of a package is submitted to bodhi, so multiple updates for the same package can be in-flight at the same time, which leads to all kinds of "fun" race conditions (including the "older" build getting composed into "stable" repositories, depending on the order in which the updates are submitted to stable). Fabio _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
