Bug#882180: nmu:

[Laurent Bigonville <bigon@debian.org>]

Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: binnmu

Hello,

Apparently pycairo upstream broke the ABI a while back and the package
with this breakage has been uploaded (by me) in unstable today. (See:
#878080)

I don't think that reverting the break is a good idea has it happened
upstream sometime ago and IMHO we should just go forward.

The number of package impacted is quite limited[0], some have already
been fixed by a sourceful upload to day, the remaining ones are:

nmu pygtk_2.24.0-5.1 . ANY . unstable . -m "Rebuild after pycairo ABI break"
dw pygtk_2.24.0-5.1 . ANY . -m 'python-cairo-dev (>= 1.15.4)'

nmu hippo-canvas_0.3.1-1.2 . ANY . unstable . -m "Rebuild after pycairo ABI break"
dw hippo-canvas_0.3.1-1.2 . ANY . -m 'python-cairo-dev (>= 1.15.4)'

nmu gnome-python-desktop_2.32.0+dfsg-4 . ANY . unstable . -m "Rebuild after pycairo ABI break"
dw gnome-python-desktop_2.32.0+dfsg-4 . ANY . -m 'python-cairo-dev (>= 1.15.4)'

nmu gcompris_15.10-1 . ANY . unstable . -m "Rebuild after pycairo ABI break"
dw gcompris_15.10-1 . ANY . -m 'python-cairo-dev (>= 1.15.4)'

nmu pygobject-2_2.28.6-13 . ANY . unstable . -m "Rebuild after pycairo ABI break"
dw pygobject-2_2.28.6-13 . ANY . -m 'python-cairo-dev (>= 1.15.4)'

Kind regards,

Laurent Bigonville

[0] https://codesearch.debian.net/search?q=Pycairo_IMPORT

-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.13.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)