Side tags for Python 3.15 (Fedora 45) #13345
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
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
releng/tickets#13345
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
Hi, I need side tags for Python 3.15 rebuild, ideally like that:
_with_bootstrap=1which would tag builds directly into f45-pythonThe idea behind: we've got quite a few packages that require a two-step build, first as bootstrap, then as a final build. We used to do this by submitting patches switching bconds in specfiles, but this arrangement could save us dozens of commits.
Also, please enable signing the packages so that merging the side tag is faster -- we have been bitten by the long signing queue in the past, it would save all of us some trouble.
When do you need this? (2026-05-20 - arbitrary date)
We plan to start rebuild at the beginning of June. It would be nice to be able to test the bootstrap sequence beforehand, hence I set the deadline a few days earlier.
When is this no longer needed or useful?
After the side tag merge (I'll ask for it in a separate issue).
If we cannot complete this, what is the impact? [Dependencies/Blocker]
We would have to defer the Python 3.15 change to a later Fedora release, which hasn't happened so far. We will strive to ship it on time. https://fedoraproject.org/wiki/Changes/Python3.15
Checklist
Hello!
Thanks for opening this request. I have created these tags, please check the info below, in case you need anything more please let me know.
Is i686 missing from arches expected?
Also, is there a way to configure the f45-python-bootstrap target to tag builds automatically to f45-python?
@jnsamyak, hello, could you take a look at Miro's questions? Thank you.
To clarify:
I think I was able to fix this myself:
The second tag exists but has no associated target :/
Could not execute build: Unknown build target: f45-python-bootstrap
Testing some scratchbuilds (which will not verify the tagging but at least the arches).
Apparently, I also needed to run
koji edit-tag -x rpm.macro._with_bootstrap=1 f45-python-bootstrapor else the bootstrap tag hadsidetag_rpm_macros_allowed '_with_bootstrap=1'only.Everything wrt the build targets seems to be in order now.
Except I don't know if autosign was enabled.
infra/ansible#3367
Apoligies, I was on PTO last week, I'll look at it today.