Debian Bug report logs - #476383
Please port to new libmpcdec API

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Sebastian Dröge <slomo@circular-chaos.org>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: Please port to new libmpcdec API

Date: Wed, 16 Apr 2008 13:07:06 +0200

[Message part 1 (text/plain, inline)]

Package: audacious-plugins
Severity: wishlist
Version: 1.5.0-1

Hi,
please port your application to the new libmpcdec API in experimental.
You find it as libmpcdec-dev / libmpcdec6 in the libmpc source package.

The API changes are fairly trivial, see [0] for a patch that does this
for the GStreamer plugin.

The API might not be 100% stable yet but there are very few changes (if
any) to be expected. I don't know if libmpc (and Musepack's stream
version 8) will be ready for lenny but when this gets uploaded to
unstable this bugs will become grave.

Thanks

[0] http://bugzilla.gnome.org/show_bug.cgi?id=526905

[signature.asc (application/pgp-signature, inline)]

Message #10 received at 476383@bugs.debian.org (full text, mbox, reply):

From: Sebastian Dröge <slomo@circular-chaos.org>

To: 476382@bugs.debian.org, 476381@bugs.debian.org, 476379@bugs.debian.org, 476378@bugs.debian.org, 476371@bugs.debian.org, 476372@bugs.debian.org, 476377@bugs.debian.org, 476384@bugs.debian.org, 476376@bugs.debian.org, 476375@bugs.debian.org, 476374@bugs.debian.org, 476373@bugs.debian.org, 476383@bugs.debian.org, 476370@bugs.debian.org

Cc: control@bugs.debian.org

Subject: Re: Please port to new libmpcdec API

Date: Sat, 21 Mar 2009 08:57:04 +0100

[Message part 1 (text/plain, inline)]

severity 476382 important
severity 476381 important
severity 476379 important
severity 476378 important
severity 476371 important
severity 476372 important
severity 476377 important
severity 476384 important
severity 476376 important
severity 476375 important
severity 476374 important
severity 476373 important
severity 476383 important
severity 476370 important
severity 520596 important
thanks

Hi,
libmpc will be uploaded to unstable in the next days. Please port your
package to the new API ASAP, it will most probably fail to build after
the upload to unstable.

The new package can already be found in experimental and the biggest API
change is probably the location change of the headers and the change
from mpc_decoder to mpc_demuxer and some minor changes to the bits
reader. Take a look at the sources of mpcdec inside the libmpc sources
for an example usage of the new API or at ext/musepack from
gst-plugins-bad0.10.

Thanks

[signature.asc (application/pgp-signature, inline)]

Message #17 received at 476383-done@bugs.debian.org (full text, mbox, reply):

From: Sebastian Dröge <slomo@circular-chaos.org>

To: 476370-done@bugs.debian.org, 476383-done@bugs.debian.org

Subject: Re: Bug#476384: Please port to new libmpcdec API

Date: Sat, 21 Mar 2009 09:31:42 +0100

[Message part 1 (text/plain, inline)]

Hi,
these two bugs are actually not useful anymore as the packages don't
link against libmpcdec... closing.

[signature.asc (application/pgp-signature, inline)]

Message #22 received at 476383@bugs.debian.org (full text, mbox, reply):

From: Max Kellermann <max@duempel.org>

To: Sebastian Dröge <slomo@circular-chaos.org>, 476377@bugs.debian.org

Cc: 476382@bugs.debian.org, 476381@bugs.debian.org, 476379@bugs.debian.org, 476378@bugs.debian.org, 476371@bugs.debian.org, 476372@bugs.debian.org, 476384@bugs.debian.org, 476376@bugs.debian.org, 476375@bugs.debian.org, 476374@bugs.debian.org, 476373@bugs.debian.org, 476383@bugs.debian.org, 476370@bugs.debian.org

Subject: Re: Bug#476377: Please port to new libmpcdec API

Date: Sat, 21 Mar 2009 09:37:03 +0100

On 2009/03/21 08:57, Sebastian Dröge <slomo@circular-chaos.org> wrote:
> libmpc will be uploaded to unstable in the next days. Please port your
> package to the new API ASAP, it will most probably fail to build after
> the upload to unstable.

I do not understand the hurry.  Do you plan to remove the old libmpc
package?  The Debian shared library policy guarantees that older
package continue to work/build (with older SO versions) even when a
new API of a library gets uploaded.  Please explain how this bug
report relates to the Debian shared library policy.

