Your message dated Tue, 30 May 2006 14:32:12 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#368219: fixed in dbconfig-common 1.8.14
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.12
Severity: important

Hello,


the package cannot be installed:

--------
# dpkg -i db-test-pgsql_2.0_all.deb
Selecting previously deselected package db-test-pgsql.
(Reading database ... 144326 files and directories currently installed.)
Unpacking db-test-pgsql (from db-test-pgsql_2.0_all.deb) ...
Setting up db-test-pgsql (2.0) ...
dbconfig-common: writing config to /etc/dbconfig-common/db-test-pgsql.conf

Creating config file /etc/dbconfig-common/db-test-pgsql.conf with new version
creating postgres user dbtestpgsql:  success.
verifying creation of user: success.
creating database dbtestpgsql: success.
verifying database dbtestpgsql exists: success.
populating database via administrative sql...  chown: `dbtestpgsql': invalid 
user
error encountered populating database:
Unknown id: dbtestpgsql
dbconfig-common: db-test-pgsql configure: aborted.
dbconfig-common: flushing administrative password
dpkg: error processing db-test-pgsql (--install):
 subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
 db-test-pgsql
---------

I have installed a local postgreql-8.0 package. The db user and the db
is created but no tables. Purging the package works though.

Another question: How can I use a remote database? There were no
questions during the installation that allowed installation on a remote
database.

I have set the severity to important, because I want to use
dbconfig-common for my own packages but this bug makes it completely
useless to me.


Regards,
Torsten


-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (88, 'testing'), (87, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.16.14
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)

Versions of packages dbconfig-common depends on:
ii  debconf [debconf-2.0]         1.4.30.13  Debian configuration management sy
ii  pwgen                         2.03-1     Automatic Password generation
ii  ucf                           1.17       Update Configuration File: preserv

-- debconf information:
  dbconfig-common/import-oldsettings:
  dbconfig-common/pgsql/revertconf: false
  dbconfig-common/db/dbname: ${pkg}
  dbconfig-common/pgsql/manualconf:
  dbconfig-common/dbconfig-remove: true
  dbconfig-common/mysql/method: unix socket
  dbconfig-common/upgrade-backup: true
  dbconfig-common/performing_upgrade: false
  dbconfig-common/pgsql/authmethod-admin: ident
  dbconfig-common/upgrade-error: abort
  dbconfig-common/purge: false
  dbconfig-common/install-error: abort
  dbconfig-common/pgsql/no-empty-passwords:
  dbconfig-common/pgsql/admin-user: postgres
  dbconfig-common/dbconfig-install: true
  dbconfig-common/remote/host:
  dbconfig-common/pgsql/changeconf: false
  dbconfig-common/remote/newhost:
  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: ident
  dbconfig-common/database-type:
  dbconfig-common/db/app-user:
  dbconfig-common/remote/port:


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

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.14.dsc
  to pool/main/d/dbconfig-common/dbconfig-common_1.8.14.dsc
dbconfig-common_1.8.14.tar.gz
  to pool/main/d/dbconfig-common/dbconfig-common_1.8.14.tar.gz
dbconfig-common_1.8.14_all.deb
  to pool/main/d/dbconfig-common/dbconfig-common_1.8.14_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: Tue, 30 May 2006 23:15:35 +0200
Source: dbconfig-common
Binary: dbconfig-common
Architecture: source all
Version: 1.8.14
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: 366761 368219 368714
Changes: 
 dbconfig-common (1.8.14) unstable; urgency=low
 .
   [sean finney]
   * provide a new hint option dbc_sql_substitutions, which will pipe
     all provided sql files through the template-based substitution
     filter of dbconfig-generate-include before being processed
     (closes: #366761).
   * andrew mcmillan found a spelling error, so i ran aspell over all
     the documentation :)
   * provide a new hint option dbc_authmethod_user for the packager
     to provide the "sane default" for how the application's database
     user should authenticate for pgsql applications (closes: #368219).
     we'll soon provide a better (automagic) detection, but it shouldn't
     break things if you start using this feature before then.
   * extra sanity check for a glob that might not expand in some circumstances,
     from matt brown (closes: #368714).
   * more code consolidation, configfile-vs-debconf fixes, removal of some
     obsolete code/templates.
Files: 
 95104251f20d34f74c8a000912f03817 549 admin optional dbconfig-common_1.8.14.dsc
 59ab3aaa1a36f3fde2de169423046160 191793 admin optional 
dbconfig-common_1.8.14.tar.gz
 e7dfde39709730235f5d725c4ceaa410 343846 admin optional 
dbconfig-common_1.8.14_all.deb

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

iD8DBQFEfLgdynjLPm522B0RAtUAAJ0bLF4y8sElFEZxSVW9yECp9n25UgCeLy8z
/awhh4Ne4q9Yv7DzLuNc5bE=
=KmLe
-----END PGP SIGNATURE-----


--- End Message ---

Reply via email to