On Thu, Oct 30, 2014 at 11:05:20PM +0100, Niels Thykier wrote: > Control: severity 767230 serious > > On 2014-10-29 17:09, intrigeri wrote: > > Hi Sebastian, hi release team, > > > > [...] > > Hi, > > Thanks for contacting us about this matter. > > > > > Anyway: it seems that I've actually started a transition after the > > transition freeze :/ > > > > Looking through the diff between the version of libotr in testing vs. > the version in sid. I saw no obvious ABI / API breakage myself - that > said I would certainly would not mind a second (third?) reviewer > reviewing this assertion though. Preferably one who knows the C ABI > rules by heart.
For the record, the difference between the APIs of libotr 4.0.0 and libotr 4.1.0 is that two functions that existed in 4.0.0 but were not contained in the .h files (and thus could not appear in applications) were added to the .h files in 4.1.0. So if an application uses those functions, it would require to be built against libotr 4.1.0. Any application compiled against 4.0.0 will work with 4.1.0, but not vice versa (because of those two new functions). That's the reason for the minor version number change, and the corresponding libtool version 6:0:1. It's also why if you build against the 4.1.0 header files, it wants you to have at least 4.1.0 at runtime. - Ian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
