Bug#797074: transition: libical
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: transition
Hello.
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 ....
Ben file:
title = "libical";
is_affected = .depends ~ "libical1a" | .depends ~ "libical1b";
is_good = .depends ~ "libical1b";
is_bad = .depends ~ "libical1a";
-- System Information:
Debian Release: 8.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Reply to: