Bug#339211: Intent to NMU on 11/30
On Wed, 30 Nov 2005 16:58:05 +0100, Andreas Rottmann wrote: I agree. I've CC'ed the Maintainers of the remaining reverse depends of libmusicbrainz2, to get feedback. Hopefully the two packages (dcd, libtunepimp) can be rebuilt against libmusicbrainz 2.1. They can, and they were: for dcd see [EMAIL PROTECTED], and libtunepimp is a FP as an outdated version from the experimental distribution was once compiled against libmusicbrainz-2.0, but the version from unstable builds against libmusicbrainz-2.1 for almost four months now. Cheers, Flo signature.asc Description: Digital signature
Bug#339211: Intent to NMU on 11/30
On Tue, Nov 29, 2005 at 12:08:26PM +0100, Florian Ernst wrote: On Tue, Nov 29, 2005 at 12:28:50AM -0800, Steve Langasek wrote: Is there any reason to not simply drop libmusicbrainz-2.0, in favor of the libmusicbrainz-2.1 package that *everything* else in the archive is using? Except for the (broken) dcd package, which still Build-Depends on libmusicbrainz2-dev. However, I already tried building this package with libmusicbrainz4-dev and all seemed to run fine, so this probably isn't an issue at all. Well, dcd doesn't even pick up a binary dependency on musicbrainz, so I was assuming that build-dep was completely spurious. :) There currently seem to not be any python bindings for -2.1, but surely we should just get updated bindings instead of keeping -2.0 around. (And in the process, hopefully dropping python2.1/python2.2 in favor of python2.4...) In fact, this lack of python bindings was the reason for me to favor keeping libmusicbrainz-2.0 for now. On the other hand, upstream reintroduced those binding in their latest release (not yet packaged), so it looks like libmusicbrainz-2.0 won't be needed anymore at all in short time, and when packaging this new release surely older python version support should be dropped in favor of python2.4. Thus, dropping libmusicbrainz-2.0 would only hurt some users and only for short while. Still, right now I intended to stick to a minimal set of changes for an NMU, especially as long as I haven't recieved any feedback from the maintainer regarding the pending adoption... It's my opinion that libmusicbrainz-2.0 is unreleasable whether or not you do this NMU, because it's an obsolete version of the lib that should be removed. So I would definitely recommend that you focus on making python bindings available for -2.1, rather than spending time NMUing -2.0. Cheers, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ signature.asc Description: Digital signature
Bug#339211: Intent to NMU on 11/30
On Wed, Nov 30, 2005 at 05:37:52AM -0800, Steve Langasek wrote: It's my opinion that libmusicbrainz-2.0 is unreleasable whether or not you do this NMU, because it's an obsolete version of the lib that should be removed. So I would definitely recommend that you focus on making python bindings available for -2.1, rather than spending time NMUing -2.0. OK, will do. Cheers, Flo signature.asc Description: Digital signature
Bug#339211: Intent to NMU on 11/30
Steve Langasek wrote: On Tue, Nov 29, 2005 at 12:08:26PM +0100, Florian Ernst wrote: On Tue, Nov 29, 2005 at 12:28:50AM -0800, Steve Langasek wrote: Is there any reason to not simply drop libmusicbrainz-2.0, in favor of the libmusicbrainz-2.1 package that *everything* else in the archive is using? [...] It's my opinion that libmusicbrainz-2.0 is unreleasable whether or not you do this NMU, because it's an obsolete version of the lib that should be removed. So I would definitely recommend that you focus on making python bindings available for -2.1, rather than spending time NMUing -2.0. I agree. I've CC'ed the Maintainers of the remaining reverse depends of libmusicbrainz2, to get feedback. Hopefully the two packages (dcd, libtunepimp) can be rebuilt against libmusicbrainz 2.1. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#339211: Intent to NMU on 11/30
On Mon, Nov 28, 2005 at 10:03:21PM +0100, Florian Ernst wrote: Dear maintainer, as this bug is RC for 11 days now and a simple patch for fixing it is available I intent to NMU this package on Wednesday, the 30th, uploading to DELAYED/7-day. If I don't hear any feedback from you wrt bug#328958 (RFA for libmusicbrainz) I'll use the attached patch, otherwise I'll probably go for Matthias' patch. Is there any reason to not simply drop libmusicbrainz-2.0, in favor of the libmusicbrainz-2.1 package that *everything* else in the archive is using? There currently seem to not be any python bindings for -2.1, but surely we should just get updated bindings instead of keeping -2.0 around. (And in the process, hopefully dropping python2.1/python2.2 in favor of python2.4...) -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ signature.asc Description: Digital signature
Bug#339211: Intent to NMU on 11/30
On Tue, Nov 29, 2005 at 12:28:50AM -0800, Steve Langasek wrote: Is there any reason to not simply drop libmusicbrainz-2.0, in favor of the libmusicbrainz-2.1 package that *everything* else in the archive is using? Except for the (broken) dcd package, which still Build-Depends on libmusicbrainz2-dev. However, I already tried building this package with libmusicbrainz4-dev and all seemed to run fine, so this probably isn't an issue at all. There currently seem to not be any python bindings for -2.1, but surely we should just get updated bindings instead of keeping -2.0 around. (And in the process, hopefully dropping python2.1/python2.2 in favor of python2.4...) In fact, this lack of python bindings was the reason for me to favor keeping libmusicbrainz-2.0 for now. On the other hand, upstream reintroduced those binding in their latest release (not yet packaged), so it looks like libmusicbrainz-2.0 won't be needed anymore at all in short time, and when packaging this new release surely older python version support should be dropped in favor of python2.4. Thus, dropping libmusicbrainz-2.0 would only hurt some users and only for short while. Still, right now I intended to stick to a minimal set of changes for an NMU, especially as long as I haven't recieved any feedback from the maintainer regarding the pending adoption... Cheers, Flo signature.asc Description: Digital signature
Bug#339211: Intent to NMU on 11/30
Dear maintainer,
as this bug is RC for 11 days now and a simple patch for fixing it is
available I intent to NMU this package on Wednesday, the 30th,
uploading to DELAYED/7-day.
If I don't hear any feedback from you wrt bug#328958 (RFA for
libmusicbrainz) I'll use the attached patch, otherwise I'll probably
go for Matthias' patch.
Cheers,
Flo
diff -u libmusicbrainz-2.0-2.0.2/debian/control
libmusicbrainz-2.0-2.0.2/debian/control
--- libmusicbrainz-2.0-2.0.2/debian/control
+++ libmusicbrainz-2.0-2.0.2/debian/control
@@ -8,7 +8,7 @@
Package: libmusicbrainz2-dev
Architecture: any
Section: libdevel
-Depends: libmusicbrainz2c2 (= ${Source-Version}), libc6-dev
+Depends: libmusicbrainz2c2a (= ${Source-Version}), libc6-dev
Provides: libmusicbrainz-dev
Conflicts: libmusicbrainz-dev
Description: Second generation incarnation of the CD Index - development
@@ -17,12 +17,12 @@
.
This package contains the development files (headers, static library).
-Package: libmusicbrainz2c2
+Package: libmusicbrainz2c2a
Architecture: any
Section: libs
Depends: ${shlibs:Depends}
-Conflicts: libmusicbrainz1, libmusicbrainz2
-Replaces: libmusicbrainz2
+Conflicts: libmusicbrainz1, libmusicbrainz2, libmusicbrainz2c2
+Replaces: libmusicbrainz2, libmusicbrainz2c2
Description: Second generation incarnation of the CD Index - library
MusicBrainz indexes both digital compressed audio (MP3/Vorbis) and
digital audio CDs.
diff -u libmusicbrainz-2.0-2.0.2/debian/changelog
libmusicbrainz-2.0-2.0.2/debian/changelog
--- libmusicbrainz-2.0-2.0.2/debian/changelog
+++ libmusicbrainz-2.0-2.0.2/debian/changelog
@@ -1,3 +1,11 @@
+libmusicbrainz-2.0 (2.0.2-12.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Rename libmusicbrainz2c2 to libmusicbrainz2c2a (libstdc++ allocator
+change, closes: #339211).
+
+ -- Florian Ernst [EMAIL PROTECTED] Mon, 28 Nov 2005 18:46:55 +0100
+
libmusicbrainz-2.0 (2.0.2-12) unstable; urgency=low
* libmusicbrainz2c2: Add conflicts, replaces on libmusicbrainz2 (closes:
diff -u libmusicbrainz-2.0-2.0.2/debian/rules
libmusicbrainz-2.0-2.0.2/debian/rules
--- libmusicbrainz-2.0-2.0.2/debian/rules
+++ libmusicbrainz-2.0-2.0.2/debian/rules
@@ -20,6 +20,6 @@
-$(patsubst %,binary/%,$(DEB_PYTHON_REAL_PACKAGES)):: binary/libmusicbrainz2
+$(patsubst %,binary/%,$(DEB_PYTHON_REAL_PACKAGES)):: binary/libmusicbrainz2c2a
-DEB_SHLIBDEPS_INCLUDE := debian/libmusicbrainz2/usr/lib/
-DEB_SHLIBDEPS_LIBRARY_python2.1-musicbrainz := libmusicbrainz2
-DEB_SHLIBDEPS_LIBRARY_python2.2-musicbrainz := libmusicbrainz2
-DEB_SHLIBDEPS_LIBRARY_python2.3-musicbrainz := libmusicbrainz2
+DEB_SHLIBDEPS_INCLUDE := debian/libmusicbrainz2c2a/usr/lib/
+DEB_SHLIBDEPS_LIBRARY_python2.1-musicbrainz := libmusicbrainz2c2a
+DEB_SHLIBDEPS_LIBRARY_python2.2-musicbrainz := libmusicbrainz2c2a
+DEB_SHLIBDEPS_LIBRARY_python2.3-musicbrainz := libmusicbrainz2c2a
reverted:
--- libmusicbrainz-2.0-2.0.2/debian/libmusicbrainz2c2.install
+++ libmusicbrainz-2.0-2.0.2.orig/debian/libmusicbrainz2c2.install
@@ -1 +0,0 @@
-debian/tmp/usr/lib/*.so.*
only in patch2:
unchanged:
--- libmusicbrainz-2.0-2.0.2.orig/debian/libmusicbrainz2c2a.install
+++ libmusicbrainz-2.0-2.0.2/debian/libmusicbrainz2c2a.install
@@ -0,0 +1 @@
+debian/tmp/usr/lib/*.so.*
signature.asc
Description: Digital signature
