Re: bin-NMU scheduling for python transition
On Sun, 20 Aug 2006, Steve Langasek wrote:
> > ruledispatch (python-dispatch)
> > pyprotocols (python-protocols)
> > turbojson (python-turbojson)
> > turbogears (python-turbogears)
> > This last one is in experimental, so I'm not sure a binNMU scheduled by
> > the Release Team is possible, so if a different action on my part (such
> > as a manual binNMU or a sourceful upload) is required, please let me
> > know.
> turbojson and turbogears are arch: all packages and cannot be binNMUed. It
> also doesn't look like they need to be -- they depend on python (>= 2.4) |
> python2.4, which is satisfied just fine.
> The other two packages are arch: any and so can be binNMUed, but I'm puzzled
> why they build-depend on python-all-dev if they only build for the current
> version of python. Perhaps this is something you would like to fix with a
> sourceful upload?
There's nothing to fix. I re-built the packages here and they get the
correct dependency. I think that the packages have initially been built on
a broken sid system with a bad dh_python. The current packages despite
their strict dependencies provide the modules for both versions of python.
Please go ahead with the bin-NMU on ruledispatch and pyprotocols.
Premier livre français sur Debian GNU/Linux :