Your message dated Fri, 11 Dec 2015 12:08:30 +0100
with message-id <[email protected]>
and subject line Re: Bug#807639: nmu: clementine_1.2.3+git1354-gdaddbde+dfsg-1
has caused the Debian Bug report #807639,
regarding nmu: clementine_1.2.3+git1354-gdaddbde+dfsg-1
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 [email protected]
immediately.)
--
807639: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807639
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: [email protected]
Usertags: binnmu
nmu clementine_1.2.3+git1354-gdaddbde+dfsg-1 . ANY . unstable . -m "Rebuild
against libechonest2.3"
Hi!
Due to a transition done wrong, clementine built against libechonest2.1
crashes on startup. This could be fixed by re-uploading a working version
of echonest2.1, but as clementine is its only user, it'd be much less work
to simply transition to libechonest2.3 immediately.
Thus, please rebuild clementine. I tested a local binnmu, it appears to work.
Related bugs: #807629, #807507.
--- End Message ---
--- Begin Message ---
On 11/12/15 07:24, Adam Borowski wrote:
> Package: release.debian.org
> Severity: normal
> User: [email protected]
> Usertags: binnmu
>
> nmu clementine_1.2.3+git1354-gdaddbde+dfsg-1 . ANY . unstable . -m "Rebuild
> against libechonest2.3"
>
> Hi!
> Due to a transition done wrong, clementine built against libechonest2.1
> crashes on startup. This could be fixed by re-uploading a working version
> of echonest2.1, but as clementine is its only user, it'd be much less work
> to simply transition to libechonest2.3 immediately.
>
> Thus, please rebuild clementine. I tested a local binnmu, it appears to work.
>
> Related bugs: #807629, #807507.
And #807509. Let's track this there.
Emilio
--- End Message ---