Your message dated Sun, 15 Mar 2009 11:02:04 +0000
with message-id <[email protected]>
and subject line Bug#514347: fixed in dbconfig-common 1.8.41
has caused the Debian Bug report #514347,
regarding dbconfig-common: dbc_generate_include generates configuration file, 
even if not asked to
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
514347: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=514347
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dbconfig-common
Version: 1.8.40
Severity: normal

In the first dialog, dbconfig-common asks, if it should manage the db
configuration or not. If I choose "No", 
dbc_generate_include will still generates a configuration file with bogus
(i.e. mostly empty values).
In such a case, it should be up to the administrator to setup the db and
generate a configuration on his own.

Why: In my case, if the user choses no, and dbconfig-common generates a
'bogus' configuration file, my app (rsyslog) will pick up this
configuration and fail to connect to the db.
If there is no configuration, my app won't make a connection attempt.

Cheers,
Michael

-- System Information:
Debian Release: 5.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (300, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.28.3
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

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

dbconfig-common recommends no packages.

Versions of packages dbconfig-common suggests:
ii  mysql-client                  5.0.75-1   MySQL database client (metapackage
ii  mysql-client-5.0 [virtual-mys 5.0.75-1   MySQL database client binaries
ii  postgresql-client-8.3 [postgr 8.3.5-1    front-end programs for PostgreSQL 

-- debconf information:
  dbconfig-common/remote-questions-default: false
  dbconfig-common/pgsql/revertconf: false
  dbconfig-common/internal/skip-preseed: false
  dbconfig-common/db/dbname:
  dbconfig-common/pgsql/manualconf:
  dbconfig-common/dbconfig-remove: true
  dbconfig-common/mysql/method: unix socket
  dbconfig-common/upgrade-backup: true
  dbconfig-common/pgsql/authmethod-admin: ident
  dbconfig-common/upgrade-error: abort
  dbconfig-common/purge: false
  dbconfig-common/db/basepath:
  dbconfig-common/install-error: abort
  dbconfig-common/pgsql/no-empty-passwords:
  dbconfig-common/pgsql/admin-user: postgres
  dbconfig-common/dbconfig-install: true
  dbconfig-common/dbconfig-reinstall: false
  dbconfig-common/remote/host:
  dbconfig-common/pgsql/changeconf: false
  dbconfig-common/remote/newhost:
  dbconfig-common/missing-db-package-error: abort
  dbconfig-common/dbconfig-upgrade: true
  dbconfig-common/pgsql/no-user-choose-other-method:
  dbconfig-common/internal/reconfiguring: false
  dbconfig-common/passwords-do-not-match:
  dbconfig-common/remove-error: abort
  dbconfig-common/remember-admin-pass: false
  dbconfig-common/mysql/admin-user: root
  dbconfig-common/pgsql/method: unix socket
  dbconfig-common/pgsql/authmethod-user:
  dbconfig-common/database-type:
  dbconfig-common/db/app-user:
  dbconfig-common/remote/port:



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

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.41.dsc
  to pool/main/d/dbconfig-common/dbconfig-common_1.8.41.dsc
dbconfig-common_1.8.41.tar.gz
  to pool/main/d/dbconfig-common/dbconfig-common_1.8.41.tar.gz
dbconfig-common_1.8.41_all.deb
  to pool/main/d/dbconfig-common/dbconfig-common_1.8.41_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.8
Date: Sun, 15 Mar 2009 11:08:39 +0100
Source: dbconfig-common
Binary: dbconfig-common
Architecture: source all
Version: 1.8.41
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: 513753 513909 514347 514354 514357 514368 514441 514503 514574 514574 
514783 514896 516118 516606 516623 516643
Changes: 
 dbconfig-common (1.8.41) unstable; urgency=low
 .
   * Fix for a location in the code where ucf was not being called with the
     now requisite --debconf-ok (closes: #513753).
   * New postinst maintainer variable: dbc_dgi_on_manual.  Allows the
     packager to disable creation of the d-g-i generated files when the
     admin opts for manual installation (closes: #514347).
   * Incorporate suggested rewrite of package description and debconf templates
     from Christian Perrier and the debian-l10n-english contributors
     (closes: #513909).
   * new/updated debconf translations:
     - Basque, thanks to Piarres Beobide (closes: #516118).
     - Czech, thanks to Miroslav Kure (closes: #514441).
     - Finnish, thanks to Esko Arajärvi (closes: #516623).
     - French, thanks to Christian Perrier (closes: #514574).
     - German, thanks to Helge Kreutzmann (Closes: #514783).
     - Italian, thanks to Giuseppe Sacco (closes: #514574).
     - Korean, thanks to Changwoo Ryu (closes: #514354).
     - Norwegian Bokmål, thanks to Bjørn Steensrud and Christian Perrier
       (closes: #514368).
     - Portuguese, thanks to Miguel Figueiredo (closes: #516643).
     - Russian, thanks to Yuri Kozlov and Christian Perrier (closes: #514896).
     - Slovak, thanks to helix84 (closes: #514357).
     - Swedish, thanks to Daniel Nylander (closes: #516606).
     - Vietnamese, thanks to Clytie Siddall and Christian Perrier
       (closes: #514503)
   * dbconfig-common is now maintained in git.  Update control info
     accordingly, and introduce a gbp.conf in the debian subdir for
     git-buildpackage.
   * Misc lintian fixes:
     - update Standards-Version to 3.8.1 (no changes needed).
     - fix Build-Depends for gs -> ghostscript
     - remove Build-Depends alternatives on packages that were only needed
       for etch (tetex-bin, tetex-extra).
Checksums-Sha1: 
 2310c906586105c1549770cc8487516230cdf8af 994 dbconfig-common_1.8.41.dsc
 21b40e3294cc03de8b2689fc21b79b24117f0adf 345745 dbconfig-common_1.8.41.tar.gz
 fb2944a5cb3243df7817a96a0e3c239baaab046f 463464 dbconfig-common_1.8.41_all.deb
Checksums-Sha256: 
 adc3137bd172e831e5aa502d6d68fe10bb14fee7e953457e18feec00e5b311fc 994 
dbconfig-common_1.8.41.dsc
 9ff4f05e4aed2aa72d495a78c68524e8e5ded787182498781ab5e842d5ff0e3c 345745 
dbconfig-common_1.8.41.tar.gz
 ff889ddf14af45cde8ec103f489ea6fadb28a2e277bc1d60e1382915baf42665 463464 
dbconfig-common_1.8.41_all.deb
Files: 
 0761b19379b127b5a3157416907c49d8 994 admin optional dbconfig-common_1.8.41.dsc
 d3424958b1cf950a67c384804c1af4be 345745 admin optional 
dbconfig-common_1.8.41.tar.gz
 61a7fcf0c83d5a2ced2df08482055033 463464 admin optional 
dbconfig-common_1.8.41_all.deb

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

iD8DBQFJvN5tynjLPm522B0RAtXvAJ0dUCFxDLPgdYwJGP50nEEB3IBlvQCfVKrp
M2Sr3a6Shd+kAcsx1zoXt9M=
=fQhx
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to