package ubuntustudio-default-settings 0.26 failed to install/upgrade:

I seem to be caught in a loop here... When trying to uninstall this ubuntustudio-default-settings, I'm told there's an error and I must re-install it. So I do which brings back a load of related packages. Uninstalling them or ubuntustudio-default-settings gets me back to the start!

How can I kill Ubuntu Studio?!?

Going around in circles with this... But other people also having the issue and there's a solution here: http://ubuntuforums.org/showthread.php?t=1192122#5 which goes like this:

1.. sudo gedit /var/lib/dpkg/info/ubuntustudio-default-settings.postrm
2.. change the line
     [ -x /usr/sbin/update-gconf-defaults ] && update-gconf-defaults
to:
     [ -x /usr/bin/update-gconf-defaults ] && update-gconf-defaults
3.. remove as the package as normal (sudo apt-get-remove ubuntustudio-default-settings)

#!/bin/sh

set -e

# Automatically added by dh_gconf
if which update-gconf-defaults >/dev/null 2>&1; then
        update-gconf-defaults
fi
# End automatically added section

rm -f /usr/share/gconf/defaults/21_ubuntustudio-panel-settings.entries
[ -x /usr/bin/update-gconf-defaults ] && update-gconf-defaults

the line

[ -x /usr/sbin/update-gconf-defaults ] && update-gconf-defaults

should be,

[ -x /usr/bin/update-gconf-defaults ] && update-gconf-defaults

update-gconf-defaults is in /usr/bin not /usr/sbin

Changed in ubuntustudio-default-settings (Ubuntu):
status: Fix Committed → Fix Released

The entry
set -e
in the script causes this sort of problem to be more grave than it needs to be. It prevents using package management at a high level even for other packages when 1 package has a problem.
I think the
set -e
should be removed & should rarely be part of removal scripts.

From what I see, the fix is still Committed, but not yet Released. SubliM, what makes it Released?

Just wanted to report that everything seems to be fine now. The upgrade went though and the 100+ packages that were being held up by this glitch also got installed. So... thank-you to the developer(s) involved in correcting this.

This bug was fixed in the package ubuntustudio-default-settings - 0.26ubuntu2

---------------
ubuntustudio-default-settings (0.26ubuntu2) karmic; urgency=low

  [ Eric Hedekar ]
  * Changed postrm call of update-gconf-defaults location (LP: #410867)

  [ Luke Yelavich ]
  * debian/postrm: Remove set -e as it manages to make things appear to be more
    grave than they need to be

 -- Eric Hedekar <email address hidden> Fri, 09 Oct 2009 06:26:58 -0700