Re: pigment and pigment-python unblocks
* Loïc Minier [Thu, 21 Aug 2008 12:36:21 +0200]:
> Hey
> Summary: I've been away for a little while, and the situation of
> pigment for lenny doesn't look too shiny; I made a couple of uploads to
> address the biggest issues, please consider them for lenny.
> The pigment in testing is 0.3.6-1 and is quite borken: upstream changed
> SONAME but the uploader didn't rename the package. python-pgm was bin
> NMUed to use the new SONAME but it now has an unversionned dependency
> on the old package name.
> The package name was fixed in 0.3.6-2, but without Replaces for
> upgrades from 0.3.6-1; I pushed 0.3.6-3 addressing this yesterday to
> unstable.
> pigment-python in unstable is a new upstream release uploaded the 18th
> of July which updates the bindings to support pigment 0.3.6, I think it
> belongs with this pigment version in testing. I just pushed a new
> pigment-python bumping the bdep appropriately as this was forgotten by
> the uploader of pigment-python 0.3.4.
> (technically, pigment-python was uploaded just before the freeze, but I
> think the arguments given above are more interesting to you.)
> Could you please consider pigment/0.3.6-3 and pigment-python/0.3.4-2?
Both unblocked.
> python-pgm was bin
> NMUed to use the new SONAME but it now has an unversionned dependency
> on the old package name.
Hm, I can't see such binNMU request on -release. Was it on irc or
something?
--
Adeodato Simó dato at net.com.org.es
Debian Developer adeodato at debian.org
Truth is the most valuable thing we have, so let's economize it.
-- Mark Twain
Reply to: