** Changed in: glib2.0 (Ubuntu)
Assignee: (unassigned) = Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/950967
Title:
glib2.0:armel uninstallable on systems that don't
I'd like to merge with Debian again, now that 2.30.2 has hit unstable.
That way we'll reduce our delta again and get that fix.
** Changed in: glib2.0 (Ubuntu)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Branch linked: lp:~ubuntu-desktop/glib/ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/950967
Title:
glib2.0:armel uninstallable on systems that don't support executing
armel code
To
This bug was fixed in the package glib2.0 - 2.32.0-1ubuntu1
---
glib2.0 (2.32.0-1ubuntu1) precise; urgency=low
* Merge with Debian unstable. Remaining Ubuntu changes:
- debian/control.in: Add Conflicts to obsolete libzeitgeist-gio,
wncksyncdaemon, and old bamfdaemon, to
** Changed in: glib2.0 (Debian)
Status: Unknown = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/950967
Title:
glib2.0:armel uninstallable on systems that don't support
the change in the Debian upload is apparently wrong:
glib2.0 (2.30.2-7) UNRELEASED; urgency=low
* libglib2.0-0.postinst.in:
+ Encapsulate gio-querymodules calls in || true statements.
Closes: #659588.
+ Only run gio-querymodules on the non-multiarch path for the host»
Discussed this with mbiebl and seb128 on IRC. In fact, since the
giomodules.cache is per-directory, only one package can have a cache in
/usr/ilb/gio/modules - so it might as well be the native arch for
compatibility. Yeah, this change is reasonable.
--
You received this bug notification