I sort of became the (temporary?) maintainer of libmusicbrainz, so
it's probably reasonable to look at the status of the oldest musicbrainz
library version in the archive, libmusicbrainz-2.1 (maintained by QA),
and packages depending on it.
The bottom line is that the package should be removed from the archive,
since it only supports the old RDF interface which got deprecated in
2006 and shut down in August 2009 . Martin Michlmayr sent an email
about this a while back , but there are still some reverse
- doesn't actually need python-musicbrainz, cddb is the default
- the dependency on python-musicbrainz should be dropped
which renders the package useless -> remove?
- needs a patch to either remove the mb functionality, or ported to
- can be removed from the archive, nothing uses it
- dropping the build-dep would mean losing libgsttrm.so (tested),
which apparently doesn't work anyway
- dropping the build-dep should be enough, or port the app to
libmusicbrainz4-dev has one rdep, libtunepimp-dev, which also only
supports the old stuff and is deprecated long ago . Rdeps on
- has libtunepimp5 as Suggests, should be dropped
* kdemultimedia (juk)
- just needs to not build-depend libtunepimp-dev (tested)
- should be built with -DWITH_TUNEPIMP=OFF (tested)
So what would be the next step, filing bugs against the packages
requesting the changes suggested above?
ps. I have libmusicbrainz-4.0.0 packaged, just need to push it to alioth
under collab-maint and ask for a sponsor..
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact email@example.com