Package: libglib2.0-dev Version: 2.45.1-2 Followup-For: Bug #683593 Dear Maintainer,
I had a look and this bug is still present in 2.45.1-2. The only issues I noticed are the following binaries: /usr/bin/glib-genmarshal /usr/bin/gobject-query /usr/bin/gtester Is there any reason not to move them to a separate Multi-Arch: foreign package? One option would be libglib2.0-bin but it would also be possible to add a new package, libglib2.0-tools for instance. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libglib2.0-dev depends on: ii libc6 2.19-18 ii libglib2.0-0 2.44.0-3 ii libglib2.0-bin 2.44.0-3 ii libpcre3-dev 2:8.35-3.3 ii pkg-config 0.28-1 pn python:any <none> ii zlib1g-dev 1:1.2.8.dfsg-2+b1 libglib2.0-dev recommends no packages. Versions of packages libglib2.0-dev suggests: ii libglib2.0-doc 2.44.0-3 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
