Hi, as I noticed new apiextractor tarballs, I launched "new upstream" builds of apiextractor.
Very unfortunately, I noticed the following : apiextractor 0.5.0 breaks the public API with regards to apiextractor 0.4.0. Although that might not be a problem per se (and I very much understand the possible reasons behind the breakage), from a distributor point of view it is a very serious issue: libapiextractor0 (SONAME: 0) was shipped in its 0.4.0 version with certain symbols: binaries dynamically linking against libapiextractor0 are now expecting that same set of symbols, no matter what further version they might get, which is not the case with 0.5.0. The symbols of 0.4.0: http://git.debian.org/?p=collab- maint/apiextractor.git;a=blob;f=debian/libapiextractor0.symbols;hb=debian/0.4.0-3 (there were already some "optional" symbols appearing on some arches and not on others) The symbols of 0.5.0: http://pastebin.com/y9eu8ixt (the diff is from line 1520) The only reasonable thing to do seems to be to bump the SONAME from 0 to 1 and by such, releasing apiextractor 0.5.0 which would be shipping libapiextractor1 . Thanks for considering, OdyX, Debian packager for PySide _______________________________________________ PySide mailing list [email protected] http://lists.openbossa.org/listinfo/pyside
