Your message dated Mon, 18 Feb 2013 21:55:40 +0100 with message-id <20130218205540.GD5761@radis.cristau.org> and subject line Re: Bug#697764: unblock: glib2.0/2.33.12+really2.32.4-4 has caused the Debian Bug report #697764, regarding unblock: glib2.0/2.33.12+really2.32.4-5 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 697764: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697764 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: unblock: glib2.0/2.33.12+really2.32.4-4
- From: Michael Biebl <biebl@debian.org>
- Date: Wed, 09 Jan 2013 14:51:55 +0100
- Message-id: <20130109135155.29915.32499.reportbug@pluto.milchstrasse.xx>
Package: release.debian.org Severity: normal User: release.debian.org@packages.debian.org Usertags: unblock Please unblock package glib2.0 It fixes two RC bugs. Related to #676485 is the pu request for gdm3/squeeze [1],[2]. glib2.0 (2.33.12+really2.32.4-4) unstable; urgency=low * Take into account multiarch when removing the cache files in postrm: Remove /usr/lib/gio/modules/giomodule.cache only for the native architecture for which this cache file was created. After removing /usr/share/glib-2.0/schemas/gschemas.compiled on purge, run dpkg-trigger explicitly, so in case libglib2.0-0 is installed for other architectures, the cache file is re-created. (Closes: #696389) * Drop the various Breaks from libglib2.0-0. Those are causing APT to fail on a dist-upgrade from squeeze to wheezy. (Closes: #676485) -- Michael Biebl <biebl@debian.org> Tue, 08 Jan 2013 23:30:04 +0100 Full debdiff is attached. In case you are wondering, why the gvfs Breaks was kept: We noticed in our upgrade tests, that only packages with an (indirect) dependency on libgdk-pixbuf2.0-0 were causing problems. So only those were dropped. Cheers, Michael unblock glib2.0/2.33.12+really2.32.4-4 [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697751 [2] https://lists.debian.org/debian-release/2012/12/msg00778.html -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dashdiff -Nru glib2.0-2.33.12+really2.32.4/debian/changelog glib2.0-2.33.12+really2.32.4/debian/changelog --- glib2.0-2.33.12+really2.32.4/debian/changelog 2012-10-24 11:51:16.000000000 +0200 +++ glib2.0-2.33.12+really2.32.4/debian/changelog 2013-01-08 23:30:05.000000000 +0100 @@ -1,3 +1,16 @@ +glib2.0 (2.33.12+really2.32.4-4) unstable; urgency=low + + * Take into account multiarch when removing the cache files in postrm: + Remove /usr/lib/gio/modules/giomodule.cache only for the native + architecture for which this cache file was created. + After removing /usr/share/glib-2.0/schemas/gschemas.compiled on purge, + run dpkg-trigger explicitly, so in case libglib2.0-0 is installed for + other architectures, the cache file is re-created. (Closes: #696389) + * Drop the various Breaks from libglib2.0-0. Those are causing APT to fail + on a dist-upgrade from squeeze to wheezy. (Closes: #676485) + + -- Michael Biebl <biebl@debian.org> Tue, 08 Jan 2013 23:30:04 +0100 + glib2.0 (2.33.12+really2.32.4-3) unstable; urgency=low * Team upload diff -Nru glib2.0-2.33.12+really2.32.4/debian/control glib2.0-2.33.12+really2.32.4/debian/control --- glib2.0-2.33.12+really2.32.4/debian/control 2012-10-24 12:33:11.000000000 +0200 +++ glib2.0-2.33.12+really2.32.4/debian/control 2013-01-08 23:33:01.000000000 +0100 @@ -38,14 +38,7 @@ ${shlibs:Depends} Recommends: libglib2.0-data, shared-mime-info -Breaks: gvfs (<< 1.8), - gnome-control-center (<< 1:3), - gnome-session (<< 3.0.0-3), - gdm3 (<< 3.0.3), - libgtk-3-0 (<< 3.0.12), - emacs23 (<< 23.4+1-3), - eog (<< 3.2.2-3), - gwaei (<< 3.2.0b1-2) +Breaks: gvfs (<< 1.8) Replaces: libglib2.0-dev (<< 2.23.2-2) Multi-Arch: same Pre-Depends: ${misc:Pre-Depends} diff -Nru glib2.0-2.33.12+really2.32.4/debian/control.in glib2.0-2.33.12+really2.32.4/debian/control.in --- glib2.0-2.33.12+really2.32.4/debian/control.in 2012-09-23 09:31:12.000000000 +0200 +++ glib2.0-2.33.12+really2.32.4/debian/control.in 2013-01-08 08:00:23.000000000 +0100 @@ -38,14 +38,7 @@ ${shlibs:Depends} Recommends: @DATA_PKG@, shared-mime-info -Breaks: gvfs (<< 1.8), - gnome-control-center (<< 1:3), - gnome-session (<< 3.0.0-3), - gdm3 (<< 3.0.3), - libgtk-3-0 (<< 3.0.12), - emacs23 (<< 23.4+1-3), - eog (<< 3.2.2-3), - gwaei (<< 3.2.0b1-2) +Breaks: gvfs (<< 1.8) Replaces: @DEV_PKG@ (<< 2.23.2-2) Multi-Arch: same Pre-Depends: ${misc:Pre-Depends} diff -Nru glib2.0-2.33.12+really2.32.4/debian/libglib2.0-0.postrm.in glib2.0-2.33.12+really2.32.4/debian/libglib2.0-0.postrm.in --- glib2.0-2.33.12+really2.32.4/debian/libglib2.0-0.postrm.in 2012-03-30 15:37:03.000000000 +0200 +++ glib2.0-2.33.12+really2.32.4/debian/libglib2.0-0.postrm.in 2013-01-08 23:28:38.000000000 +0100 @@ -10,12 +10,22 @@ fi if [ -d /usr/lib/gio/modules ]; then # Purge the cache - rm -f /usr/lib/gio/modules/giomodule.cache - rmdir -p --ignore-fail-on-non-empty /usr/lib/gio/modules + if [ $(dpkg --print-architecture) = #ARCH# ]; then + rm -f /usr/lib/gio/modules/giomodule.cache + rmdir -p --ignore-fail-on-non-empty /usr/lib/gio/modules + fi fi if [ "$1" = purge ] && [ -d /usr/share/glib-2.0/schemas ]; then # Purge the compiled schemas rm -f /usr/share/glib-2.0/schemas/gschemas.compiled rmdir -p --ignore-fail-on-non-empty /usr/share/glib-2.0/schemas + + # With multiarch enabled we can't be certain that the cache file + # isn't needed for other architectures since it is not reference + # counted. The best we can do is to fire a file trigger which will + # regenerate the cache file if required. + if [ -d /usr/share/glib-2.0/schemas ]; then + dpkg-trigger /usr/share/glib-2.0/schemas + if fi
--- End Message ---
--- Begin Message ---
- To: Michael Biebl <biebl@debian.org>, 697764-done@bugs.debian.org
- Cc: kibi@debian.org
- Subject: Re: Bug#697764: unblock: glib2.0/2.33.12+really2.32.4-4
- From: Julien Cristau <jcristau@debian.org>
- Date: Mon, 18 Feb 2013 21:55:40 +0100
- Message-id: <20130218205540.GD5761@radis.cristau.org>
- In-reply-to: <20130119113518.GT5676@radis.cristau.org>
- References: <20130109135155.29915.32499.reportbug@pluto.milchstrasse.xx> <20130119113518.GT5676@radis.cristau.org>
On Sat, Jan 19, 2013 at 12:35:18 +0100, Julien Cristau wrote: > Also this needs a kibi-ack for the udeb. > acked now, so unblock-udeb added. Cheers, JulienAttachment: signature.asc
Description: Digital signature
--- End Message ---