In data giovedì 12 novembre 2020 22:25:31 CET, Vincent Lefevre ha scritto: > Control: retitle -1 libexiv2-27: change in both the API and the ABI > Control: severity -1 serious > > On 2020-10-09 03:11:19 +0200, Vincent Lefevre wrote: > > I think that this is > > > > https://github.com/Exiv2/exiv2/issues/1258 > > > > but this bug has been closed. So I don't know the current status. > > According to upstream, this is a change in the behavior on purpose, > which affects the ABI as one can see (and probably the API too). It > is not normal that one can upgrade libexiv2-27 only, affecting other > applications like gthumb as a consequence. > > The soname should have been changed.
This is not how SONAME works, especially in a binary distro like Debian. Even assuming an SONAME bump is due (which IMHO is not), the consequence will be: 1) the SONAME of the library is bumped, either by upstream or in Debian 2) the Debian package is renamed 3) exiv2 will go through NEW 4) there will be a new exiv2 transition, and all the packages using the exiv2 library will be rebuilt anyway (including gthumb) 5) we are back to the same situation This is a behaviour change of the API, and IMHO there are two only options: a) restore the old behaviour, optionally adding a new API if needed b) adapt the applications to the new behaviour of the API Considering that it seems a wanted change by upstream, then I don't see (a) happening, so (b) seems to me the only alternative. Sure, it is not nice, but meh, not something else to do. Because of the above, Vincent, what about closing this bug, since there is nothing actionable in exiv2? -- Pino Toscano
signature.asc
Description: This is a digitally signed message part.
