Bug#747928: libglib2.0-dev: fails to configure - unmet "python:any" dependency

[Lionel Elie Mamane]

Package: libglib2.0-dev
Version: 2.40.0-3
Severity: serious

libglib2.0-dev fails to configure:

dpkg: dependency problems prevent configuration of libglib2.0-dev:
libglib2.0-dev depends on python:any (>= 2.6.6-7~).

Well, the package name is "python", not "python:any". I thought it
might be related to multiarch and maybe a newer dpkg would parse the
"python:any", but nope, even with dpkg from unstable, still same error
message.

-- System Information:
Debian Release: 7.5
APT prefers stable
APT policy: (500, 'stable'), (400, 'testing'), (300, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_LU.UTF-8, LC_CTYPE=fr_LU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages libglib2.0-dev depends on:
ii libc6 2.17-3
ii libglib2.0-0 2.40.0-3
ii libglib2.0-bin 2.40.0-3
ii libpcre3-dev 1:8.31-2
ii pkg-config 0.26-1
pn python:any <none>
ii zlib1g-dev 1:1.2.7.dfsg-13

libglib2.0-dev recommends no packages.

Versions of packages libglib2.0-dev suggests:
ii libglib2.0-doc 2.33.12+really2.32.4-5

-- no debconf information

[Lionel Elie Mamane]

Post by Lionel Elie Mamane
Package: libglib2.0-dev
Version: 2.40.0-3
Severity: serious
libglib2.0-dev depends on python:any (>= 2.6.6-7~).
Well, the package name is "python", not "python:any". I thought it
might be related to multiarch and maybe a newer dpkg would parse the
"python:any", but nope, even with dpkg from unstable, still same error
message.

Upgrading *python* helped. So it seems there is a missing dependency
on new-enough python. See e.g. https://bugs.debian.org/724705 for a
similar situation.