On Fri, Dec 30, 2022 at 10:29:46AM -0500, Robert Middleton wrote: > On Fri, Dec 30, 2022 at 10:17 AM Tobias Frost <t...@debian.org> wrote: > > > > On Fri, Dec 30, 2022 at 07:18:46AM +0100, Tobias Frost wrote: > > > IF an SONAME bump is required, it will become more challenging, as other > > > Debian teams are involved (and other maintainers if it casues breakages in > > > reverse dependencies) > > > I would basically needs something (it does not need to be the final > > > release, just something with the target SONAME) now to kick of the > > > process. Fixes > > > (without SONAME bump) can still then be provided until February. > > > > Ok, I've compiled the new version and the version currently in Debian and > > threw it at abi-compliance-checker [1]. Unfortunatly it is not happy with > > 8 errors. > > > > I've put the report here: > > https://people.debian.org/~tobi/log4cxx/1_to_2/compat_report.html > > > > 1 = old version, currently in debian > > 2 = new version "head" of current git, master-branch. > > > > Level::initializeLevels ( ) should not be deleted… > > > > On the other erros, where registers have changed, I have no idea what's > > going on… > > > > The registers changing sounds like something in the compiler changed.
Both versions were freshly compiled, with the same compiler and using the same "debian/rules" > But it looks like that's on master, where what we're talking about > here is currently in the next_stable branch(which should have a > ridiculous number of ABI failures, Yes, https://people.debian.org/~tobi/log4cxx/1_to_2/compat_report.html was from the branch "master" to 0.13.0 (as in "from the release tarball" [1]) When doing the same against the branch "next_stable", currently at [2] the result is much much worse: https://people.debian.org/~tobi/log4cxx/1_to_next/compat_report.html /me confused… (I've read your text as it should be the opposite…) [1] sha256sum log4cxx_0.13.0.orig.tar.gz 4e5be64b6b1e6de8525f8b87635270b81f772a98902d20d7ac646fdf1ac08284 log4cxx_0.13.0.orig.tar.gz [2] commit ad751d5fc523205e47fda013df0ff51691eaffb3 (HEAD -> next_stable, origin/next_stable) Author: Stephen Webb <stephen.w...@sabreautonomous.com.au> Date: Fri Dec 30 16:17:56 2022 +1100 Prevent compilation error when the log4cxx user uses a different C++ standard to the log4cxx build The result is much much worse: https://people.debian.org/~tobi/log4cxx/1_to_next/compat_report.html > but it should still be source-compatible). If it is only API compatible, but not ABI compable, we'll need a SONAME bump. > > -Robert Middleton Cheers, -- tobi
signature.asc
Description: PGP signature
