update from python2.5.1 rc1 to 2.5.1 for feisty

Bug #107525 reported by Matthias Klose
10
Affects Status Importance Assigned to Milestone
python2.5 (Ubuntu)
Fix Released
Undecided
Matthias Klose

Bug Description

Binary package hint: python2.5

feisty ships with python2.5.1 rc1; on Apr 18 the 2.5.1 final version is released, reverting two changes to restore the behaviour from the 2.5 release. The final 2.5.1 release should go to feisty-updates so that this version is compatible with the version from edgy and with the upstream release.

- the source packages python-profiler and python-stdlib-extensions didn't see any changes except the version bump to 2.5.1
- the source package python-defaults bumps the version and depends on the python2.5 packages of the final 2.5.1. release.

python2.5 (2.5.1-0ubuntu1) feisty-proposed; urgency=low

  * Python-2.5.1 release; changes compared to the release candidate:
    - SF #1701207: svnversion_init assertion failed; revert bogus asserts
      (added to the wrong place) from rev 52501.
    - Revert SF #1615701 (rev 53655): dict.update() does *not* call
      __getitem__() or keys() if subclassed. This is to remain consistent
      with 2.5.
    - Revert 53667, bypass set specific optimizations for set and frozenset
      subclasses. This is to remain consistent with 2.5.
    - Describe undocumented third argument to touchline()
  * Regenerate the documentation.

 -- Matthias Klose <email address hidden> Wed, 18 Apr 2007 16:01:10 +0200

The debdiffs (for python2.5 without the regenerated documentation tarball) can be found at

http://people.ubuntu.com/~doko/tmp/python2.5/python2.5.debdiff
http://people.ubuntu.com/~doko/tmp/python2.5/python-profiler.debdiff
http://people.ubuntu.com/~doko/tmp/python2.5/python-stdlib-extensions.debdiff
http://people.ubuntu.com/~doko/tmp/python2.5/python-defaults.debdiff

Revision history for this message
Martin Pitt (pitti) wrote :

All of these debdiffs look reasonable. Matthias, thanks for preparing them, please go ahead and upload.

Changed in python2.5:
assignee: nobody → doko
status: Unconfirmed → In Progress
Revision history for this message
Chris Vigelius (chris-vigelius) wrote :

Please increase the importance of this bug because the current state of python-2.5 on feisty breaks the Django tutorial (see http://code.djangoproject.com/ticket/3708). After applying http://people.ubuntu.com/~doko/tmp/python2.5/python2.5.debdiff to the python-2.5 package and rebuilding the package, tutorial can be executed again.

Revision history for this message
Martin Pitt (pitti) wrote :

Accepted into feisty-proposed, please go ahead with QA testing. NB that this does not require no-change uploads to -updates after verification (see updated SRU policy).

Changed in python2.5:
status: In Progress → Fix Committed
Revision history for this message
Eric Walstad (ewalstad) wrote :

For those Django user's that get bitten by this. Until the above changes make it into Feisty, here's a temporary hack to upgrade Feisty to Python2.5.1-final:

[http://code.djangoproject.com/ticket/3708#comment:7]

Revision history for this message
Matthias Klose (doko) wrote : Re: [Bug 107525] Re: update from python2.5.1 rc1 to 2.5.1 for feisty

Eric Walstad schrieb:
> For those Django user's that get bitten by this. Until the above
> changes make it into Feisty, here's a temporary hack to upgrade Feisty
> to Python2.5.1-final:
>
> [http://code.djangoproject.com/ticket/3708#comment:7]

sorry, that recommendation is just crap. those django users should just add
feisty-proposed to their list of archives and help getting this version into
feisty-updates.

Revision history for this message
Matthias Klose (doko) wrote :

checked that all packages are installable and work as expected on i386, amd64 and sparc. real code changes are in the python2.5 package only, reverting the behaviour to the one from the python2.5 release.

Revision history for this message
Michael Vogt (mvo) wrote :

I did a verification for this today.

The new StableReleaseUpdates policy requires that a step-by-step instruction is given to verify the fix, but because the bug was filed before that prolicy was introduced it can be skipped this time.

I installed the updated packages and verified that the python applications we have installed still work as before. This is the case.

I will mark this package "verification-done".

Revision history for this message
Michael Vogt (mvo) wrote :

This can go into -updates

Revision history for this message
Martin Pitt (pitti) wrote :

Copied all four packages from -proposed to -updates.

Changed in python2.5:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.