Hello,
The side tag has been merged. Now you can build Python packages in regular Rawhide with Python 3.15 safely. Shortly we'll start opening bugzillas for the remaining packages.
## What now? The usual advice
If you are aware of the problem and working towards fixing it, set your bugzilla to ASSIGNED to avoid further automated reminders. If blocked by dependencies, do not close the bugzillas as NOTABUG or DUPLICATE just because it is "not a problem in your package". The automation will file new ones anyway. Use the Blocks and Depends on fields in bugzilla instead please.
## My package fails to build because it has test failures in %check
Please, try to resolve the failures. If you are confident that the package works fine, but the tests are wrong, skip some failing tests, ideally with a link to an upstream issue. Do not disable (e.g. comment out) all tests just to unblock the rebuild of your package, it usually only hides the problem.
## My package fails to build because it has broken build dependencies
Please try to track the missing build dependencies in Bugzilla. If possible, help the maintainers of your dependencies to get them rebuilt. When in need of escalation, ask us for provenpackager help (ideally with pull requests to be merged). Once possible, rebuild your package. When you do, the bugzilla will eventually get automatically closed, but you can do that manually as well.
## My package was rebuilt with Python 3.15 but it has broken runtime dependencies
Please try to track the missing runtime dependencies in Bugzilla. If possible, help the maintainers of your dependencies to get them rebuilt. When in need of escalation, ask us for provenpackager help (ideally with pull requests to be merged). When the dependencies are rebuilt, your package will install successfully once again and the bugzilla will eventually get automatically closed, but you can do that manually as well.
## My package failed to build but installs just fine
Some packages that only require libpython3.14.so.1.0 will successfully pull in the python3.14 package as a dependency and hence they don't have installation issues. They need to be rebuilt with Python 3.15 anyway, we don't want Fedora users to pull in two Python versions unless they need them for development purposes.
## How to run things locally?
You can use mock. Make sure to: 1. Clear all caches first: $ mock -r fedora-rawhide-x86_64--scrub=all 2. Use the Koji repo: $ mock -r fedora-rawhide-x86_64 --enablerepo=local ...
## Where to get help
Reply to this thread or find us (ksurma, mhroncok) on Matrix (#python:fedoraproject.org).
Happy building, Karolina