[HEADS UP] Fedora 41 Python 3.13 rebuilds to start in a side tag
(hopefully) next week
by Karolina Surma
Hello,
To deliver Python 3.13 with Fedora Linux 41, we will run a coordinated
rebuild in a side tag.
https://fedoraproject.org/wiki/Changes/Python3.13
Python 3.13.0b2 is scheduled for Tuesday, Jun 4th 2024.
We hope to start the mass rebuild shortly after it's available.
TL;DR: If you can, for the period of the mass rebuild just don't build
your packages in rawhide.
We will let you know when the side tag rebuild actually starts and when
it is merged and it's safe to build in rawhide with Python 3.13.
Details:
If you see a "Rebuilt for Python 3.13" (or similar) commit in your package,
please don't rebuild it in regular rawhide or another rawhide side tag.
If you need to, please let us know, so we can coordinate.
If you'd like to build a package after we already rebuilt it, you should
be able to build it in the side tag via:
on branch rawhide:
$ fedpkg build --target=f41-python
$ koji wait-repo f41-python --build <nvr>
It takes time to build all the essential packages,
so don't expect all your dependencies to be available right away.
Any attempts to build your packages in the side tag before we do will
likely fail due to missing dependencies.
When in trouble, ask here or on Fedora's Matrix - Fedora Python room
(https://matrix.to/#/#python:fedoraproject.org)
Ping me (ksurma) or Miro (mhroncok) if you need to talk to us.
Builds will appear here:
https://koji.fedoraproject.org/koji/builds?latest=0&tagID=f41-python&orde...
Please avoid any potentially disturbing or major changes in Python
packages until the rebuild is over.
Thanks!
Karolina
5 days, 3 hours
- 1
- 0
are pyproject rpm macros supposed to pick up the license
automatically?
by Felix Schwarz
While I was reviewing python-pypdf [1] I noticed that the produced rpm
(python3-pypdf) does not contain the license file, that is "rpm -q
--licensefiles" comes up empty.
As far as I can tell the package follows the example spec file [2] which does
not feature an explicit %license tag so I guess the %pyproject macros are
supposed to pick these up automatically?
As for python-pypdf, the license file IS present in Python's dist-info directory.
The release tarball uses pyproject.toml with the following line:
license = { file = "LICENSE" }
Am I misunderstanding something here or could this be a shortcoming in the
current macros?
Felix
[1] https://bugzilla.redhat.com/show_bug.cgi?id=2279080
[2]
https://docs.fedoraproject.org/en-US/packaging-guidelines/Python/#_exampl...
6 days, 23 hours
- 3
- 3
- ← Newer
- 1
- Older →