Line 83: | Line 83: | ||
== Maintainer Actions == | == Maintainer Actions == | ||
Hopefully none: dmalcolm will do the rebuild and will attempt to fix anything that breaks. If larger issues arise, he may file bugs | |||
* Maintainers can help this effort by ensuring '''rpmdev-bumpspec''' correctly bumps your package's spec files. | * Maintainers can help this effort by ensuring '''rpmdev-bumpspec''' correctly bumps your package's spec files. | ||
* Maintainers should ensure that their packages currently build from source. | * Maintainers should ensure that their packages currently build from source. | ||
* Maintainers should ensure that there are no unwanted changes committed to CVS but not built yet. | * Maintainers should ensure that there are no unwanted changes committed to CVS but not built yet. | ||
== Frequently Asked Questions == | == Frequently Asked Questions == |
Revision as of 22:41, 19 July 2010
Goal
The goal is to rebuild every Fedora Python package before the Fedora 14 Feature Freeze (July 27th).
Driving Features
From an RPM metadata perspective, the relevant packages contain:
- various files below /usr/lib{64}/python-2.6, which need to move to /usr/lib{64}/python-2.7
- a
Requires: python(abi) = 2.6
, which must become aRequires: python(abi) = 2.7
From an implementation perspective, the bytecode format for .pyc and .pyo files has changed, and the C ABI for extension modules has likely changed as well, necessitating a recompile of all of these
Schedule
FIXME
Note: dmalcolm intends to babysit and fix packages that don't rebuild. He is a proven packager.
Scripts
FIXME
Maintainer Actions
Hopefully none: dmalcolm will do the rebuild and will attempt to fix anything that breaks. If larger issues arise, he may file bugs
- Maintainers can help this effort by ensuring rpmdev-bumpspec correctly bumps your package's spec files.
- Maintainers should ensure that their packages currently build from source.
- Maintainers should ensure that there are no unwanted changes committed to CVS but not built yet.
Frequently Asked Questions
FIXME
Feedback
Questions/comments/concerns should be directed to fedora-devel-list, the discussion page, or #fedora-devel on freenode IRC.