The 2.20 release code freeze is very near

[Aurelien Jarno]

On Mon, Jul 14, 2014 at 10:50:22AM +0530, Siddhesh Poyarekar wrote:
> On Sun, Jul 13, 2014 at 08:24:20PM +0200, Aurelien Jarno wrote:
> > On the debian side, we are fighting with the s390x jmp_buf change done
> > in 2.19 (commit 93a45ff1). At the beginning it seemed to be only a few
> > packages to be affected, but more we go more we have issues. Among the
> > packages with a lot of reverse dependencies, we have already found that
> > perl and libpng are affected. This start to be difficult to handle.
> 
> Bug link or bug#?

The ABI change is described there:
http://sourceware.org/git/?p=glibc.git;a=commitdiff;h=ee4ec1d7f9bdbdfc87117133478cfb2f6653e65c
https://sourceware.org/glibc/wiki/Release/2.19#Packaging_Changes

On the distributions side, this is described there:
https://bugzilla.redhat.com/show_bug.cgi?id=1064271
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753542

In Debian we rebuilt almost all perl to workaround this abi change,
until we found the following issue:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754125

Indeed jmp_buf is used in the publically exported png_struct_def:
http://sourceforge.net/p/libpng/code/ci/libpng12/tree/png.h#l1263

We can continue handling this ABI change by rebuilding all packages
dependind on libpng, but I am afraid that embedding a jmp_buf in a
structure is not that uncommon and that we are going to discover
more affected packages.

Aurelien

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurelien@aurel32.net                 http://www.aurel32.net