Your message dated Wed, 4 May 2011 01:23:56 +0700
with message-id <[email protected]>
and subject line Re: libflac bugs
has caused the Debian Bug report #426641,
regarding FLAC 1.1.4 is coming, library transition imminent
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 [email protected]
immediately.)
--
426641: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=426641
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: easytag
Version: 1.99.12-1
Severity: normal
Hi,
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
dedicated maintainer!):
http://flac.sourceforge.net/api/group__porting.html
If you're ready to build against 1.1.4, please download binary packages
or build them from source from here:
http://people.debian.org/~joshk/
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.
--
Joshua Kwan
--- End Message ---
--- Begin Message ---
This bug is long obsolete; even oldstable (squeeze) now includes libflac8
version 1.2.1, so build problems against the ancient libflac7 1.1.2 are no
longer the concern.
Closing.
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
