* Julien Cristau: >> This caused an other problem, related to ICU support in SQLite3. I have >> disabled it and rpm now builds fine. So a rebuild trigger will be enough >> for rpm when sqlite3 3.6.14.2 is in the archive. >> As of #522103, I don't think it worths a SONAME bump. An internal >> function is changed in an incompatible way. The only one application > > It's not an internal function. It's part of your library's public > interface, aka ABI.
Huh? SQLite has an extensive API documentation. If something is not listed at all, or explicitly marked as experimental, it is certainly not part of the stable API. We had endless problems back in the old days when everyone used internal libc functions because they could, as a consequence of the C linkage model. Nowadays, libc uses private symbols to prevent this (and other libraries could as well), but it doesn't mean that anything which can be referenced externally is actually part of the public API of a library. > Have you added Breaks on old evolution to make sure people don't get > bitten by this again? I don't think Breaks is needed if evolution has been fixed. The version in stable is not affected, right? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
