Bug#795918: libatkmm-1.6-1: transition potentially needed for g++-5 ABI

Simon McVittie smcv at debian.org
Mon Aug 17 23:26:59 UTC 2015

Package: libatkmm-1.6-1
Version: 2.22.7-2.1+b1
Severity: important
Tags: patch

atkmm1.6 potentially needs a transition to the g++-5 ABI.
See the similar glibmm bug for all the tedious details.

This was blocked by starting both the cairomm and glibmm phases of the
transition, but that has now been done.

Matthias' build logs do not mention any cxx11 symbols, so it is possible
that atkmm1.6 and pangomm do not strictly need to transition,
but Matthias' recent mail to debian-devel mentions some concerns about
ABI breaks that are not automatically detected, and nothing seems to
build-depend on atkmm1.6 or pangomm without also depending on either gtkmm2.4
or gtkmm3.0 anyway; so everything that would be binNMU'd for an atk1.6 or
pangomm transition is going to have to be binNMU'd for a gtkmm2.4 or
gtkmm3.0 transition in any case, and those two are definitely required.
So we might as well do them all at once?

I have staged this in pkg-gnome svn, but not yet tested it (I want to work
my way far enough up the dependency stack to run an actual application).

-------------- next part --------------
A non-text attachment was scrubbed...
Name: atkmm1.6_2.22.7-3.diff
Type: text/x-diff
Size: 6740 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20150818/851ea0a0/attachment-0001.diff>

More information about the pkg-gnome-maintainers mailing list