Package: python2.6-dev Version: 2.6.8-1.1 Severity: normal Unlike the python2.7-dev and python3.2-dev packages in wheezy, python2.6-dev does not include a .pc file in /usr/lib/pkgconfig, used by autoconf-based buildsystems to find compilation versions and options.
This means many configure scripts will fail to find python2.6, even when it's installed, which is a bit puzzling when trying to build multi-version python extension packages. I was personally trying to build libguestfs which generates python bindings, and had the build fail silently just for 2.6. Using the 2.7 file as a template should mostly work: I did such a copy manually and things worked mostly fine. -- System Information: Debian Release: 7.2 APT prefers stable APT policy: (700, 'stable'), (650, 'testing'), (500, 'stable-updates') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/6 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages python2.6-dev depends on: ii libpython2.6 2.6.8-1.1 ii libssl-dev 1.0.1e-2 ii python2.6 2.6.8-1.1 Versions of packages python2.6-dev recommends: ii libc6-dev [libc-dev] 2.13-38 python2.6-dev suggests no packages. -- no debconf information
