This was confusing me for a few days...
for t in f42 f41 f40 epel10.0 epel9; do koji list-tagged --quiet $t-signing-pending done
outputs
rust-bootupd-0.2.24-1.fc41 f41-signing-pending siosm kwin-6.0.4.1-3.fc40 f40-signing-pending farchord btrfs-efi-20230328^git20240520.c134e61-1.el10_0 epel10.0-signing-pending ngompa btrfs-efi-20230328^git20240520.c134e61-2.el10_0 epel10.0-signing-pending ngompa cargo2rpm-0.1.16-3.el10_0 epel10.0-signing-pending decathorpe kiwi-10.1.3-1.el10_0 epel10.0-signing-pending ngompa rust-packaging-26.3-1.el10_0 epel10.0-signing-pending decathorpe screen-4.9.1-2.el10_0 epel10.0-signing-pending jridky kf5-bluez-qt-5.115.0-1.el9 epel9-signing-pending tdawson kf5-libkipi-23.08.5-1.el9 epel9-signing-pending tdawson
I believe they are all harmless since 8 were released or other 2 superseded:
$ for i in $(signing-queues | /usr/bin/hwk -w head); do echo -ne "$i\t"; koji buildinfo $i | grep Tags ; done rust-bootupd-0.2.24-1.fc41 Tags: coreos-pool f41 f41-signing-pending kwin-6.0.4.1-3.fc40 Tags: f40-updates f40-signing-pending btrfs-efi-20230328^git20240520.c134e61-1.el10_0 Tags: epel10.0-signing-pending btrfs-efi-20230328^git20240520.c134e61-2.el10_0 Tags: epel10.0 epel10.0-signing-pending cargo2rpm-0.1.16-3.el10_0 Tags: epel10.0 epel10.0-signing-pending kiwi-10.1.3-1.el10_0 Tags: epel10.0-signing-pending rust-packaging-26.3-1.el10_0 Tags: epel10.0 epel10.0-signing-pending screen-4.9.1-2.el10_0 Tags: epel10.0 epel10.0-signing-pending kf5-bluez-qt-5.115.0-1.el9 Tags: epel9 epel9-testing-pending epel9-signing-pending kf5-libkipi-23.08.5-1.el9 Tags: epel9 epel9-testing-pending epel9-signing-pending
but it is confusing for them to remain so could they please be untagged from the sign-pending tags? Thanks
Metadata Update from @patrikp: - Issue assigned to patrikp
Metadata Update from @kevin: - Issue tagged with: low-gain, low-trouble
Metadata Update from @patrikp: - Assignee reset
I think at present I see these 4 still there:
rust-bootupd-0.2.24-1.fc41 f41-signing-pending siosm kwin-6.0.4.1-3.fc40 f40-signing-pending farchord kf5-bluez-qt-5.115.0-1.el9 epel9-signing-pending tdawson kf5-libkipi-23.08.5-1.el9 epel9-signing-pending tdawson
Should we process them manually?
I re-tagged the 4 builds into the same tags they were in previously.
The hypothesis here is that something happened and robosignatory didn't get the message that they needed to be processed.
It seems like it helped, for example:
$ koji list-history --build rust-bootupd-0.2.24-1.fc41
Tue Apr 29 13:29:13 2025 rust-bootupd-0.2.24-1.fc41 re-tagged into f41-signing-pending by patrikp
Tue Apr 29 13:30:17 2025 rust-bootupd-0.2.24-1.fc41 untagged from f41-signing-pending by autosign/autosign02.iad2.fedoraproject.org
Tue Apr 29 13:30:17 2025 rust-bootupd-0.2.24-1.fc41 tagged into f41-updates-testing-pending by autosign/autosign02.iad2.fedoraproject.org [still active]
Alright, seeing how the EPEL builds were already tagged into epel9 I went ahead and untagged the rest. Now the for cycle returns nothing (by chance, no other builds are getting signed at this time but none are stuck there) and:
$ koji list-tags --build kf5-libkipi-23.08.5-1.el9 epel9
$ koji list-tags --build kf5-libkipi-23.08.5-1.el9
$ kf5-bluez-qt-5.115.0-1.el9 epel9
$ kf5-bluez-qt-5.115.0-1.el9
So I think we're all good. :thumbsup:
Metadata Update from @patrikp: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.