search for: oggflac__streamdecoderstate

...(matches libtool soname - ok) oggflac 1.1.0 not forward or backwards compatible with 1.0.4 -> ok. oggflac 1.1.1 not forward or backwards compatible with 1.1.0 -> problem. So, it looks to me that liboggflac 1.1.1 should have version-info 2:1:0. This is based on what you told us about the OggFLAC__StreamDecoderState enum entries changing position. > If, in fact, the underlying C library is somehow exposed in > liboggflac++ then, as you suggest, we do have a problem there. I didn't check for that one. If you believe there is not, then I have no reason to think there is a leak. It was just a head...

On Sun, Jan 09, 2005 at 02:03:28AM -0200, Henrique de Moraes Holschuh wrote: > *AND* there is a major problem with liboggflac1. > > liboggflac1 did not change the soname (better check this, it might require a > soname change, check the seekable ogg-flac support stuff). CCing upstream on this. Josh, did 1.1.1 change interfaces in liboggflac? If so, it needs a soname change. >

...> > oggflac 1.1.0 not forward or backwards compatible with 1.0.4 -> ok. > oggflac 1.1.1 not forward or backwards compatible with 1.1.0 -> problem. > > So, it looks to me that liboggflac 1.1.1 should have version-info 2:1:0. > This is based on what you told us about the OggFLAC__StreamDecoderState enum > entries changing position. Thank you. What I said about the enum was between 1.0.4 and 1.1.1. But you are correct. 1.1.0 has version-info 1:2:0 and also does not include the new streaming api or the enum reordering. So the update to 2:1:1 in the 1.1.1 release was incorrect. I should h...

...(better check this, it might require a > > soname change, check the seekable ogg-flac support stuff). > > CCing upstream on this. Josh, did 1.1.1 change interfaces in liboggflac? > If so, it needs a soname change. Most of the changes were compatible, but it looks like some of the OggFLAC__StreamDecoderState enum entries changed position, so the soname should increment. Also, note that the file format changed to fix the streaming issues. liboggflac* prior to 1.1.1 is deprecated and debian should not support it. -r

On Sun, 09 Jan 2005, Matt Zimmerman wrote: > > Is the debian mismatch based on a release between these too? Should > > flac-1.1.1 release have been 2:1:0? In either case, it seems rebuilding > > all the packages against the 1.1.1 library should resolve the issue? Well, if something built against 1.0.4 can (even in corner cases) malfunction with 1.1.1, then yes, it must be

...e a > > > soname change, check the seekable ogg-flac support stuff). > > > > CCing upstream on this. Josh, did 1.1.1 change interfaces in liboggflac? > > If so, it needs a soname change. > > Most of the changes were compatible, but it looks like some of the > OggFLAC__StreamDecoderState enum entries changed position, so the > soname should increment. > > Also, note that the file format changed to fix the streaming issues. > liboggflac* prior to 1.1.1 is deprecated and debian should not support > it. Sure. But since there is soname breakage, we need a completel...