releng

#13036 Retag ejected Bodhi pushes from failed compose (builders fix impact)
Closed: Fixed by jnsamyak. Opened by jnsamyak.

Closed: Fixed
Reopen Issue

Description:

During today’s compose, several Bodhi updates were ejected due to the ongoing builder issues. The compose failure led to these updates being dropped.
Flatpak builds are already being handled separately, so this ticket tracks non-Flatpak Fedora updates only.

These updates need to be reviewed and retagged to either:
-pending-testing, or
-candidate

as appropriate.

FEDORA-2025-d11261d473  fcitx5-5.1.16-1.fc42
FEDORA-2025-66fb3fa6b0  bind-9.18.41-1.fc43
FEDORA-2025-9933872d65  crosswords-0.3.16.2-1.fc43
FEDORA-2025-793c50d804  haruna-1.6.0-1.fc42
FEDORA-2025-7d9c7f15ad  ocaml-cpdf-2.8.1-1.fc42
FEDORA-2025-4acc51b3f9  digikam-8.8.0-1.fc43
FEDORA-2025-b205f40552  openmw-0.49.0-9.fc42
FEDORA-2025-4c2b0ee418  emacs-30.2-4.fc43
FEDORA-2025-df98744d8d  python-sqlite-migrate-0.1~b0-1.fc42
FEDORA-2025-69bb3e0340  rust-alacritty_terminal-0.25.1-1.fc42
FEDORA-2025-eaac9c417f  gap-4.15.1-1.fc43
FEDORA-2025-bb3a46a245  rust-crypto-auditing-0.2.3-5.fc42
FEDORA-2025-cc54a72bb9  gdk-pixbuf2-2.44.4-1.fc43
FEDORA-2025-7234cc70a8  rust-typenum-1.19.0-1.fc42
FEDORA-2025-cfbbf9b56b  rust-url-2.5.7-1.fc42
FEDORA-2025-37cb448a83  rust-zstd-sys-2.0.16-1.fc42
FEDORA-2025-e2956ec610  gst-devtools-1.26.7-1.fc43
FEDORA-2025-51b5fdc613  solaar-1.1.16-1.fc42
FEDORA-2025-935dc3f65a  stb-0^20251025gitf1c79c0-1.fc42
FEDORA-2025-34736d4a32  strawberry-1.2.14-1.fc42
FEDORA-2025-a557949f39  java-21-openjdk-21.0.9.0.10-1.fc43
FEDORA-2025-5a936ab0a5  kitty-0.43.1-3.fc43
FEDORA-2025-67b0a9a393  libdecor-0.2.4-1.fc43
FEDORA-2025-4f2b9310b0  libdrm-2.4.127-3.fc43
FEDORA-2025-bf75a8e636  planarity-4.0.1.0-1.fc43
FEDORA-2025-e39d6dbd19  python-boto3-1.40.56-1.fc43
FEDORA-2025-16d124a396  python-gitlab-6.5.0-1.fc43
FEDORA-2025-c64be5633b  python-watchfiles-1.1.1-1.fc43
FEDORA-2025-9a46af550f  qt5-qtbase-5.15.17-6.fc43
FEDORA-2025-93e94dc306  selinux-policy-42.14-1.fc43
FEDORA-2025-e52df2a9ce  spacer-0.5.0-1.fc43
FEDORA-2025-2f124e7827  squid-7.2-1.fc43
FEDORA-2025-aed2d1c0c1  web-eid-2.7.0-1.fc43
FEDORA-2025-e01494f776  dialect-2.6.1-2.fc43
FEDORA-2025-99820fbef6  fcitx5-5.1.16-1.fc43
FEDORA-2025-86fd842326  haruna-1.6.0-1.fc43
FEDORA-2025-0956602f41  ocaml-cpdf-2.8.1-1.fc43
FEDORA-2025-38761a8047  openmw-0.49.0-9.fc43
FEDORA-2025-161cd91eae  python-autobahn-25.10.2-1.fc43
FEDORA-2025-92a06081a4  python-sqlite-utils-3.38-1.fc43
FEDORA-2025-3ae70d9344  rust-alacritty_terminal-0.25.1-1.fc43
FEDORA-2025-98228cd858  rust-crypto-auditing-0.2.3-5.fc43
FEDORA-2025-7b35fcbacc  rust-typenum-1.19.0-1.fc43
FEDORA-2025-548049ab14  rust-url-2.5.7-1.fc43
FEDORA-2025-e62ad9cfd5  solaar-1.1.16-1.fc43
FEDORA-2025-4a46d8366d  speedcrunch-0.12^20241202git3c1b4c1-1.fc43
FEDORA-2025-58ace87b58  stb-0^20251025gitf1c79c0-1.fc43
FEDORA-2025-2a34a6e4ad  strawberry-1.2.14-1.fc43
FEDORA-2025-22f0d0366c  ocaml-cpdf-2.8.1-1.fc41
FEDORA-2025-d68d758ee5  rust-alacritty_terminal-0.25.1-1.fc41
FEDORA-2025-e767e7e714  rust-b3sum-1.8.2-3.fc41
FEDORA-2025-8e4461701c  rust-crypto-auditing-0.2.3-3.fc41
FEDORA-2025-8004afaba3  rust-typenum-1.19.0-1.fc41
FEDORA-2025-a47f27bb52  rust-url-2.5.7-1.fc41
FEDORA-2025-74b3263294  rust-zstd-sys-2.0.16-1.fc41
FEDORA-2025-6a32cc8b7a  stb-0^20251025gitf1c79c0-1.fc41
FEDORA-2025-79259a9956  strawberry-1.2.14-1.fc41

Metadata Update from @jnsamyak:
- Issue tagged with: high-gain, medium-trouble, ops, sprint-3

Metadata Update from @jnsamyak:
- Issue assigned to jnsamyak

All the F43/F42/F41 updates mentioned above are handled and are tagged properly, should be in the respective places soonish with next compose i suppose.

Metadata Update from @jnsamyak:
- Issue untagged with: high-gain, medium-trouble, ops, sprint-3
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

FYI a bunch of F43F updates (push to stable) were similarly affected, however I have retagged and resubmitted them already.

Seems a number aren't perhaps going to testing...

There doesn't seem to be a good way to list them all, but looking at:

But if you look on pages 4, 5, 6 here:

https://bodhi.fedoraproject.org/updates/?status=pending&page=4

and ones that are pending without a request for testing.
It might be they just need to have a testing request, or perhaps they are still needing tagged?

Can you take a look at them?

Metadata Update from @kevin:
- Issue status updated to: Open (was: Closed)

Two of my pending updates are affected too:

https://koji.fedoraproject.org/koji/buildinfo?buildID=2850538
https://koji.fedoraproject.org/koji/buildinfo?buildID=2850499

They are tagged "-signing-pending" so I'm not sure why the signing doesn't see them as "to be signed", I tried untagging them and tagging them into their respective "-candidate" tags, which did nothing. Looks like fixing them myself is beyond my powers.

Metadata Update from @jnsamyak:
- Issue tagged with: medium-gain, medium-trouble, ops, sprint-3

I fixed those two. autosign ignores normal users tagging into signing pending tags as a security measure. It only works if bodhi does it. ;)

I looked at the tracker otherwise, and fixed some of the other bunch, and I see the composes went in. If there will be another bunch, I'll look into it; otherwise, I think we are sorted.

Metadata Update from @jnsamyak:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)
Metadata

medium-gain medium-trouble ops sprint-3

None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.