Package: dbconfig-common Version: 1.8.29 Severity: serious Justification: violates section 10.4 of Policy
dbconfig-common includes a number of bash-isms that makes packages that use it break completely if /bin/sh points to a non-bash shell. For example, when /bin/sh points to posh (or I use #!/bin/posh in a postinst), I get the following: Setting up vdmt-mysql (0.1) ... /var/lib/dpkg/info/vdmt-mysql.postinst:6: local: not found dpkg: error processing vdmt-mysql (--configure): subprocess post-installation script returned error exit status 127 When /bin/sh points to dash: Please provide a name for the MySQL database to be used by vdmt-mysql. MySQL database name for vdmt-mysql: vdmt dbconfig-common: writing config to /etc/dbconfig-common/vdmt-mysql.conf -ne granting access to database vdmt for [EMAIL PROTECTED]: -e already exists. -ne creating database vdmt: -e already exists. -ne populating database via sql... -e done. When /bin/sh points to bash, the postinst works just fine. dbconfig-common should either document this (saying that postinst scripts should use #!/bin/bash, and the packages should depend upon bash), should explicitly be using bash (w/ a proper dependency), or be fixed to not using anything that's not POSIX. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
