Package: python-twisted-web
Version: 12.0.0-1
Severity: minor

Well -- the bugreport could be loughed at, but to verify some compatibility I
wanted to have python2.3 installed from snapshot.debian.org.  Apparently
python-twisted-web has a good memory of those times and still conflicts
with  python2.3-* packages.  as far as I see it -- there should be no
reason for this conflict:

> dpkg -L python-twisted-web | grep '2\.3'
> dpkg -c /tmp/python2.3_2.3.5-16_amd64.deb | grep -v '2\.3'
drwxr-xr-x root/root         0 2006-10-18 19:58 ./           
drwxr-xr-x root/root         0 2006-10-18 19:58 ./usr/
drwxr-xr-x root/root         0 2006-10-18 19:58 ./usr/lib/
drwxr-xr-x root/root         0 2006-10-18 19:58 ./usr/share/
drwxr-xr-x root/root         0 2006-10-18 19:58 ./usr/share/doc/
drwxr-xr-x root/root         0 2006-10-18 19:58 ./usr/share/man/
drwxr-xr-x root/root         0 2006-10-18 19:58 ./usr/share/man/man1/
drwxr-xr-x root/root         0 2006-10-18 19:58 ./usr/share/pixmaps/
drwxr-xr-x root/root         0 2006-10-18 19:58 ./usr/share/binfmts/
drwxr-xr-x root/root         0 2006-10-18 19:58 ./usr/share/menu/
drwxr-xr-x root/root         0 2006-10-18 19:58 ./usr/bin/
drwxr-xr-x root/root         0 2006-10-18 19:58 ./etc/

doesn't look like anything should conflict

-- System Information:
Debian Release: 7.0
  APT prefers testing
  APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental'), (100, 
'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-4-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 python-twisted-web depends on:
ii  python               2.7.3-13
ii  python-twisted-core  12.0.0-1
ii  python2.6            2.6.8-1.1
ii  python2.7            2.7.4~rc1-3

python-twisted-web recommends no packages.

python-twisted-web suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to