Regression on maverick when updating to 0.6.7 (security upload)

[Stéphane Graber]

Binary package hint: language-selector

When updating to 0.6.7 from an existing maverick system or when installing from netboot, the upgrade process fails when running postinst.

That happens when no existing language-selector dbus backend is running (quite common).

The issue is:
diff -Nru language-selector-0.6.6/debian/language-selector-common.postinst language-selector-0.6.7/debian/language-selector-common.postinst
--- language-selector-0.6.6/debian/language-selector-common.postinst 2010-10-05 10:14:09.000000000 +0000
+++ language-selector-0.6.7/debian/language-selector-common.postinst 2011-04-19 17:15:45.000000000 +0000
@@ -21,6 +21,8 @@

 case "$1" in
     configure)
+ # shut down any old language-selector dbus backends
+ kill $(pgrep -U root '^ls-dbus-backend$') 2>/dev/null
  fontconfig-voodoo --auto --quiet || true
     ;;

Where "kill" will return != 0 when the process doesn't exist.

[Stéphane Graber (stgraber)]

A fix is being worked on by Kees and will be uploaded very soon.

[Louis Zuckerman (semiosis)]

Glad to see this is actively being worked on.

I use cloudinit & cloud-config to bootstrap puppet in EC2, and this bug completely breaks the automatic bootstrap process for new instances.

Even without the fancy cloud-config/puppet stuff, new maverick instances can't be upgraded. If they are, then dpkg is left in a bad state preventing any other packages from being installed.

Thank you for the urgent response to this critical issue.

[Kees Cook (kees)]

language-selector (0.6.8) maverick-security; urgency=low

  * debian/language-selector-common.postinst: allow missing backend.

[PresuntoRJ (fabio-tleitao)]

Is it on the security repository?

[Ralph Corderoy (ralph-inputplus)]

Congrats on the quick release of a fix. When it's time for us to update and dist-upgrade to get our hands on it can someone add a note to this bug. Thanks.

[Kees Cook (kees)]

@Ralph, sure thing (see comment 3). It's been in the -security repository for about 45 minutes now. Sorry for the trouble!

[David B (d-bannon)]

Hi, reported (a duplicate of) this bug yesterday and received a nice message from Gunnar saying its fixed in 0.6.8
So, just confirming that my Update Manager wanted to pull down 0.6.8 this morning, it all worked smoothly !
Thanks guys !

David