fedpkg request-repo rust-base64-simd didn't create koji tags #13270
Labels
No labels
after freeze
automation
backlog
blocked
change-ack
change-nak
change-noreleng
changes
Closed As
Can't Fix
Closed As
Duplicate
Closed As
Fixed
Closed As
Fixed with Explanation
Closed As
Get back later
Closed As
Grooming
Closed As
Insufficient data
Closed As
Invalid
Closed As
It's all good
Closed As
taiga
Closed As
upstream
day-to-day
dev
docs
easyfix
epel
f26
f27
f28
f29
f30
f31
f32
f33
f34
f35
f36
f37
f38
f39
f40
f41
f42
f43
f44
f45
fedora
groomed
high-gain
high-trouble
in-progress
in-review
investigation
legal
low-gain
low-trouble
mass rebuild
medium-gain
medium-trouble
meeting
mini-initiative
new_artifact
ops
pdc_retirement
rawhide
RCA
review
script
sidetarget
sprint-0
sprint-1
sprint-2
sprint-3
sprint-4
sprint-5
unfrozen
waiting on external
Backlog Status
Needs Review
Backlog Status
Ready
chore
documentation
points
01
points
02
points
03
points
05
points
08
points
13
Priority
High
Priority
Low
Priority
Medium
Sprint Status
Blocked
Sprint Status
Done
Sprint Status
In Progress
Sprint Status
Review
Sprint Status
To Do
Technical Debt
Work Item
Bug
Work Item
Epic
Work Item
Spike
Work Item
Task
Work Item
User Story
No milestone
No project
No assignees
5 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
releng/tickets#13270
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Describe the issue
I requested a repo for rust-base64-simd, and over an hour later Koji still does not know about this package
When do you need this? (YYYY/MM/DD)
2026/03/20
When is this no longer needed or useful? (YYYY/MM/DD)
N/A
If we cannot complete this, what is the impact? [Dependencies/Blocker]
Blocks updating rust-coreutils, an approved F44 change
Checklist
The reason this happened is that there was a unretirement request in the fedora-scm-requests pagure and it couldn't handle it, so it crashed.
We should make the koji_sync_listener able to handle this case.
The payload of the message that broke it:
The traceback:
We should fix this before unretirement processing is made live.
FYI, I dropped that message from the queue and it's processing again for now.
I looked at the code and I think there are 2 ways to fix this:
koji_sync_listenerto look for the package name in"name"instead of"repo"when it's an unretirement requestfedpkgto use arepokey instead of anamekey when creating the ticket, like all the other requests.I would prefer option 2, but I'm not certain whether that would break other listeners of these unretirement requests.
@james commited a small workaround in
infra/ansible@b17170efc7I guess a question is if koji_sync_listener needs to act on unretirement messages at all?
CC: @amedvede ^^
I checked the traceback of the error, and it seems that the main purpose of the script is called on closing fedora-scm-requests is that which calls this script and it syncs ownership of the package to koji. Hmm, it probably should react on the unretirement ticket if the project was orphaned and we unorphan it. Does it seem reasonable @kevin? If so, I'll probably rename the variable that is used in the request.
Otherwise,
rust-base64-simdpackage now exists on koji, so probably this ticket can be closed, and it will be good to create a new one for renaming the variable.@amedvede wrote in #13270 (comment):
Yes, on unretirement it should unblock the package and then also assign it to the new owner in koji.
rust-base64-simdnow exists on koji, so closing this ticket. Thekeyproblem is that the payload will be discussed in the following ticket #13364