From Fedora Project Wiki
(initial page creation, based on Fedora_12_Mass_Rebuild)
 
(→‎Schedule: not a provenpackager yet)
Line 20: Line 20:
FIXME
FIXME


Note: dmalcolm intends to babysit and fix packages that don't rebuild.  However, [https://fedorahosted.org/fesco/ticket/415 his proven packager status is pending]  This is a blocker for the mass rebuild.


<!--
=== Opting Out ===
=== Opting Out ===
<!-- Release Engineering has given maintainers the ability to
Release Engineering has given maintainers the ability to
opt out of the scripted rebuild in order to do the build on their own.
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
Note that every single package needs to be rebuilt, regardless of the
Line 41: Line 43:
multiple attempts to build something that fails for one reason or
multiple attempts to build something that fails for one reason or
another. -->
another. -->
FIXME


== Scripts ==
== Scripts ==

Revision as of 23:54, 8 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

FIXME

Note: dmalcolm intends to babysit and fix packages that don't rebuild. However, his proven packager status is pending This is a blocker for the mass rebuild.


Scripts

FIXME

Maintainer Actions

FIXME

Frequently Asked Questions

FIXME

Feedback

Questions/comments/concerns should be directed to fedora-devel-list, the discussion page, or #fedora-devel on freenode IRC.