Bug#697764: unblock: glib2.0/2.33.12+really2.32.4-4

2013-01-09 Thread Michael Biebl 
Package: release.debian.org
Severity: normal
User: release.debian@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   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/dash
diff -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.0 +0200
+++ glib2.0-2.33.12+really2.32.4/debian/changelog	2013-01-08 23:30:05.0 +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   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.0 +0200
+++ glib2.0-2.33.12+really2.32.4/debian/control	2013-01-08 23:33:01.0 +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.0 +0200
+++ glib2.0-2.33.12+really2.32.4/debian/control.in	2013-01-08 08:00:23.0 +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.0 +0200
+++ glib2.0-2.33.12+really2.32.4/debian/libglib2.0-0.postrm.in	2013-01-08 23:28:38.0 +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

Bug#697764: unblock: glib2.0/2.33.12+really2.32.4-4

2013-01-19 Thread Julien Cristau 
On Wed, Jan  9, 2013 at 14:51:55 +0100, Michael Biebl wrote:

> Package: release.debian.org
> Severity: normal
> User: release.debian@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   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.
> 
Does keeping the breaks on just gvfs+gdm3 also cause upgrade issues?  If
yes, I'd like this to wait until SRM gets a chance to look at the gdm3
pu.

Also this needs a kibi-ack for the udeb.

Cheers,
Julien


signature.asc
Description: Digital signature

Bug#697764: unblock: glib2.0/2.33.12+really2.32.4-4

2013-01-19 Thread Michael Biebl 
On 19.01.2013 12:35, Julien Cristau wrote:
> On Wed, Jan  9, 2013 at 14:51:55 +0100, Michael Biebl wrote:

>> 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.
>>
> Does keeping the breaks on just gvfs+gdm3 also cause upgrade issues?  If
> yes, I'd like this to wait until SRM gets a chance to look at the gdm3
> pu.

When I keep gdm3, the upgrade still fails. As mentioned, I needed to
drop all Breaks which had an indirect or direct dependency on
libgdk-pixbuf2.0-0, which gdm3 has.

I've been talking to Joss regarding gdm3/stable, and I wasn't able to
actually find a dialog or anything where I could trigger an URI open
request. Joss couldn't remember anymore, how he was able to exploit that
and if gdm3/stable is actually vulnerable to such an attack.
So we concluded that the stable upload is more of a precautionary
measure. We shouldn't block the glib2.0 unblock for this.
Having a working upgrade path is more important.

Michael


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#697764: unblock: glib2.0/2.33.12+really2.32.4-4

2013-01-21 Thread Cyril Brulebois 
Julien Cristau  (19/01/2013):
> Also this needs a kibi-ack for the udeb.

As nothing is expected to change/be fixed on the udeb side, I'd like
to see this postponed until rc1 is out.

Mraw,
KiBi.


signature.asc
Description: Digital signature