Your message dated Sun, 13 May 2007 14:17:01 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#418479: fixed in dbconfig-common 1.8.33
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: dbconfig-common
Version: 1.8.31
Severity: normal
Tags: patch

I am not sure I am missing something, but I cannot build a webcalendar
package [1] that initializes correctly the MySQL database.  I traced down
the problem and discovered a problem in dpkg/postint: the order of the 
creatadb and createuser commands are reversed.  The patch attached below
fixes the problem for me.

Indeed, I see in internal/mysql:

dbc_mysql_createdb(){
        [...]
                _dbc_nodb="yes" dbc_mysql_exec_command "CREATE DATABASE 
$dbc_dbname"
        [...]
        
dbc_mysql_createuser(){
        [...]
GRANT ALL PRIVILEGES ON \`$dbc_dbname\`.* TO \`$dbc_dbuser\`[...]
        [...]

Now, the database $dbc_dbname must be created before the
dbc_mysql_createuser is called, but this is not what dpkg/postinst does.

If this is not a bug, please indicate to me how I can make the webcalendar
package install correctly.

[1] The webcalendar package is being actually co-maintainied in Alioth,
    see http://svn.debian.org/wsvn/collab-maint/ext-maint/webcalendar/

Thanks,

Rafael Laboissiere
    
-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/dash
Kernel: Linux 2.6.17-2-686
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages dbconfig-common depends on:
ii  debconf [debconf-2.0]         1.4.72     Debian configuration management sy
ii  ucf                           2.007      Update Configuration File: preserv

dbconfig-common recommends no packages.

-- debconf information excluded
diff -Naur dbconfig-common/dpkg/postinst dbconfig-common-new/dpkg/postinst
--- dbconfig-common/dpkg/postinst       2007-03-04 13:10:42.000000000 +0100
+++ dbconfig-common-new/dpkg/postinst   2007-04-08 09:50:45.000000000 +0200
@@ -62,15 +62,16 @@
                # don't perform the following block of code during upgrades
                if [ ! "$upgrading" ]; then
                        ###
-                       ### now, create the app user account
+                       ### create the database
                        ###
-                       $dbc_createuser_cmd || dbc_install_error "creating user"
+
+                       $dbc_createdb_cmd || dbc_install_error "creating 
database"
                        [ "$dbc_tried_again" ] && return 0
        
                        ###
-                       ### create the database
+                       ### now, create the app user account
                        ###
-                       $dbc_createdb_cmd || dbc_install_error "creating 
database"
+                       $dbc_createuser_cmd || dbc_install_error "creating user"
                        [ "$dbc_tried_again" ] && return 0
        
                        ###

--- End Message ---
--- Begin Message ---
Source: dbconfig-common
Source-Version: 1.8.33

We believe that the bug you reported is fixed in the latest version of
dbconfig-common, which is due to be installed in the Debian FTP archive:

dbconfig-common_1.8.33.dsc
  to pool/main/d/dbconfig-common/dbconfig-common_1.8.33.dsc
dbconfig-common_1.8.33.tar.gz
  to pool/main/d/dbconfig-common/dbconfig-common_1.8.33.tar.gz
dbconfig-common_1.8.33_all.deb
  to pool/main/d/dbconfig-common/dbconfig-common_1.8.33_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
sean finney <[EMAIL PROTECTED]> (supplier of updated dbconfig-common package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Sun, 13 May 2007 15:06:01 +0200
Source: dbconfig-common
Binary: dbconfig-common
Architecture: source all
Version: 1.8.33
Distribution: unstable
Urgency: low
Maintainer: sean finney <[EMAIL PROTECTED]>
Changed-By: sean finney <[EMAIL PROTECTED]>
Description: 
 dbconfig-common - common framework for packaging database applications
Closes: 406127 418479
Changes: 
 dbconfig-common (1.8.33) unstable; urgency=low
 .
   * include a long-neglected fix from Adam Lebsack, which seems to fix the
     problems prevents dbconfig-common from working with dash (closes: #406127).
     this was also likely the cause of dbconfig appearing to attempt creating
     the database/user in the wrong order (closes: #418479).
   * remove some extra straggler bashisms, and use printf instead of echo
     for the dbc_log functions.
   * change function names for some internal debugging/logging functions.
   * now dbc defaults to logging to /var/log/dbconfig-common/dbc.log, which
     can perhaps make it a bit easier to get debugging info from folks who
     experience bugs.
Files: 
 1eee39262133e787de794981446801df 561 admin optional dbconfig-common_1.8.33.dsc
 8edabfde464a7db9eb01ad8d7de0693c 288020 admin optional 
dbconfig-common_1.8.33.tar.gz
 29e5584516c6a2f85cecb05166419920 449754 admin optional 
dbconfig-common_1.8.33_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGRxrpynjLPm522B0RAvrBAJwOEI5xsZ9vORXEZA4smA1MyjTEVgCePr0B
szwU7hm1fZqhkZJeOaorKFM=
=YcwW
-----END PGP SIGNATURE-----


--- End Message ---

Reply via email to