Max

Message #27 received at 476383@bugs.debian.org (full text, mbox, reply):

From: Reinhard Tartler <siretart@tauware.de>

To: Max Kellermann <max@duempel.org>

Cc: 476384@bugs.debian.org, Sebastian Dröge <slomo@circular-chaos.org>, 476377@bugs.debian.org, 476383@bugs.debian.org, 476379@bugs.debian.org, 476373@bugs.debian.org, 476375@bugs.debian.org, 476378@bugs.debian.org, 476374@bugs.debian.org, 476381@bugs.debian.org, 476372@bugs.debian.org, 476382@bugs.debian.org, 476371@bugs.debian.org, 476376@bugs.debian.org, 476370@bugs.debian.org

Subject: Re: Bug#476384: Bug#476377: Please port to new libmpcdec API

Date: Sat, 21 Mar 2009 11:37:53 +0100

Max Kellermann <max@duempel.org> writes:

> On 2009/03/21 08:57, Sebastian Dröge <slomo@circular-chaos.org> wrote:
>> libmpc will be uploaded to unstable in the next days. Please port your
>> package to the new API ASAP, it will most probably fail to build after
>> the upload to unstable.
>
> I do not understand the hurry.  Do you plan to remove the old libmpc
> package?  The Debian shared library policy guarantees that older
> package continue to work/build (with older SO versions) even when a
> new API of a library gets uploaded.  Please explain how this bug
> report relates to the Debian shared library policy.

the transition will replace the old version of the library in
testing. Existing packages will not be broken immediately, but they need
to be removed from 'testing' in order to let the new version of libmpc
migrate.

Ideally all packages are updated in a timely fashion, so that no
packages need to be removed from testing at all.

-- 
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4

Message #32 received at 476383@bugs.debian.org (full text, mbox, reply):

From: Adeodato Simó <dato@net.com.org.es>

To: Sebastian Dröge <slomo@circular-chaos.org>

Cc: 476370@bugs.debian.org, 476383@bugs.debian.org

Subject: Re: Bug#476384: Please port to new libmpcdec API

Date: Tue, 7 Apr 2009 19:05:06 +0200

reopen 476370
reopen 476383
thanks

Sebastian Dröge (Sat, 21 Mar 2009 09:31:42 +0100):

> Hi,
> these two bugs are actually not useful anymore as the packages don't
> link against libmpcdec... closing.

Well, the packages do not link against libmpcdec *anymore* as a
workaround for the API change. AFAIK, this applications still have to be
ported in order to regain their full functionality (or, rather, to
regain suport for the Musepack format).

Cheers,

-- 
- Are you sure we're good?
- Always.
        -- Rory and Lorelai

Message #39 received at 476383@bugs.debian.org (full text, mbox, reply):

From: Adeodato Simó <dato@net.com.org.es>

To: Sebastian Dröge <slomo@circular-chaos.org>

Cc: debian-release@lists.debian.org

Subject: Re: Reverting the libmpc 0.1~r435-1 upload

Date: Tue, 7 Apr 2009 20:27:07 +0200

+ Sebastian Dröge (Sat, 21 Mar 2009 09:26:20 +0100):

Hello,

> > > I'll take a look at some packages in the next days and send an status
> > > update to those bugs, maybe raising the severity to important now...
> > Sure, important sounds fine to me, thanks.

> Ok, done... the affected packages are:

> cmus                   ---- Bug #476382
> cynthiune.app          ---- Bug #476381
> gst-plugins-bad0.10    ---- Ported
> k3b                    ---- Bug #476379
> libtunepimp            ---- Bug #476378
> moc                    ---- Ported (FTBFS atm because of other issues)
> mpc123                 ---- Bug #476372
> mpd                    ---- Bug #476377
> mplayer                ---- Bug #476384
> qmmp                   ---- Bug #520596
> quodlibet              ---- Unnecessary dependency, bug #476376
> vlc                    ---- Bug #476375
> xine-lib               ---- Bug #476374
> xine-lib-1.2           ---- Bug #520600
> xmms2                  ---- Bug #476373

> Some of them might actually be ported already but they don't
> build their musepack support with the experimental package right
> now. This might be because the header location has changed
> after I've filed those bugs, now it's final though :)

