FWIW, I went ahead and updated upstream to be fully buildable from source (there was a weird thing I was doing with generating source from swig but not distributing swig source... don't ask, I think I was high) but if done properly would have avoided this issue.
Anyway - http://mentors.debian.net/debian/pool/main/p/python-drizzle/python-drizzle_1.0-1.dsc lp:~mordred/debian/sid/python-drizzle/trunk still works. On 12/13/2010 12:59 AM, Monty Taylor wrote: > Hi! > > I cut a new version of python-drizzle upstream, and then made a new > package version. I uploaded the .dsc to mentors: > > http://mentors.debian.net/debian/pool/main/p/python-drizzle/python-drizzle_0.08.3-1.dsc > > Also, the packaging branch I used is at > lp:~mordred/debian/sid/python-drizzle/trunk ... bzr bd should work in > it straight away if you'd prefer touch that. > > In any case- if you can upload to debian for me, that'd be swell. (And > then I'm going to go back and re-org upstream code so that this all > works better - this was definitely caused by a baroque source code > arrangement, actually) > > On 12/12/2010 03:34 PM, Stefano Rivera wrote: >> Package: python-drizzle >> Version: 0.08.2-1 >> Severity: normal >> Tags: patch >> >> Hi, python-drizzle has "2.6" in pyversions, when this should list the >> range of supported versions, preferably open-ended. >> >> This means that python-drizzle won't build for python2.7, should it be >> available. >> >> I suggest (assuming 2.6 is the first supported version by the upstream >> code): >>> 2.6- >> >> SR >> >> -- System Information: >> Debian Release: squeeze/sid >> APT prefers testing >> APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') >> Architecture: amd64 (x86_64) >> >> Kernel: Linux 2.6.32-5-amd64 (SMP w/8 CPU cores) >> Locale: LANG=en_ZA.UTF-8, LC_CTYPE=en_ZA.UTF-8 (charmap=UTF-8) >> Shell: /bin/sh linked to /bin/dash >> >> >> > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
