Your message dated Fri, 12 May 2006 10:47:24 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#362571: fixed in dbconfig-common 1.8.13 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.11 Severity: important I was trying to debug a problem i had with simba and ended up looking at this code: ---- ### ### perform a few sanity checks on the data ### # if dbserver is unset, that means localhost. if [ -z "$dbc_dbserver" ]; then # if the server is local, only allow connections from localhost dbc_dballow="localhost" else # otherwise, only tell the remote database to allow from us dbc_dballow=`hostname` fi ---- I see two bugs here. The first one, and the one i am getting: if i tell dbserver to use "localhost" dbc_dballow gets set to my hostname ("stark"). "Stark" hostname resolves to my real ip address, on which, by default, mysql does not listen to. The second bug: if i would actually write the data to a remote server, that machine may or may not be in the same domain name as me (search field in /etc/resolv.conf), so it should be "hostname -f", or even better an ip address. This is how i think the code should look like: ---- ### ### perform a few sanity checks on the data ### # if dbserver is unset, that means localhost. if [ -z "$dbc_dbserver" ] || [ "$dbc_dbserver" = "localhost" ]; then # if the server is local, only allow connections from localhost dbc_dballow="localhost" else # otherwise, only tell the remote database to allow from us dbc_dballow=`hostname -f` fi ---- -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-k7 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages dbconfig-common depends on: ii debconf [debconf-2.0] 1.4.72 Debian configuration management sy ii pwgen 2.05-1 Automatic Password generation ii ucf 2.007 Update Configuration File: preserv dbconfig-common recommends no packages. -- debconf information excluded
--- End Message ---
--- Begin Message ---Source: dbconfig-common Source-Version: 1.8.13 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.13.dsc to pool/main/d/dbconfig-common/dbconfig-common_1.8.13.dsc dbconfig-common_1.8.13.tar.gz to pool/main/d/dbconfig-common/dbconfig-common_1.8.13.tar.gz dbconfig-common_1.8.13_all.deb to pool/main/d/dbconfig-common/dbconfig-common_1.8.13_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: Fri, 12 May 2006 19:21:48 +0200 Source: dbconfig-common Binary: dbconfig-common Architecture: source all Version: 1.8.13 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: 362571 366261 366758 Changes: dbconfig-common (1.8.13) unstable; urgency=low . [sean finney] * now support a dbc_pgsql_createdb_encoding hint option in the postinst for supporting specific encodings (closes: #366758). * updated czech translation from Miroslav Kure (closes: #366261). * a third fix for GRANT command construction hiding in the prerm support script. thanks again to Radu (closes: #362571). * added a check for the version of createuser to prevent the createuser cmd from stopping the install question with a prompt about roles (defaulting to not giving users the role granting privs). * change the authmethod-user question to medium priority, but we really need a way to let the maintainers specify the default authentication method. * fix typo in postinst support code that always logs "administrative sql" even when it's doing normal sql. * error checking when dumping the database in prerm. needs a bit more work still as we end up going back through the postinst/configure code again which isn't smart enough to realize what's going on sometimes. * fix some internal pgsql code where $extra was tossed around too much in the wrong scope. * support for postgresql-8.1. Files: f08a828554e8ac5b0f6f0b6a984cca37 549 admin optional dbconfig-common_1.8.13.dsc 5399e332cf42fddbbd94b885e476990a 193552 admin optional dbconfig-common_1.8.13.tar.gz 2d10b672f385f7c55b952686b6562a58 342204 admin optional dbconfig-common_1.8.13_all.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFEZMXNynjLPm522B0RAvDJAJsHDgVIM/Ow1dHCfLj2Gl91Ik2r/gCfR1mT P15oeltW/EWLtymKfOgNoPs= =6CDn -----END PGP SIGNATURE-----
--- End Message ---