Well, none of those bugs has been fixed in experimental by now (nor have
a patch), and the one marked as pending (the one that is not quodlibet),
has a comment by the maintainer stating that he intends to disable
musepack support while upstream gets around to fixing the issue. The
picture doesn’t look very promising:

    http://bit.ly/libmpcdec6-transition

I’m all for getting this transition done without leaving the old API
around, but at the same time I don’t want packages unbuildable in
unstable, with failures that are not straightforward to fix, for a long
period of time.

As I said in one of my earlier mails, I won’t feel comfortable with
going forward with this transition until all (or most) of the packages
have tested patches. The thing is that for this to happen, we’re going
to need either time, quite a lot of it, or for somebody to step up and
start “driving” the transition, filling the gaps the maintainers may
leave.

So the question is whether you have the time and inclination to do the
latter yourself, if you want the transition done sooner rather than
later, working with maintainers on a solution for each particular
package (a solution that does not entail, preferably, dropping Musepack
support from the application). For example, Rafael Laboissiere, the
maintainer of libmtp, did exactly this for the recent libmtp7 -> libmtp8
transition: he filed bugs, provided patches, and did a bunch of NMUs,
which allowed us to do the transition in a timely manner.

So, do we have a plan, or do we just opt for waiting? I’m Bcc'ing all of
the involved bugs so that maintainers can send an update on the status
of their bug (to the debian-release mailing list and *your* bug,
please). If a fix exists, please send it to the BTS with an appropriate
“patch” tag or, preferably, make an upload to experimental.

Thanks,

-- 
- Are you sure we're good?
- Always.
        -- Rory and Lorelai

Message #44 received at 476383-close@bugs.debian.org (full text, mbox, reply):

From: William Pitcock <nenolod@dereferenced.org>

To: 476383-close@bugs.debian.org

Subject: Bug#476383: fixed in audacious-plugins 2.0.1-1

Date: Sun, 31 May 2009 01:32:06 +0000

Source: audacious-plugins
Source-Version: 2.0.1-1

We believe that the bug you reported is fixed in the latest version of
audacious-plugins, which is due to be installed in the Debian FTP archive:

audacious-plugins-dbg_2.0.1-1_i386.deb
  to pool/main/a/audacious-plugins/audacious-plugins-dbg_2.0.1-1_i386.deb
audacious-plugins-dev_2.0.1-1_i386.deb
  to pool/main/a/audacious-plugins/audacious-plugins-dev_2.0.1-1_i386.deb
audacious-plugins-extra_2.0.1-1_i386.deb
  to pool/main/a/audacious-plugins/audacious-plugins-extra_2.0.1-1_i386.deb
audacious-plugins_2.0.1-1.diff.gz
  to pool/main/a/audacious-plugins/audacious-plugins_2.0.1-1.diff.gz
audacious-plugins_2.0.1-1.dsc
  to pool/main/a/audacious-plugins/audacious-plugins_2.0.1-1.dsc
audacious-plugins_2.0.1-1_i386.deb
  to pool/main/a/audacious-plugins/audacious-plugins_2.0.1-1_i386.deb
