[Build-common-hackers] Bug#577580: use of cdbs_python_build_versions forbids both arch and indep Python packages from the same source

[Yaroslav Halchenko]

Package: cdbs
Version: 0.4.77
Severity: normal


per Jonas request, filing a fresh bug  report...  two packages of mine FTBFS
using recent cdbs version while they were building just fine using previous
versions.

the reason actually is following code:

/usr/share/cdbs/1/class/python-distutils.mk-$(patsubst %,install/%,$(cdbs_python_indep_packages)) :: install/%: python-install-py
/usr/share/cdbs/1/class/python-distutils.mk-    cd $(DEB_SRCDIR) && python$(cdbs_python_nondefault_version) $(DEB_PYTHON_SETUP_CMD) install --root=$(cdbs_python_destdir) \
/usr/share/cdbs/1/class/python-distutils.mk:        --install-purelib=/usr/lib/python$(cdbs_python_build_versions)/site-packages/ $(DEB_PYTHON_INSTALL_ARGS_ALL)

and that one defined as
                                                                                                             
/usr/share/cdbs/1/class/python-vars.mk-# arch(+indep): all; indep: current if supported, else first supported
/usr/share/cdbs/1/class/python-vars.mk:cdbs_python_build_versions = $(or $(if $(cdbs_python_arch_packages),$(cdbs_python_supported_versions)),$(filter $(cdbs_python_current_version),$(cdbs_python_supported_versions)),$(cdbs_python_first_supported_version))

so now cdbs_python_build_versions (despite having "s" in suffix) is supposed to
have all versions if there is any arch package as well (-lib in my case), for
building indep packages (e.g. python-mvpa), which fails with what you
can observe in original bugreports:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=577312
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=577308

so, if before it was working correctly, now it doesn't (backward
incompatibility).

Yes, someone could call my packaging "dirty" since it got a bit elaborate in an
attempt to allow arch-dependent -lib packages using cdbs.  I am aware of the
fact that it is calling python setup.py install twice (for all supported
versions for arch -lib package, and once for main package for main version),
and such approach worked fine for quite a while.  But I do consider that
the cdbs either needs explicitely to allow for automagic handling of -lib arch
packages or not to rely on the colliding $(cdbs_python_build_versions).

P.S. keeping severity at normal to be raised at the maintainers discretion

Cheers,

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (901, 'unstable'), (900, 'testing'), (300, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.31-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages cdbs depends on:
ii  debhelper                     7.4.15     helper programs for debian/rules

Versions of packages cdbs recommends:
ii  autotools-dev                 20090611.1 Update infrastructure for config.{

Versions of packages cdbs suggests:
ii  devscripts                    2.10.61    scripts to make the life of a Debi
ii  doc-base                      0.9.4      utilities to manage online documen

-- no debconf information