Package: python-support
Version: 1.0.7
Severity: normal

I have debian/pyversions set to 2.6- and am building two binaries out of the 
same source, both of which contain both private modules and scripts. The 
Depends-lines for both packages start with ${python:Depends}. The first
package ends up with "Depends: python2.6", which is correct. The second one
gets "python (>= 2.6) | python2.6" which obviously isn't correct (it does not
guarantee the availability of /usr/bin/python2.6 which the scripts have as the
interpreter).

The package I'm working on isn't yet available in Debian, but a version which
triggers this behavior is available at http://viiru.iki.fi/debian/bcfg2/

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.33.1 (SMP w/2 CPU cores; PREEMPT)
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 python-support depends on:
ii  dpkg                          1.15.5.6   Debian package management system
ii  python                        2.5.4-9    An interactive high-level object-o

python-support recommends no packages.

python-support suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to