Your message dated Sun, 21 Jul 2013 23:19:08 +0100
with message-id <1374445148.5881.43.ca...@jacala.jungle.funky-badger.org>
and subject line Re: Bug#710720: transition: libechonest
has caused the Debian Bug report #710720,
regarding transition: libechonest
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 ow...@bugs.debian.org
immediately.)
--
710720: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710720
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian....@packages.debian.org
Usertags: transition
Hi! A new upstream release of libechonest is sitting in experimental and
I would like to push it to unstable.
The only reverse dependency I know of is clementine. I'm sure a binNMU
will surely work in this case, as clementine in experimental was linked
against this new version.
Kinds regards, Lisandro.
Ben file:
title = "libechonest";
is_affected = .depends ~ "libechonest1.2" | .depends ~ "libechonest2.0";
is_good = .depends ~ "libechonest2.0";
is_bad = .depends ~ "libechonest1.2";
-- System Information:
Debian Release: jessie/sid
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.2.21+edid (SMP w/2 CPU cores)
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--- End Message ---
--- Begin Message ---
On Wed, 2013-07-17 at 18:34 -0300, Lisandro Damián Nicanor Pérez Meyer
wrote:
> On Wednesday 17 July 2013 21:34:11 Adam D. Barratt wrote:
> [snip]
> > In sid, yes (I've just asked for the old binary package to be
> > decrufted). There's still a few days before it hits testing though.
>
> My bad, I didn't know that it's marked until it hits testing.
It did now. :-) Therefore closing.
Regards,
Adam
--- End Message ---