Bug#353254: gksu: config migration fails on upgrade

[Alex King]

Package: gksu
Version: 1.3.6-1
Severity: normal


When installing gksu from etch into a mixed sarge/etch environment, the
config migration script fails:

bash: /usr/share/gksu/gksu-migrate-conf.sh: line 26: conditional binary
operator expected
bash: /usr/share/gksu/gksu-migrate-conf.sh: line 26: syntax error near
`=~'
bash: /usr/share/gksu/gksu-migrate-conf.sh: line 26: `    if [[ $value
=~ "yes$" ]]; then'

I suspect =~ is a bashism which doesn't exist in the sarge version of
bash (I have no idea what =~ is supposed to do).  For reference:

ii  bash           2.05b-26       The GNU Bourne Again SHell

I guess the fix is to put an appropriate dependancy on a recent bash, or
better, rewrite the script.

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (101, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-686
Locale: LANG=en_NZ, LC_CTYPE=en_NZ (charmap=ISO-8859-1)

Versions of packages gksu depends on:
ii  gconf2                       2.12.1-9    GNOME configuration database syste
ii  libatk1.0-0                  1.10.3-1    The ATK accessibility toolkit
ii  libc6                        2.3.5-13    GNU C Library: Shared libraries an
ii  libgconf2-4                  2.12.1-9    GNOME configuration database syste
ii  libgksu1.2-0                 1.3.7-1     library providing su and sudo func
ii  libgksuui1.0-1               1.0.7-1     a graphical fronted to su library
ii  libglib2.0-0                 2.8.6-1     The GLib library of C routines
ii  libgnome-keyring0            0.4.6-2     GNOME keyring services library
ii  libgtk2.0-0                  2.8.10-1    The GTK+ graphical user interface 
ii  liborbit2                    1:2.12.2-1  libraries for ORBit2 - a CORBA ORB
ii  libpango1.0-0                1.10.3-1    Layout and rendering of internatio
ii  libpopt0                     1.7-5       lib for parsing cmdline parameters
ii  sudo                         1.6.8p7-1.3 Provide limited super user privile

-- no debconf information