Bug#426668: marked as done (FLAC 1.1.4 is coming, library transition imminent)
Your message dated Sun, 08 Jul 2007 10:02:14 +0000
with message-id <E1I7Tao-0001Sz-G1@ries.debian.org>
and subject line Bug#426668: fixed in kwave 0.7.7-3
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
- To: email@example.com
- Subject: FLAC 1.1.4 is coming, library transition imminent
- From: firstname.lastname@example.org (Joshua Kwan)
- Date: Wed, 30 May 2007 00:18:35 -0700 (PDT)
- Message-id: <20070530071835.2417986C86@tristan.triplehelix.org>
This is to let you know I've gotten around to packaging FLAC 1.1.4. As
you may know, this involves not only the usual SONAME change from
libflac7 -> libflac8
libflac++5 -> libflac++6
but also liboggflac* have been removed, and merged into the main
FLAC library, so there are lots of API considerations involved
with that. You're receiving this bug because your package depends
on one or more of libflac7, libflac++5, liboggflac3, or liboggflac++2.
By now your upstream sources have transitioned, or at least made #ifdef
style provisions for this new API, especially if your package depends
on liboggflac*. If not, Josh Coalson, the upstream maintainer of FLAC,
has prepared a fairly extensive transition guide on the FLAC web site in
case you want to have a go at making the transition yourself. (What a
If you're ready to build against 1.1.4, please download binary packages
or build them from source from here:
i386 and amd64 are available on that page.
Well, this is a small-time library transition. So this is probably the
only message you'll see about this. I plan to upload 1.1.4 tomorrow
evening if there are no concerns raised about the sanity of this
transition, and you will have until the package clears NEW to prepare.
Once it hits unstable, you should upload your package on the same day to
mitigate uninstallable packages. (But if anyone complains, tell them
that they're using unstable, and should live with it.)
Oh, and sorry for the belated transition -- I've been quite busy with
school. Anyway, let me know if there are any problems.
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is fixed in the latest version of
kwave, which is due to be installed in the Debian FTP archive:
A summary of the changes between this version and the previous one is
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to email@example.com,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
Steve Kowalik <firstname.lastname@example.org> (supplier of updated kwave 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 email@example.com)
-----BEGIN PGP SIGNED MESSAGE-----
Date: Sun, 8 Jul 2007 19:22:58 +1000
Architecture: source i386
Maintainer: Debian QA Group <firstname.lastname@example.org>
Changed-By: Steve Kowalik <email@example.com>
kwave - sound editor for KDE
Closes: 426668 427747 431199
kwave (0.7.7-3) unstable; urgency=low
* QA upload.
* Add in dpatch.
* Re-run aclocal and autoconf after patching.
* Run dh_iconcache if it exists.
* Add a hand-picked patch from upstream SVN to fix FTBFS.
(Closes: #426668, #427747, #431199)
fafb8ae5304a9122c924d40caa22679c 873 kde optional kwave_0.7.7-3.dsc
b52cd1719ea8fee3a63c733639160bcb 9688 kde optional kwave_0.7.7-3.diff.gz
0e2978f43d054bab46ee3e7977a13199 3088694 kde optional kwave_0.7.7-3_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
-----END PGP SIGNATURE-----
--- End Message ---