On Thu, Aug 27, 2015 at 18:00:54 +0200, Andreas Henriksson wrote: > I've already updated the libical package to a new upstream micro-release. > Given that this was a micro-release plus the following release note I > did not expect any breakage: > "Version 1.0.1 fixes some bugs and adds some small features to > version 1.0.0 while retaining binary and source compatibility." > > Unfortunately this seems to not be true. While there where no > missing symbols there are apparently other ABI breakages > as reported in https://bugs.debian.org/797003 > > Not sure about the full reasons for the breakage but it looks to me like > it's partially caused by a debian patch to generate reproducible builds > which sorts the output of a generated enum which means new additions > ends up in the middle instead of at the end. > Will this patch cause ABI problems for every new release from now on I > wonder?! > This might not be the only reason for breakage though and I've only > quickly looked at it..... > > Anyway, back to the current breakage. The last time similar breakage > was upon us, we seem to simply have renamed the package and then > rebuilt reverse dependencies. > > Please advice if you'd like me to upload a new version with libical1a > renamed to libical1b and start a transition .... > I'd prefer to fix the root cause and start by making sure no accidental ABI breakage like this happens again. Then we can talk about whether the ABI is the libical1a one or something else. Cheers, Julien
Attachment:
signature.asc
Description: Digital signature