Your message dated Mon, 17 Sep 2007 10:26:09 +1000
with message-id <[EMAIL PROTECTED]>
and subject line bugzilla: Uninstallable due to bashisms (when using POSIX 
shell, eg. dash)
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: bugzilla
Version: 2.22.1-2
Severity: serious
Justification: Policy 10.4

Installation is failing on my system where /bin/sh is a link to
/bin/dash. The precense of the "-ne" and "-e" in output indicates that
there are probably one or more scripts using bash features without
specifying /bin/bash as the interpreter.

Here is a snippet of the output during installation:
> Replacing config file /etc/bugzilla/dbconfig-params with new version
> -ne granting access to database bugzilla for [EMAIL PROTECTED]: 
> -e failed.
> error encountered creating user:
> mysql said: ERROR 1049 (42000): Unknown database 'bugzilla'


-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'testing')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/dash
Kernel: Linux 2.6.16.29-xen
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)

Versions of packages bugzilla depends on:
ii  apache2-mpm-prefork [httpd 2.2.3-4+etch1 Traditional model for Apache HTTPD
ii  dbconfig-common            1.8.29+etch1  common framework for packaging dat
ii  debconf [debconf-2.0]      1.5.11        Debian configuration management sy
ii  exim4                      4.63-17       metapackage to ease exim MTA (v4) 
ii  exim4-daemon-light [mail-t 4.63-17       lightweight exim MTA (v4) daemon
ii  libappconfig-perl          1.56-2        Perl module for configuration file
ii  libdbd-mysql-perl          3.0008-1      A Perl5 database interface to the 
ii  libmailtools-perl          1.74-1        Manipulate email in perl programs
ii  libmime-perl               5.420-0.1     Perl5 modules for MIME-compliant m
ii  libtemplate-perl           2.14-1        template processing system written
ii  libtimedate-perl           1.1600-5      Time and date functions for Perl
ii  mysql-client-5.0 [mysql-cl 5.0.32-7etch1 mysql database client binaries
ii  patch                      2.5.9-4       Apply a diff file to an original
ii  ucf                        2.0020        Update Configuration File: preserv

Versions of packages bugzilla recommends:
ii  libchart-perl       2.4.1-4              Chart Library for Perl
ii  libxml-parser-perl  2.34-4.2             Perl module for parsing XML files
ii  mysql-server        5.0.32-7etch1        mysql database server (meta packag
ii  mysql-server-5.0 [m 5.0.32-7etch1        mysql database server binaries
ii  perlmagick          7:6.2.4.5.dfsg1-0.14 A perl interface to the libMagick 

-- debconf information excluded


--- End Message ---
--- Begin Message ---
reassign 440324 dbconfig-common 1.8.29+etch1
fixed 440624 1.8.33
forcemerge 406127 440324
thanks

Magnus Holmgren wrote:
Ted Percival <[EMAIL PROTECTED]>:
Installation is failing on my system where /bin/sh is a link to
/bin/dash. The precense of the "-ne" and "-e" in output indicates that
there are probably one or more scripts using bash features without
specifying /bin/bash as the interpreter.

I've taken a look at this bug as part of my NM process. The "-n" and "-ne" you're seeing comes from dbconfig-common, not bugzilla. This particular problem was fixed in dbconfig-common 1.8.33.

That will be the cause then, thanks.

That probably has nothing to do with the error message from mysql. Apparently the database wasn't created successfully. I think you need to provide more details of what you did, how you answered debconf questions and what other output you got.

Switching /bin/sh back to /bin/bash for the installation solved the problem.

--
\0


--- End Message ---

Reply via email to