[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#618805: marked as done (britney2: wrong uninstallable count in some cases? (libebml+libmatroska transition))

Your message dated Fri, 20 May 2011 21:49:46 +0100
with message-id <1305924587.3491.682.camel@hathi.jungle.funky-badger.org>
and subject line Re: Bug#618805: britney2: wrong uninstallable count in some cases? (libebml+libmatroska transition)
has caused the Debian Bug report #618805,
regarding britney2: wrong uninstallable count in some cases? (libebml+libmatroska transition)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
618805: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=618805
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
User: release.debian.org@packages.debian.org
Usertags: britney

Filing in the bts so we don't forget...
This was from the March 16 morning run.

On Wed, Mar 16, 2011 at 11:37:57 +0100, Julien Cristau wrote:

> On Wed, Mar 16, 2011 at 10:23:35 +0000, Release Managers wrote:
> 
> > --- HeidiResult_b1	2011-03-16 10:10:09.000000000 +0000
> > +++ HeidiResult_b2	2011-03-16 10:23:29.000000000 +0000
> > @@ -121224,29 +121224,29 @@
> > -libebml 1.2.0-2 source libs
> > +libebml 0.7.7-3.1 source libs
> 
> Looks like we got ourselves yet another b2 bug...
> 
> b1 does:
> Trying hint from jcristau: libmatroska/1.1.0-2 libebml/1.2.0-2
> leading: libmatroska,libebml
> start: 113+0: i-7:a-2:a-2:i-2:k-45:k-45:m-3:m-2:p-2:s-2:s-1
> orig: 113+0: i-7:a-2:a-2:i-2:k-45:k-45:m-3:m-2:p-2:s-2:s-1
> recur: [] libmatroska,libebml 403/0
> trying: -boost-jam
> skipped: -boost-jam (0 <- 402)
>     got: 31+0: i-31
>     * i386: boost-build
> [...]
> trying: grass
> skipped: grass (360 <- 42)
>     got: 35+0: i-35
>     * i386: grass, grass-dev, libgdal1-1.6.0-grass, libqgis-dev, qgis-plugin-grass
> 
> b2:
> Trying hint from jcristau: libmatroska/1.1.0-2 libebml/1.2.0-2
> leading: libmatroska,libebml
> start: 113+0: i-7:a-2:a-2:i-2:k-45:k-45:m-3:m-2:p-2:s-2:s-1
> orig: 113+0: i-7:a-2:a-2:i-2:k-45:k-45:m-3:m-2:p-2:s-2:s-1
> recur: [] libmatroska,libebml 403/0

b2 believes grass, grass-dev, libgdal1-1.6.0-grass, libqgis-dev,
qgis-plugin-grass are already uninstallable by that point.

> trying: -boost-jam
> skipped: -boost-jam (0 <- 402)
>     got: 36+0: i-36
>     * i386: boost-build
> [...]
> trying: grass
> accepted: grass
>    ori: 113+0: i-7:a-2:a-2:i-2:k-45:k-45:m-3:m-2:p-2:s-2:s-1
>    pre: 382+0: i-35:a-27:a-26:i-26:k-69:k-69:m-27:m-26:p-26:s-26:s-25
>    now: 382+0: i-35:a-27:a-26:i-26:k-69:k-69:m-27:m-26:p-26:s-26:s-25
>    all: libmatroska libebml grass
> 
> i.e. it seems to have a different (broken?) uninstallable count at the
> start of the hint already...
> 
Cheers,
Julien

--- End Message ---
--- Begin Message --- 
On Wed, 2011-05-18 at 19:51 +0100, Adam D. Barratt wrote:
> On Fri, 2011-03-18 at 16:53 +0100, Julien Cristau wrote:
> > b2 believes grass, grass-dev, libgdal1-1.6.0-grass, libqgis-dev,
> > qgis-plugin-grass are already uninstallable by that point.
[...]
> > > i.e. it seems to have a different (broken?) uninstallable count at the
> > > start of the hint already...
> 
> This may (but equally may not) be related to an issue I fixed earlier
> today and pushed as 347022bb01182704cc1976ffb8fd2de916933620.
> Unfortunately I haven't managed to reproduce this particular issue in my
> tests so far, which is making it difficult to confirm whether one of the
> recent fixes may have resolved it.

I managed to reproduce the original issue earlier today, and confirmed
that it reliably occurs with the code from March and never occurs with
the current code.  On that basis, I'm marking this as fixed.

Regards,

Adam

--- End Message ---
Reply to: