Bug#597342: debhelper: building and installing with all python versions should not be done for arch: all packages
Raphaël Hertzog
Version: 8.0.0
Severity: normal
If you build the packages python-django with only python2.6 installed, you
don't get the same result as if you build it when python2.5 and python2.6
are installed... this is because the python buildsystem in debhelper
invokes setup.py once for each version and somehow this leads to modules
being installed in versioned directories when it should not.
As said in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=520834#10
modules should only be built with the current python version. While
distinguishing module and extension is not doable in the generic case,
we know that a source package that builds only arch: all packages can only
build "modules" and not extensions.
So I suggest that we build those only with the current python version.
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (150, 'experimental')
Architecture: i386 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages debhelper depends on:
ii binutils 2.20.1-14 The GNU assembler, linker and bina
ii dpkg-dev 1.15.8.5 Debian package development tools
ii file 5.04-5 Determines file type using "magic"
ii html2text 1.3.2a-15 advanced HTML to text converter
ii man-db 2.5.7-4 on-line manual pager
ii perl 5.10.1-14 Larry Wall's Practical Extraction
ii perl-base 5.10.1-14 minimal Perl system
ii po-debconf 1.0.16 tool for managing templates file t
debhelper recommends no packages.
Versions of packages debhelper suggests:
ii dh-make 0.55 tool that converts source archives
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Piotr Ożarowski
> If you build the packages python-django with only python2.6 installed, you
> don't get the same result as if you build it when python2.5 and python2.6
> are installed... this is because the python buildsystem in debhelper
> invokes setup.py once for each version and somehow this leads to modules
> being installed in versioned directories when it should not.
"versioned directories"? Did you mean shebangs?
> As said in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=520834#10
> modules should only be built with the current python version. While
IMHO we should test them (if other tests are not available, at least by
byte-compiling .py files) at build time with all supported Python
versions. I'm even thinking about making that a requirement in packages
I upload
[...]
> So I suggest that we build those only with the current python version.
what problems do you have with current approach? IIRC debhelper uses
--executable already, so shebangs shouldn't be a problem anymore
--
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