Processed: add blocking bugs for gstreamer0.10-rm

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> block 785198 by 785845 785898 785924
Bug #785198 [release.debian.org] transition: GStreamer 0.10 removal
785198 was not blocked by any bugs.
785198 was not blocking any bugs.
Added blocking bug(s) of 785198: 785924, 785845, and 785898
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
785198: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785198
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#806999: transition: clamav

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 806999 + pending
Bug #806999 [release.debian.org] transition: clamav
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
806999: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806999
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Processed: Re: Bug#807089: transition: poppler 0.38

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 807089 - pending
Bug #807089 [release.debian.org] transition: poppler 0.38
Removed tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
807089: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807089
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#807612: jessie-pu: package rsyslog/8.4.2-1+deb8u2

[Michael Biebl]

Package: release.debian.org
Severity: normal
Tags: jessie
User: release.debian@packages.debian.org
Usertags: pu

Hi,

I'd like to make a stable upload for rsyslog in jessie to fix a bug in
the imfile module. If more then one file is monitored, rsyslog segfaults
when using the inotify backend (which is used by default).

This issue has been fixed upstream and the fixed version is in
sid/stretch for quite a while.

In http://bugs.debian.org/770998 I was asked if I can pull this fix for
stable.

I cherry-picked the upstream commit and I could confirm that this fixes
the segfault.
Complete debdiff is attached.

Please let me know if I can proceed with the upload so this fix can make
it into 8.3

Regards,
Michael


