Your message dated Sun, 13 May 2007 14:17:01 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#406127: 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.29
I am trying to maintain a package that requires dbconfig-common. I
originally found this bug on ubuntu's Edgy Eft, but found that this
is a bug that would affect Debian as well, I think due to varying
mysql versions. I've included a patch that takes the _dbc_nodb
variable in dbc_mysql_exec_file and makes sure it's honored. Without
this patch, l_dbname is defined before entering this function, which
causes the mysql command to require the database in l_dbname.
--- internal/mysql.orig 2007-01-08 15:53:55.000000000 -0700
+++ internal/mysql 2007-01-08 15:54:13.000000000 -0700
@@ -71,7 +71,8 @@
dbc_log="no file supplied to execute"
return 1
fi
-
+
+ l_dbname=
if [ ! "$_dbc_nodb" ]; then
l_dbname="$dbc_dbname"
fi
Adam Lebsack
Software Engineer
Ruffdogs, Inc.
[EMAIL PROTECTED]
970-484-5390
--- 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 ---
