Bug#557293: polybori: FTBFS without Python 2.4

Package: polybori Version: 0.5~rc1-2 Severity: important User: debian-python@lists.debian.org Usertags: python2.6 ftbfs polybori hardcodes Python version it uses at build time in python-polybori.install, despite have a build-depends on python-all-dev. This means that polybori will fail to build on

Bug#557288: libkml: manipulates site-packages/ directly, failing with Python 2.6

Package: libkml Version: 1.0.1-3 Severity: important User: debian-python@lists.debian.org Usertags: python2.6 ftbfs Package fails to build from source with python2.6, here's the build log tail: | # removes build-time rpaths | for version in python2.5 python2.4; \ | do \ | chrp

backporting Python 2.6

Hi, while trying to backport Python 2.6 to Lenny, I discovered that it conflicts with python-xml, which is required by several other packages in conjunction with earlier versions of Python. I don't understand why this module has to conflict, though, but rather see this conflict as an artifact of

Zope 2.12 now requires Python 2.6

Hi, while I was trying to play with the upcoming Plone 4.0, which is technically vastly different from earlier releases, I found out that recent versions, or at least trunk, of Zope 2.12, appears to absolutely require Python 2.6. Or at least that's the way Andreas Jung, the Zope2 release manager,