-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.3.0-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff --git a/debian/changelog b/debian/changelog
index 0b01623..f9a8ae8 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+rsyslog (8.4.2-1+deb8u2) jessie; urgency=medium
+
+  * Fix crash in imfile module when using inotify mode.
+Patch cherry-picked from upstream Git. (Closes: #770998)
+
+ -- Michael Biebl   Thu, 10 Dec 2015 22:20:45 +0100
+
 rsyslog (8.4.2-1+deb8u1) jessie; urgency=medium
 
   * Disable transactions in ompgsql as they were not working properly.
diff --git a/debian/patches/0003-bugfix-imfile-segfault-on-startup-in-inotify-mode.patch b/debian/patches/0003-bugfix-imfile-segfault-on-startup-in-inotify-mode.patch
new file mode 100644
index 000..baae04b
--- /dev/null
+++ b/debian/patches/0003-bugfix-imfile-segfault-on-startup-in-inotify-mode.patch
@@ -0,0 +1,24 @@
+From: Rainer Gerhards 
+Date: Thu, 9 Oct 2014 08:22:39 +0200
+Subject: bugfix imfile: segfault on startup in "inotify" mode
+
+A segfault happened when more than one file was monitored.
+
+(cherry-picked from commit 8bf43525fe1bf08fd542ad054c987ccf7c97616c)
+---
+ plugins/imfile/imfile.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/plugins/imfile/imfile.c b/plugins/imfile/imfile.c
+index d37cb03..1dde52f 100644
+--- a/plugins/imfile/imfile.c
 b/plugins/imfile/imfile.c
+@@ -1093,7 +1093,7 @@ dirsAddFile(int i)
+ 
+ 	if(dir->currMaxFiles == dir->allocMaxFiles) {
+ 		newMax = 2 * allocMaxFiles;
+-		newFileTab = realloc(dirs, newMax * sizeof(dirInfoFiles_t));
++		newFileTab = realloc(dirs->files, newMax * sizeof(dirInfoFiles_t));
+ 		if(newFileTab == NULL) {
+ 			errmsg.LogError(0, RS_RET_OUT_OF_MEMORY,
+ 	"cannot alloc memory to map directory '%s' file relationship "
diff --git a/debian/patches/series b/debian/patches/series
index 8351e07..b0c49c1 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,2 +1,3 @@
 0001-Don-t-create-a-database.patch
 0002-bugfix-ompgsql-transaction-were-improperly-handled.patch
+0003-bugfix-imfile-segfault-on-startup-in-inotify-mode.patch

Bug#806999: marked as done (transition: clamav)

[Debian Bug Tracking System]

Your message dated Fri, 11 Dec 2015 00:34:38 +0100
with message-id <566a0c0e.2080...@debian.org>
and subject line Re: Bug#806999: transition: clamav
has caused the Debian Bug report #806999,
regarding transition: clamav
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.)


-- 
806999: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806999
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: transition
Severity: normal

The version 0.99 of clamav has SONAME bump. Currently we have 0.99-rc2
in experimental which built everywhere (mips is Needs-Build at the time
of writing). 0.99 and -rc2 are almost identical.

The auto tracker is okay, all reverse dependencies are:
- libclamunrar
- c-icap-modules
- dansguardian
- havp
- python-clamav

All packages were build tested in sid-chroot against libclamav7 from
experimental.

In the last c-icap-modules upload (which is part of testing and
unstable) the maintainer forgot to include the .so library that was built
against libclamav-dev and as such the package is listed as `unknown` in the
tracker (which is correct, no libclamav6 dependency). The bug #806757 has
been filled regarding this issue.

libclamunrar needs a source upload because it is has a manual
dependency on libclamav6 (and needs to provide libclamunrar7).

After the upload has migrated to testing we would plan to upload it to
s-p-u and os-p-u so it can pop up in s/updates and os/update. This
unfortunately triggers a transition in stable and oldstable.

Sebastian
--- End Message ---
--- Begin Message ---
On 05/12/15 15:35, Sebastian Andrzej Siewior wrote:
> On 2015-12-04 00:59:02 [+0100], Emilio Pozuelo Monfort wrote:
>>> The auto tracker is okay, all reverse dependencies are:
>>> - libclamunrar
>>> - c-icap-modules
>>> - dansguardian
>>> - havp
>>> - python-clamav
>>>
>>> In the last c-icap-modules upload (which is part of testing and
>>> unstable) the maintainer forgot to include the .so library that was built
>>> against libclamav-dev and as such the package is listed as `unknown` in the
>>> tracker (which is correct, no libclamav6 dependency). The bug #806757 has
>>> been filled regarding this issue.
>>>
>>> libclamunrar needs a source upload because it is has a manual
>>> dependency on libclamav6 (and needs to provide libclamunrar7).
>>
>> Go ahead.
> Thanks.
> Clamav was uploaded and built everywhere (mips64el is Uploaded, sh4
> Need-Builds).
> libclamunrar was uploaded & passed the NEW queue, it should be picked up by
> the buildds soon.

This is over now.

Cheers,
Emilio--- End Message ---

Bug#807621: transition: stk

[Felipe Sateler]

On 10 December 2015 at 20:56, Emilio Pozuelo Monfort  wrote:
> Control: tags -1 confirmed
>
> On 11/12/15 00:44, Felipe Sateler wrote:
>> A transition is needed for stk. I have confirmed that both rdeps, csound
>> and lmms, build with the new version that I am about to upload. The
>> package has already gone through binNEW and is in experimental.
>
> Go ahead.

Thanks. Uploaded


-- 

Saludos,
Felipe Sateler

Bug#807621: transition: stk

[Felipe Sateler]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition

Hi,

A transition is needed for stk. I have confirmed that both rdeps, csound
and lmms, build with the new version that I am about to upload. The
package has already gone through binNEW and is in experimental.


Ben file:

title = "stk";
is_affected = .depends ~ "libstk0v5" | .depends ~ "libstk-4.5.0";
is_good = .depends ~ "libstk-4.5.0";
is_bad = .depends ~ "libstk0v5";


-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Processed: Re: Bug#807621: transition: stk

[Debian Bug Tracking System]

Processing control commands:

> tags -1 confirmed
Bug #807621 [release.debian.org] transition: stk
Added tag(s) confirmed.

-- 
807621: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807621
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#807621: transition: stk

[Emilio Pozuelo Monfort]

Control: tags -1 confirmed

On 11/12/15 00:44, Felipe Sateler wrote:
> A transition is needed for stk. I have confirmed that both rdeps, csound
> and lmms, build with the new version that I am about to upload. The
> package has already gone through binNEW and is in experimental.

Go ahead.

Emilio

Bug#807514: marked as done (nmu: lush and tulip)

[Debian Bug Tracking System]

Your message dated Thu, 10 Dec 2015 11:03:52 +0100
with message-id <56694e08.6010...@debian.org>
and subject line Re: Bug#807514: nmu: lush and tulip
has caused the Debian Bug report #807514,
regarding nmu: lush and tulip
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.)


-- 
807514: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807514
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: binnmu

please binNMU lush and tulip, using binutils 2.25.90.20151209.
--- End Message ---
--- Begin Message ---
On 09/12/15 23:34, Matthias Klose wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: binnmu
> 
> please binNMU lush and tulip, using binutils 2.25.90.20151209.

Scheduled.

Cheers,
Emilio--- End Message ---

Bug#807576: jessie-pu: package arb/6.0.2-1+deb8u1

[Adam D. Barratt]

On 2015-12-10 13:28, Andreas Beckmann wrote:

The maintainer Andreas Tille has acked the patch
and will perform a maintainer upload, so you won't see the "NMU" bits 
in

the uploaded package.


He already did, before you filed this bug. If he hadn't then I'd 
probably have asked for a more useful changelog entry.


Regards,

Adam

Bug#798999: marked as done (transition: python3.5 supported)

[Debian Bug Tracking System]

Your message dated Thu, 10 Dec 2015 18:33:28 +0100
with message-id <5669b768.8000...@debian.org>
and subject line Re: Bug#798999: transition: python3.5 supported
has caused the Debian Bug report #798999,
regarding transition: python3.5 supported
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.)


-- 
798999: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798999
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

Here's what I sent to debian-python about this transition:

"""
It seems very likely that we'll want to release Stretch with python3.5 as the
default and only python3 version.  To do that, we'll need three transitions
for python3 extensions (arch all python3 modules don't (with one exception)
need to be touched for these transitions):

1.  Add python3.5 as a supported python3 version (there is a python3-defaults
in experimental that has this enabled for testing).  This involves rebuilding
all extensions that build-dep on python3-all-dev to support python3 3.4 and
3.5.

2.  Make python3.5 the default python3 version.  Rebuild extensions that
build-dep on python3-dev.

3.  Drop python3.4 as a supported python3 version.  This involved rebuilding
the same packages as the first one.

For packages that build fine with python3.5, there should be nothing required
from a maintainer point of view.  Except pycxx this can all be done with
binNMUs.  Ubuntu has already done this transition and has patches for a number
of packages that may be of assistance when working through issues.

Python3 3.5.0-1 is in unstable.  I'm going to ask the release team for
permission to start the first transition once it gets to testing.  The only
impact (other than the aforementioned python3.5 specific build issues) will be
transient build-dep uninstallabliity in the higher levels of the transition
stack until the lower levels are rebuilt.
"""

Here's my attempt at a ben file for the first transition:

Ben file:

title = "python3.5 supported";
is_affected = .build-depends ~ "python3-all-dev";
is_good = .depends ~ /python3 \(<< 3\.6/;
is_bad = .depends ~ /python3 \(<< 3\.5/;

I would appreciate it if you would go ahead and publish it and then with your
permission, I'll coordinate binNMUs as I've done in the past for python
transitions.

Scott K
--- End Message ---
--- Begin Message ---
On 20/11/15 00:52, Scott Kitterman wrote:
> I don't. I've been short on Debian time recently, so I haven't been able to 
> do much on this.  I should be able to soon.

Let's close this for now, as python3.5 is supported. Please open a new bug for
the default switch when you're ready.

Cheers,
Emilio--- End Message ---

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 800509 + confirmed
Bug #800509 [release.debian.org] transition: llvm-toolchain-3.6
Added tag(s) confirmed.
> tags 796668 + confirmed
Bug #796668 [release.debian.org] transition: log4cplus
Added tag(s) confirmed.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
796668: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796668
800509: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800509
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#797074: transition: libical

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo
Bug #797074 [release.debian.org] transition: libical
Added tag(s) moreinfo.

-- 
797074: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797074
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#797074: transition: libical

[Emilio Pozuelo Monfort]

Control: tags -1 moreinfo

On 01/11/15 12:15, Emilio Pozuelo Monfort wrote:
> On 27/08/15 19:43, Andreas Henriksson wrote:
>> Hello Julien Cristau.
>>
>> Thanks for your quick reply.
>>
>> On Thu, Aug 27, 2015 at 06:17:22PM +0200, Julien Cristau wrote:
>>> I'd prefer to fix the root cause and start by making sure no accidental
>>> ABI breakage like this happens again.  Then we can talk about whether
>>> the ABI is the libical1a one or something else.
>>
>> I'd like to avoid being held responsible for the root cause of this as
>> it's a sin from the past (see comment #27 in bug #773916), but I've
>> added a check to avoid having the next person fall into the same
>> pitfall Hopefully this is good enough for now? (See below.)
> 
> I guess... Can you please let upstream know about this so it doesn't happen 
> again?
> 
> Please upload to experimental and let us know when it has cleared NEW.

...and remove the moreinfo tag when that happens.

Emilio

Processed: add blockers for python-support removal

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # those are only the opened bugs, there should be no more.
> # 
> https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=pysupport-deprecation;users=debian-pyt...@lists.debian.org
> block 746741 by 785949 785968 785987 785990 785991 785993 785995 785998 
> 785999 786009 786014 786019 786025 786026 786032 786037 786041 786042 786044 
> 786048 786054 786061 786065 786071 786074 786077 786078 786083 786086 786090 
> 786093 786094 786096 786100 786101 786109 786111 786113 786116 786118 786120 
> 786126 786131 786133 786134 786138 786141 786144 786145 786148 786149 786150 
> 786155 786158 786163 786165 786166 786173 786178 786179 786183 786184 786190 
> 786192 786194 786197 786198 786201 786209 786213 786221 786222 786227 786228 
> 786229 786230 786241 786251 786257 786258 786259 786265 786266 786267 786282 
> 786287 786311 786316 786317 786318 786335 786365 798477 798478
Bug #746741 [release.debian.org] transition: python-support removal
746741 was not blocked by any bugs.
746741 was not blocking any bugs.
Added blocking bug(s) of 746741: 786150, 786145, 785991, 786257, 786227, 
786148, 786183, 785987, 798478, 786365, 786026, 786109, 785990, 786113, 786209, 
786126, 786311, 786138, 786287, 786141, 786144, 786111, 786101, 786074, 786116, 
786009, 785999, 786083, 785998, 786019, 785968, 786014, 786201, 786230, 786025, 
786149, 786194, 786266, 786065, 786318, 785949, 786165, 786042, 786166, 786158, 
786335, 786041, 786090, 786265, 786131, 786037, 786048, 786251, 786078, 786213, 
786086, 786222, 786221, 798477, 785993, 786163, 786198, 786178, 786190, 786173, 
786093, 786044, 786184, 786100, 786032, 786118, 786258, 786133, 785995, 786228, 
786155, 786134, 786061, 786077, 786179, 786120, 786259, 786192, 786316, 786094, 
786096, 786282, 786197, 786267, 786317, 786229, 786241, 786071, and 786054
> --
Stopping processing here.

Please contact me if you need assistance.
-- 
746741: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746741
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#807576: jessie-pu: package arb/6.0.2-1+deb8u1

[Andreas Beckmann]

Package: release.debian.org
Severity: normal
Tags: jessie
User: release.debian@packages.debian.org
Usertags: pu

arb FTBFS in jessie due to an overly strict gcc version check: arb only
knows about versions up to 4.9.1 while jessie has 4.9.2. For sid the
version check has been disabled, a change I'd like to backport to
jessie.

debdiff is attached. The maintainer Andreas Tille has acked the patch
and will perform a maintainer upload, so you won't see the "NMU" bits in
the uploaded package.


Andreas
diff -Nru arb-6.0.2/debian/changelog arb-6.0.2/debian/changelog
--- arb-6.0.2/debian/changelog	2014-09-09 09:12:14.0 +0200
+++ arb-6.0.2/debian/changelog	2015-12-09 07:32:10.0 +0100
@@ -1,3 +1,14 @@
+arb (6.0.2-1+deb8u1) jessie; urgency=medium
+
+  [ Andreas Beckmann ]
+  * Non-maintainer upload.
+
+  [ Andreas Tille ]
+  * Skip compiler version check at all
+Closes: #793187
+
+ -- Andreas Beckmann   Wed, 09 Dec 2015 07:30:47 +0100
+
 arb (6.0.2-1) unstable; urgency=medium
 
   [ Andreas Tille ]
diff -Nru arb-6.0.2/debian/patches/70_skip_compler_version_check.patch arb-6.0.2/debian/patches/70_skip_compler_version_check.patch
--- arb-6.0.2/debian/patches/70_skip_compler_version_check.patch	1970-01-01 01:00:00.0 +0100
+++ arb-6.0.2/debian/patches/70_skip_compler_version_check.patch	2015-12-09 07:30:36.0 +0100
@@ -0,0 +1,32 @@
+Description: Skip compiler version check at all
+Author: Andreas Tille 
+Bug-Debian: http://bugs.debian.org/793187
+Last-Update: Wed, 22 Jul 2015 22:45:32 +0200
+
+--- a/Makefile
 b/Makefile
+@@ -736,23 +736,7 @@ check_same_GCC_VERSION:
+ 		$(ARBHOME)/SOURCE_TOOLS/check_same_compiler_version.pl $(COMPILER_NAME) $(COMPILER_VERSION_ALLOWED)
+ 
+ check_GCC_VERSION:
+-		@echo 'Compiler version check:'
+-ifeq ('$(COMPILER_VERSION_ALLOWED)', '')
+-		@echo "  - Your compiler is '$(COMPILER_NAME)' version '$(COMPILER_VERSION)'"
+-		@echo 'This version is not in the list of supported $(COMPILER_NAME)-versions:'
+-		@$(foreach version,$(ALLOWED_COMPILER_VERSIONS),echo '* $(version)';)
+-		@echo '  - You may either ..'
+-		@echo '- add your version to ALLOWED_$(COMPILER_NAME)_VERSIONS in the Makefile and try it out or'
+-		@echo '- switch to one of the allowed versions (see arb_README_gcc.txt for installing'
+-		@echo '  a different version of gcc)'
+-		@echo ''
+-		@false
+-else
+-		@echo "  - Supported $(COMPILER_NAME) version '$(COMPILER_VERSION_ALLOWED)' detected - fine!"
+-		@echo ''
+-		$(MAKE) check_same_GCC_VERSION
+-
+-endif
++		@echo 'Skip compiler version check in Debian - we need to fix the code if it does not work'
+ 
+ #-- check ARBHOME
+ 
diff -Nru arb-6.0.2/debian/patches/series arb-6.0.2/debian/patches/series
--- arb-6.0.2/debian/patches/series	2014-09-07 22:38:14.0 +0200
+++ arb-6.0.2/debian/patches/series	2015-12-09 07:30:36.0 +0100
@@ -4,3 +4,4 @@
 40_upstream_r12815__lintian_spelling
 50_private_nameservers
 60_use_packaged_phyml
+70_skip_compler_version_check.patch

Processed: Re: Bug#804246: transition: gsl

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 804246 + pending
Bug #804246 [release.debian.org] transition: gsl
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
804246: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804246
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#807639: nmu: clementine_1.2.3+git1354-gdaddbde+dfsg-1

[Adam Borowski]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
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.