« Return to Thread: Report on the situation of python2.5 in Debian
Re: Report on the situation of python2.5 in Debian
by Josselin Mouette
::
Rate this Message:
Le vendredi 12 octobre 2007 à 22:40 -0700, Steve Langasek a écrit :
> Is there code available that can be used to reproduce this list from
> Packages/Sources? I would very much prefer to be able to generate an
> authoritative list of per-arch binaries that need to be binNMUed, so that
> the progress can be tracked and so we're not needlessly binNMUing packages
> that have sourceful uploads first.
Given the number of packages that don't follow the policy or declare
wrong values in XS-Python-Version, for most packages it was possible to
decide only by looking at debian/rules by hand.
--
.''`.
: :' : We are debian.org. Lower your prices, surrender your code.
`. `' We will add your hardware and software distinctiveness to
`- our own. Resistance is futile.
> Is there code available that can be used to reproduce this list from
> Packages/Sources? I would very much prefer to be able to generate an
> authoritative list of per-arch binaries that need to be binNMUed, so that
> the progress can be tracked and so we're not needlessly binNMUing packages
> that have sourceful uploads first.
Given the number of packages that don't follow the policy or declare
wrong values in XS-Python-Version, for most packages it was possible to
decide only by looking at debian/rules by hand.
--
.''`.
: :' : We are debian.org. Lower your prices, surrender your code.
`. `' We will add your hardware and software distinctiveness to
`- our own. Resistance is futile.
signature.asc (196 bytes) « Return to Thread: Report on the situation of python2.5 in Debian
| Free embeddable forum powered by Nabble | Forum Help |
