From Fedora Project Wiki
Line 14: Line 14:
<!-- Given the changes required for the above features and the given
<!-- Given the changes required for the above features and the given
schedules, Release Engineering will be ready to start scripted rebuilds
schedules, Release Engineering will be ready to start scripted rebuilds
on Thursday, July 23rd. All automated rebuilds should be finished prior to the Feature Freeze, which is July 28th.
on Thursday, July 23rd. -->
Any clean-up manual rebuilds should be finished prior to the Alpha Freeze, which is August 4th.


Note that deltarpms will be disabled for the duration of the mass rebuild. -->
All automated rebuilds should be finished prior to the Feature Freeze, which is FIXME
FIXME
 
Any clean-up manual rebuilds should be finished prior to the Alpha Freeze, which is FIXME
 
Note that deltarpms will be disabled for the duration of the mass rebuild.


Note: dmalcolm intends to babysit and fix packages that don't rebuild.  He is a [https://fedorahosted.org/fesco/ticket/415 proven packager].
Note: dmalcolm intends to babysit and fix packages that don't rebuild.  He is a [https://fedorahosted.org/fesco/ticket/415 proven packager].


<!--
He plans to start the scripted rebuild on Wednesday 21st July at noon EDT.
=== Opting Out ===
Release Engineering has given maintainers the ability to
opt out of the scripted rebuild in order to do the build on their own.
Note that every single package needs to be rebuilt, regardless of the
contents.
 
In order to opt out of the scripted rebuild, a maintainer will need to
check a file into their package's devel/ branch, named '''noautobuild'''.
This file should contain a short rationale of why you wish to do the
build yourself.


If the build initiation script encounters such a file, it will skip that
For the sake of simplicity, he does ''not'' plan to provide an "opt out" system for maintainers to do their own rebuilds.
package.  However, given the tight deadlines (Feature freeze being the
28th of July, Alpha Freeze being the 4th of August), a very short grace period will be given for completing
the builds on your own.  If your build has not been attempted by the
1st of August, the script will no longer honor the noautobuild request and
will attempt to rebuild your package.  If, however, a rebuild has been
attempted, the script will bypass your module.  This should prevent
multiple attempts to build something that fails for one reason or
another. -->


== Scripts ==
== Scripts ==

Revision as of 22:45, 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 a Requires: 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

All automated rebuilds should be finished prior to the Feature Freeze, which is FIXME

Any clean-up manual rebuilds should be finished prior to the Alpha Freeze, which is FIXME

Note that deltarpms will be disabled for the duration of the mass rebuild.

Note: dmalcolm intends to babysit and fix packages that don't rebuild. He is a proven packager.

He plans to start the scripted rebuild on Wednesday 21st July at noon EDT.

For the sake of simplicity, he does not plan to provide an "opt out" system for maintainers to do their own rebuilds.

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.

Retrieved from "https://fedoraproject.org/w/index.php?title=Features/Python_2.7/MassRebuild&oldid=187169"