audacious-plugins_2.0.1.orig.tar.gz
  to pool/main/a/audacious-plugins/audacious-plugins_2.0.1.orig.tar.gz



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 476383@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
William Pitcock <nenolod@dereferenced.org> (supplier of updated audacious-plugins package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Fri, 29 May 2009 21:36:59 -0500
Source: audacious-plugins
Binary: audacious-plugins audacious-plugins-extra audacious-plugins-dev audacious-plugins-dbg
Architecture: source i386
Version: 2.0.1-1
Distribution: unstable
Urgency: low
Maintainer: Debian Audacious Packagers <pkg-audacious-maintainers@lists.alioth.debian.org>
Changed-By: William Pitcock <nenolod@dereferenced.org>
Description: 
 audacious-plugins - Base plugins for audacious
 audacious-plugins-dbg - Audacious-Plugins debug symbols
 audacious-plugins-dev - Useful virtual package for doing audacious plugin development
 audacious-plugins-extra - Various extra plugins for audacious
Closes: 456558 460802 476383 500081 514674 518679
Changes: 
 audacious-plugins (2.0.1-1) unstable; urgency=low
 .
   * New upstream release.
     - New skins plugin with many less design flaws than the old XMMS code.
       (Closes: #456558, #460802, #500081)
     - Do not crash when invalid monkey's audio chunks are encountered.
       (Closes: #514674)
 .
   * Acknowledge NMU, thanks Rafael for your work.
     - debian/patches/004-compile-with-libmtp8.patch: dropped,
       different patch integrated upstream to solve the same issue.
 .
   * debian/audacious-plugins.install: add crossfade.so, skins.so.
   * debian/audacious-plugins-extra.install: add icecast.so, psf2.so, xsf.so
   * debian/control: enable projectm again.
   * debian/patches/*: dropped, integrated upstream.
   * debian/control: remove dependency on libmpcdec-dev and disable musepack
     support, as musepack sv7 and sv8 will be regained by audacious-ffaudio
     shortly, e.g. before squeeze ships.
     (Closes: #518679, #476383)
Checksums-Sha1: 
 63cb0932d2587e68dc6d8827f90d91d94f0c8772 2432 audacious-plugins_2.0.1-1.dsc
 cbb702b269e59ccdc36f483768881baa865af012 3505273 audacious-plugins_2.0.1.orig.tar.gz
 3bf63fa1c9c83585c6c8eab9d9e88d9b766bfd8b 11161 audacious-plugins_2.0.1-1.diff.gz
 0ee08f2570e2a97975f3b7e457d6651e56a3adbf 592286 audacious-plugins_2.0.1-1_i386.deb
 cfe85160c4f529203ba744bd91820e21fb849525 1315688 audacious-plugins-extra_2.0.1-1_i386.deb
 f6fec6b6f91ba7a103b5bea0abbf07f086426b34 10624 audacious-plugins-dev_2.0.1-1_i386.deb
 031c5a6847f3f1b1dc13265ba931af9d9b90e033 5955168 audacious-plugins-dbg_2.0.1-1_i386.deb
Checksums-Sha256: 
 a9163a82381ed39ce5c6136017dcbef0f0767127effc6fe933016e828ec61c49 2432 audacious-plugins_2.0.1-1.dsc
 3279a2160d026c16828a850dd2d0b289bd69569c3a8ad6e060c6673b5d8cf648 3505273 audacious-plugins_2.0.1.orig.tar.gz
 7c1fd41c6225f0019140d8c0f57f95f458b0852a33248238ff47766c1f02bffc 11161 audacious-plugins_2.0.1-1.diff.gz
 d259ea68186ebe9f125c56f5ab15b94d2edf9795a7a0955e97674a03364abfab 592286 audacious-plugins_2.0.1-1_i386.deb
 4f90ab2f1e52d2764baa8f72a38a1e0d37817de1a5db77e4b40b4d3c5dee3a6e 1315688 audacious-plugins-extra_2.0.1-1_i386.deb
 bccbacccbf1406faa70d117e49e82fdbe714b3d375d5be4deaf5ccc963b1679c 10624 audacious-plugins-dev_2.0.1-1_i386.deb
 96fa1b6132b54e9a19ed3eee15588f6c4214905b86cb95d7821a36d91377ee6c 5955168 audacious-plugins-dbg_2.0.1-1_i386.deb
Files: 
 defebfb5582e4118b7aacf68573f9c06 2432 sound optional audacious-plugins_2.0.1-1.dsc
 5de2767d232e8f9f84fbd15d3b960f8b 3505273 sound optional audacious-plugins_2.0.1.orig.tar.gz
 de4c00f2fa15d4de089ee94e5fa9b04e 11161 sound optional audacious-plugins_2.0.1-1.diff.gz
 b80379cec4c2ffcb1a91d5a09604d7e6 592286 sound optional audacious-plugins_2.0.1-1_i386.deb
 a5cde27ec3dfbadc34e5c8f02a5316d0 1315688 sound optional audacious-plugins-extra_2.0.1-1_i386.deb
 d06d2ed55a8c7542e4458e9f88d9bf64 10624 devel optional audacious-plugins-dev_2.0.1-1_i386.deb
 f511d42b6d55e31ac2c4165bb2968b7c 5955168 debug extra audacious-plugins-dbg_2.0.1-1_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkoh2aEACgkQAQwuptkwlkQVMgCfeqd+PZVud9YbSZeeKIHhBoqo
Q3kAnjCnXloedrKjl9t3PSJjC456+Htk
=w+7l
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.