Package: ftp.debian.org
X-debbugs-cc: python-imag...@packages.debian.org
I noticed that pillow wasn't migrating to testing supposedly due to bug
709360, however this bug was closed in the version of pillow in sid and
pillow had built successfully on all architectures. So I brought it up
on debian-release and was told it was because the packages from the old
source were still in unstable for some reason.
<plugwash> Britney seems to be confused about bug 709360 when trying to
migrate pillow, can someone take a look?
<adsb> the BTS graph says it affects unstable
<adsb> as a rule of thumb, britney just uses the bug information the BTS
gives her, so it's almost always going to be due to something BTS-side
<adsb> plugwash: I assume the problem is
<adsb> python-imaging | 1.1.7-4 | unstable | source
<adsb> python-imaging | 1.1.7+2.0.0-1.1 | unstable | source, all
<adsb> python-imaging | 2.2.1-2 | unstable | all
<adsb> so the old source probably wants to go away from sid. that's
nothing something we can (or should) do...
<adsb> and it appears the new source doesn't produce all of the same
binary packages, so it won't show up on ftp-master's radar either
<adsb> hmm, actually, they may all be Provided by the new packages, but
dak rm is still sad
<adsb> either way, it needs the package state in unstable resolving, and
then migration should just work[tm]
<plugwash> adsb so what is the next step? file a bug on ftp.debian.org?
<adsb> plugwash: that would probably be best, yeah
So I went to file a rm bug but then things got even weirder. I noticed
that while the pillow source builds the same set of binaries as the last
python-imaging source the old python-imaging source package dropped some
binaries a few versions back but those binaries were not decrufted.
Normally when a source package drops binaries and they have not yet been
decrufted the cruft report lists them along with what is blocking their
removal but in this case when I checked the cruft report I found nothing.
Can you either clean up these dropped packages or explain what is
blocking their cleanup.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
