* Olly Betts <o...@survex.com> [140501 00:02]:
> On Wed, Apr 30, 2014 at 05:09:00PM +0200, Christian Hofstaedtler wrote:
> > I've prepared an NMU for xapian-bindings (versioned as 1.2.17-1.1) and
> > uploaded it to DELAYED/3. Please feel free to tell me if I
> > should delay it longer.
> > 
> > [Chosing 3 days because this affects the ruby1.9.1-rm transition and
> > apparently upcoming ports.]
> 
> A DELAYED/3 NMU for a 4 day old bug seems rather impatient.
> 
> This bug is already on my list to deal with, but I'm a bit backlogged
> after being away last week.  How urgent is this?  I'd rather not have
> to deal with fall-out from a bad NMU on top of everything else I have
> to do.
> 
> I tried to look at the transition tracker to get an idea, but it
> shows xapian-bindings as "good" already:
> 
> https://release.debian.org/transitions/html/ruby1.9.1-rm.html

I don't know why it does that, but it's wrong.

`dak rm -s testing ruby1.9.1` still shows that xapian-bindings would
need to go, but given the list of rdepends it really needs fixing.

Given that the transition tracker is wrong on this, it hasn't been
noticed early enough, and I expect that in 3 days all packages that
would block the removal are at least in sid, plus on their good way
into testing.
IIRC (excluding xapian-bindings) we should reach a "good" state in
jessie on 5th or 6th of May.

If you want, I can certainly cancel the DELAYED upload, but I really
want to see this [the ruby parts] fixed ASAP.

I also certainly see why it'd be better if you'd do the upload
instead of my NMU -- I didn't feel comfortable with the diff.


Thank you,
  -ch

-- 
 ,''`.  Christian Hofstaedtler <z...@debian.org>
: :' :  Debian Developer
`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
  `-

Attachment: pgpeQxO4UYqWt.pgp
Description: PGP signature

Reply via email to