--- Begin Message ---
Package: release.debian.org
Severity: normal
Tags: wheezy
User: release.debian.org@packages.debian.org
Usertags: pu
Hi,
There is a serious bug in Wheezy that breaks the upgrade of python2.7. Every
person that tries to upgrade python2.7 from version 2.7.3-6 to 2.7.3-6+deb7u2,
will have the following error:
--
Preconfiguring packages ...
(Reading database ... 193624 files and directories currently installed.)
Preparing to replace libpython2.7 2.7.3-6 (using
..../libpython2.7_2.7.3-6+deb7u2_amd64.deb) ...
Unpacking replacement libpython2.7 ...
Preparing to replace python2.7 2.7.3-6 (using
..../python2.7_2.7.3-6+deb7u2_amd64.deb) ...
Unpacking replacement python2.7 ...
dpkg: error processing
/var/cache/apt/archives/python2.7_2.7.3-6+deb7u2_amd64.deb (--unpack):
trying to overwrite '/usr/lib/python2.7/lib-dynload/_hashlib.so', which is also
in package python2.7-minimal 2.7.3-6
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Preparing to replace python2.7-minimal 2.7.3-6 (using
..../python2.7-minimal_2.7.3-6+deb7u2_amd64.deb) ...
Unpacking replacement python2.7-minimal ...
Errors were encountered while processing:
/var/cache/apt/archives/python2.7_2.7.3-6+deb7u2_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
dpkg: dependency problems prevent configuration of libpython2.7:
libpython2.7 depends on python2.7 (= 2.7.3-6+deb7u2); however:
Version of python2.7 on system is 2.7.3-6.
--
According to the PTS[0], version 2.7.3-6 was accepted in Wheezy at some point
around January-2013, which (theoretically) means that every person that
installed Wheezy 7.0 (May-2013) and updates today, is affected by this error.
As explained in bug #702005, this is originated because some files were moved
from python2.7-minimal to python2.7 but the corresponding "Replaces" field was
omitted. The bug is currently fixed for testing and unstable with the upload of
version 2.7.3-8, but it has not been backported yet to stable.
I have attached a patch with the fix, which i have cherry-picked from the
maintainer's launchpad[1].
Many thanks to Ian Jackson, who has kindly guided me through this process and
also has offered to sponsor my upload.
Best regards,
Luis.
[0]https://lists.debian.org/debian-devel-changes/2013/01/msg00053.html
[1]http://bazaar.launchpad.net/~doko/python/pkg2.7-debian/revision/100
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores)
diff -u python2.7-2.7.3/debian/control python2.7-2.7.3/debian/control
--- python2.7-2.7.3/debian/control
+++ python2.7-2.7.3/debian/control
@@ -28,7 +28,7 @@
Provides: python2.7-cjkcodecs, python2.7-ctypes, python2.7-elementtree, python2.7-celementtree, python2.7-wsgiref, python2.7-profiler, python2.7-argparse, python-argparse
Conflicts: python-profiler (<= 2.7.1-2)
Breaks: python-virtualenv (<< 1.7.1.2-2~), vim-nox (<< 2:7.3.547-4), vim-gtk (<< 2:7.3.547-4), vim-gnome (<< 2:7.3.547-4), vim-athena (<< 2:7.3.547-4)
-Replaces: python-profiler (<= 2.7.1-2)
+Replaces: python-profiler (<= 2.7.1-2), python2.7-minimal (<< 2.7.3-7~)
Description: Interactive high-level object-oriented language (version 2.7)
Version 2.7 of the high-level, interactive object oriented language,
includes an extensive class library with lots of goodies for
diff -u python2.7-2.7.3/debian/changelog python2.7-2.7.3/debian/changelog
--- python2.7-2.7.3/debian/changelog
+++ python2.7-2.7.3/debian/changelog
@@ -1,3 +1,11 @@
+python2.7 (2.7.3-6+deb7u3) stable; urgency=medium
+
+ * python2.7: Replace python2.7-minimal (<< 2.7.3-7~). This
+ patch addresses the issue outlined in bug #702005, which has been
+ fixed for testing and unstable, but not for stable. Closes: #702005.
+
+ -- Luis Alejandro Martínez Faneyth <luis@huntingbears.com.ve> Sat, 10 May 2014 11:59:21 -0430
+
python2.7 (2.7.3-6+deb7u2) stable-security; urgency=low
* Fix installation of modules in python2.7-minimal, thanks to
diff -u python2.7-2.7.3/debian/control.in python2.7-2.7.3/debian/control.in
--- python2.7-2.7.3/debian/control.in
+++ python2.7-2.7.3/debian/control.in
@@ -28,7 +28,7 @@
Provides: @PVER@-cjkcodecs, @PVER@-ctypes, @PVER@-elementtree, @PVER@-celementtree, @PVER@-wsgiref, @PVER@-profiler, @PVER@-argparse, python-argparse
Conflicts: python-profiler (<= 2.7.1-2)
Breaks: python-virtualenv (<< 1.7.1.2-2~), vim-nox (<< 2:7.3.547-4), vim-gtk (<< 2:7.3.547-4), vim-gnome (<< 2:7.3.547-4), vim-athena (<< 2:7.3.547-4)
-Replaces: python-profiler (<= 2.7.1-2)
+Replaces: python-profiler (<= 2.7.1-2), @PVER@-minimal (<< 2.7.3-7~)
Description: Interactive high-level object-oriented language (version @VER@)
Version @VER@ of the high-level, interactive object oriented language,
includes an extensive class library with lots of goodies for
--- End Message ---
--- Begin Message ---
Hi,
On 2014-05-15 16:37, Luis Alejandro Martínez Faneyth wrote:
There is a serious bug in Wheezy that breaks the upgrade of python2.7.
Every
person that tries to upgrade python2.7 from version 2.7.3-6 to
2.7.3-6+deb7u2,
will have the following error:
This is not quite correct. I could not reproduce the problem upgrading a
fresh
7.4 system to 7.5, nor have I seen it in the wild.
The file lists for 2.7.3-6 and 2.7.3-6+deb7u2 are identical:
$ debdiff python2.7_2.7.3-6_amd64.deb python2.7_2.7.3-6+deb7u2_amd64.deb
File lists identical (after any substitutions)
Only the intermediate package 2.7.3-6+deb7u1, which originated in
stable-security,
contains two files that do not belong to it:
$ debdiff python2.7_2.7.3-6_amd64.deb python2.7_2.7.3-6+deb7u1_amd64.deb
Files in second .deb but not in first
-------------------------------------
-rw-r--r-- root/root /usr/lib/python2.7/lib-dynload/_hashlib.so
-rw-r--r-- root/root /usr/lib/python2.7/lib-dynload/_ssl.so
(Slightly truncated.)
According to the changelog [1] the problem was detected and fixed in
March, so
users upgrading from 2.7.3-6 straight to 2.7.3-6+deb7u2 will not see a
problem.
2.7.3-6+deb7u1 was never released in a DSA or through stable, so I don't
believe
that any real users will have it installed.
Therefore although I see the bug, I don't have any reason to believe it
affects
our users directly.
If you want to pursue a fix for it regardless, the correct place to do
so is in the
Replaces field through stable-security, where the bug was introduced.
Changes in
that suite flow through to stable in due course.
1:
http://metadata.ftp-master.debian.org/changelogs/main/p/python2.7/python2.7_2.7.3-6+deb7u2_changelog
Thanks,
--
Jonathan Wiltshire jmw@debian.org
Debian Developer http://people.debian.org/~jmw
4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51
<directhex> i have six years of solaris sysadmin experience, from
8->10. i am well qualified to say it is made from bonghits
layered on top of bonghits
--- End Message ---