$ sudo apt-get install libapache2-mod-wsgi
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
libpython3.1 python3.1 python3.1-minimal
Suggested packages:
python3.1-doc python3.1-profiler binfmt-support
The following NEW packages will be installed:
libapache2-mod-wsgi libpython3.1 python3.1 python3.1-minimal
0 upgraded, 4 newly installed, 0 to remove and 3 not upgraded.
Need to get 6,275kB of archives.
After this operation, 20.9MB of additional disk space will be used.
Do you want to continue [Y/n]?
Why is it wanting to drag down Python 3.1?
Has someone screwed up package in repository or have they done stupid
thing of not naming Python 3.1 variant of package differently.
The person on #python confident they are pointing at non standard repositories.
Graham
:-)
http://ftp.de.debian.org/debian/pool/main/m/mod-wsgi/mod-wsgi_3.3-2.dsc
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.0
Source: mod-wsgi
Binary: libapache2-mod-wsgi, libapache2-mod-wsgi-py3
Architecture: any
Version: 3.3-2
Maintainer: Debian Python Modules Team
<python-mo...@lists.alioth.debian.org>
Uploaders: Bernd Zeimetz <bz...@debian.org>, Piotr Ożarowski <pi...@debian.org>
Homepage: http://www.modwsgi.org/
Standards-Version: 3.9.1
Vcs-Browser: http://svn.debian.org/viewsvn/python-modules/packages/mod-wsgi/trunk/
Vcs-Svn: svn://svn.debian.org/python-modules/packages/mod-wsgi/trunk/
Build-Depends: debhelper (>= 5), python-all-dev, python3-all-dev,
apache2-threaded-dev
Checksums-Sha1:
f32d38e5d3ed5de1efd5abefb52678f833dc9166 117930 mod-wsgi_3.3.orig.tar.gz
152fdee36d3172a44e9c2547e3c5dd60f161f11f 8766 mod-wsgi_3.3-2.diff.gz
Checksums-Sha256:
d96e1078990484cfe5579df1e95dc73f009495e9c3f9a066b0983650bd9e3243
117930 mod-wsgi_3.3.orig.tar.gz
391edefb5b4a35136164462291dce97a69f3fd715dfc46dae9c57c3a119bbc19 8766
mod-wsgi_3.3-2.diff.gz
Files:
6172bb2bbabcd0c25867c2bc06f99dbb 117930 mod-wsgi_3.3.orig.tar.gz
44c3f6fb30ca12b698934e41e010ed4b 8766 mod-wsgi_3.3-2.diff.gz
Per:
http://packages.debian.org/changelogs/pool/main/m/mod-wsgi/mod-wsgi_3.3-2/changelog
I thought that Python 3 was a separate package:
* Move Python 3.X extension to new libapache2-mod-wsgi-py3 binary package
or does it still drag it down and install it?
=
Bernd, Piotr, what is the current situation?
Graham
and is carried over to here
http://packages.ubuntu.com/maverick/libapache2-mod-wsgi
FWIW on my debian testing box, apt-cache show libapache2-mod-wsgi
cynic@debian:~$ apt-cache show libapache2-mod-wsgi
Package: libapache2-mod-wsgi
Priority: optional
Section: httpd
Installed-Size: 416
Maintainer: Debian Python Modules Team
<python-mo...@lists.alioth.debian.org>
Architecture: amd64
Source: mod-wsgi
Version: 3.3-1
Provides: httpd-wsgi
Depends: apache2, apache2.2-common, libc6 (>= 2.3.4), libpython2.6 (>=
2.6), python (>= 2.5), python (<< 2.7)
Suggests: apache2-mpm-worker | apache2-mpm-event
Filename: pool/main/m/mod-wsgi/libapache2-mod-wsgi_3.3-1_amd64.deb
cynic@debian:~$ dpkg -l|grep libpython
ii libpython2.6 2.6.6-8+b1
Shared Python runtime library (version 2.6)
Now, I didn't use the dependency to pull in python. I had python
installed before I asked for mod_wsgi and it seems to be working out
all right with my 2.6 install.
I spun up a fresh vm with a brand new 10.10 64 bit install, when I
install mod_wsgi it is indeed pulling in python3.1.
Python2.6 is already installed. This is not how it worked on the
debian box, so this is most certainly a canonical bug.
The depends line from apt-cache show on the package name indicated it
should be requiring a min version of 2.6.
The way the debian/rules file is written if you do an apt-build on the
package doesn't have obvious (to me) errors.
It looks like ubuntu is tracking the debian package, and this issue
may exist in sid. I can confirm that this is indeed happening and you
may want to get in touch ubuntu-dev...@lists.ubuntu.com
> --
> You received this message because you are subscribed to the Google Groups "modwsgi" group.
> To post to this group, send email to mod...@googlegroups.com.
> To unsubscribe from this group, send email to modwsgi+u...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en.
>
>
--
J.
[¹] http://packages.ubuntu.com/maverick/amd64/libapache2-mod-wsgi/filelist
[²] http://packages.ubuntu.com/maverick/libapache2-mod-wsgi
In Debian Squeeze³ we decided to keep Python 2.X and Python 3.X as
separate runtime systems and thus for public modules we have python-foo
and python3-foo binary packages.
That's why I added libapache2-mod-wsgi-py3 package in 3.3-1 (which
conflicts with libapache2-mod-wsgi so you cannot install both at the
same time).
[³] first Debian stable version that supports Python 3, will be released
in less than 2 weeks, BTW
mod-wsgi was synced from unstable in an unfortunate time and that's why
this problem is affecting Ubuntu only
--
Piotr Ożarowski Debian GNU/Linux Developer
www.ozarowski.pl www.griffith.cc www.debian.org
GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645
What is the result then?
Is it safe to install on Ubuntu, with the caveat that it also drags
down Python 3.1.
In the package it has:
/usr/lib/apache2/modules/mod_wsgi.so
/usr/lib/apache2/modules/mod_wsgi.so-2.6
/usr/lib/apache2/modules/mod_wsgi.so-3.1
Is the mod_wsgi.so a symlink to one or the other, or something else,
like version for Python 2.5?
Graham
Graham Dumpleton wrote:
> What is the result then?
>
> Is it safe to install on Ubuntu, with the caveat that it also drags
> down Python 3.1.
>
> In the package it has:
>
> /usr/lib/apache2/modules/mod_wsgi.so
> /usr/lib/apache2/modules/mod_wsgi.so-2.6
> /usr/lib/apache2/modules/mod_wsgi.so-3.1
>
> Is the mod_wsgi.so a symlink to one or the other, or something else,
> like version for Python 2.5?
/usr/lib/apache2/modules/mod_wsgi.so is a symlink to mod_wsgi.so-2.6,
if someone (insane ;) will change default Python version in Maverick to 3.1,
a hook will change the symlink to point to mod_wsgi.so-3.1 as well
What you can do with it?
* ask Ubuntu guys to upgrade the package, or
* drop 3.1 support in 3.2-2 (by removing line 12 from debian/rules file), or
* accept the fact that python3.1 installation wasted few MiB on your hard drive
(it doesn't harm mod_wsgi as long as you have Python 2.6 set as default)
Okay, great to know. Thanks.
Graham