libapache2-mod-wsgi v 3.2-2 attempt to install python3

[Brad Crittenden]

Attempting to install the most recent version of libapache2-mod-wsgi on Maverick attempts to install python3. The dependencies rules clearly attempted to allow it to be installed with python2.6 but fail.

I discussed this with Barry Warsaw and he commented:

"""
The packaging isn't technically broken, but it doesn't conform to the rules
we've established on the debian-python team for specifying Python 2 and Python
3 packages. We decided that we were going to have two separate stacks, but
they've conflated the Python 2 and Python 3 dependencies from this line in the
debian/control file:

Depends: apache2, apache2.2-common, libc6 (>= 2.4), libpython2.6 (>= 2.6), libpython3.1 (>= 3.1), python (>= 2.6), python (<< 3.2)

So given that, it does make sense that installing libapache2-mod-wsgi would
bring in libpython3.1.

What they should have done is created a second binary package for the Python 3
dependent binary. The other issue is the naming convention. Generally we
like things like python-foo and python3-foo for the two separate binaries, so
this package should probably be renamed python-libapache2-mod-wsgi and
python3-libapache2-mod-wsgi.
"""

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: libapache2-mod-wsgi 2.8-2ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
Date: Tue Nov 9 14:11:51 2010
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta i386 (20100901.1)
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: mod-wsgi

[George Politis (gpolitis)]

Is there a workaround we can use?

[George Politis (gpolitis)]

Obviously the workaround here is to remove the libpython3.1 (>= 3.1) and python (<< 3.2) dependencies. I just did that by manually modifying the libapache2-mod-wsgi_3.2-2_i386.deb. I did that using the videbcontrol script described in this post http://ubuntuforums.org/showthread.php?t=636724.

I tested the module using a simple python script and it works fine.

[Chuck Short (zulcss)]

Is this still a problem with natty?

chuck

[Scott Kitterman (kitterman)]

This is fixed. The python3 stuff is in a separate binary.