Your message dated Tue, 23 Feb 2010 22:03:07 +0000
with message-id <[email protected]>
and subject line Bug#569139: fixed in dbconfig-common 1.8.45
has caused the Debian Bug report #569139,
regarding dbconfig-install template has confusing wording
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.)
--
569139: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=569139
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: bacula-director-pgsql
Version: 1.38.9-10
Severity: normal
The failure may arise from my having responded improperly to the
installation questions. If so, this may be a documentation issue more
than anything. Even after the install I don't see much about how to
go from 1.36->1.38.
>From my install:
------------------------------------------------------------
Setting up bacula-director-pgsql (1.38.9-10) ...
Configuring bacula-director-pgsql
---------------------------------
bacula-director-pgsql must have a database installed and configured before it
can be used. If you like, this can be handled with
dbconfig-common.
If you are an advanced database administrator and know that you want to perform
this configuration manually, or if your database has already
been installed and configured, you should refuse this option. Details on what
needs to be done should most likely be provided in
/usr/share/doc/bacula-director-pgsql.
Otherwise, you should probably choose this option.
Configure database for bacula-director-pgsql with dbconfig-common? no
dbconfig-common: writing config to
/etc/dbconfig-common/bacula-director-pgsql.conf
Creating config file /etc/dbconfig-common/bacula-director-pgsql.conf with new
version
Processing configuration .../usr/share/bacula-director/postinst-common: line
18: /etc/bacula/bacula-dir.conf.dpkg-tmp: No such file or directory
Ok.
Stopping Bacula Director: bacula-dir.
Starting Bacula Director: 07-Jun 18:57 bacula-dir: Fatal error: Version error
for database "bacula". Wanted 9, got 8
07-Jun 18:57 bacula-dir: Fatal error: Could not open database "bacula".
07-Jun 18:57 bacula-dir: Fatal error: Version error for database "bacula".
Wanted 9, got 8
07-Jun 18:57 bacula-dir ERROR TERMINATION
Please correct configuration file: /etc/bacula/bacula-dir.conf
failed.
----------------------------------------------------------
The key phrase, as I read it, was "if your database has already been
installed and configured, you should refuse this option." This caused
me to say "no", though even at the time I wasn't sure if "installed
and configured" meant a
1.38 database only. Obviously my responses didn't work.
It was and is not clear to me if the package or dbconfig-common
(1.8.13) provide any kind of upgrade facility. It wasn't clear to me
if upgrading was required; not it is clear that the answer is yes.
I'm uncertain how to proceed. The upstream documentation provided
with the package offers few clues, and even if it did it would be good
to say what the story is for Debian (particularly given the use of
dbconfig-common).
The only thing I've found after installation is
/usr/share/doc/bacula-common/ReleaseNotes.gz, presumably from
upstream. Buried toward the bottom are several statements that the
1.36 and 1.38 database formats differ.
-----------------------------
Major Changes in 1.38:
...
- There is a new database format that is not compatible
with previous databases. You must upgrade if converting
from 1.36.x. No changes from version 1.37.30.
---------------------------------------
That and some other items (e.g., daemons are not compatible with earlier
versions) seem worth flagging for News.Debian to show to all
upgraders.
I suspect similar issues are present with other database backends as
well.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (990, 'testing'), (990, 'stable'), (50, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.4.27advncdfs
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Versions of packages bacula-director-pgsql depends on:
ii bacula-director-common 1.38.9-10 Network backup, recovery and verif
ii dbconfig-common 1.8.13 common framework for packaging dat
ii debconf [debconf-2.0] 1.5.1 Debian configuration management sy
ii postgresql-client 7.5.19 front-end programs for PostgreSQL
ii postgresql-client-8.1 8.1.4-1 front-end programs for PostgreSQL
Versions of packages bacula-director-pgsql recommends:
ii postgresql 7.5.19 object-relational SQL database man
ii postgresql-8.1 8.1.4-1 object-relational SQL database, ve
-- debconf information:
bacula-director-pgsql/pgsql/authmethod-admin: ident
bacula-director-pgsql/pgsql/no-empty-passwords:
bacula-director-pgsql/upgrade-backup: true
bacula-director-pgsql/install-error: abort
* bacula-director-pgsql/create_tables: false
bacula-director-pgsql/purge: false
* bacula-director-pgsql/pgsql_root_username: postgres
bacula-director-pgsql/pgsql/method: unix socket
bacula-director-pgsql/db/app-user:
bacula-director-pgsql/db/dbname: ${pkg}
bacula-director-pgsql/remote/host:
bacula-director-pgsql/pgsql/admin-user: postgres
bacula-director-pgsql/database-type:
bacula-director-pgsql/remote/port:
* bacula-director-pgsql/remove_catalog_on_purge: false
bacula-director-pgsql/drop_db: false
bacula-director-pgsql/remote/newhost:
bacula-director-pgsql/performing_upgrade: false
bacula-director-pgsql/remove-error: abort
bacula-director-pgsql/passwords-do-not-match:
bacula-director-pgsql/internal/reconfiguring: false
bacula-director-pgsql/pgsql/authmethod-user: ident
bacula-director-pgsql/import-oldsettings:
* bacula-director-pgsql/db_host: localhost
bacula-director-pgsql/pgsql/manualconf:
* bacula-director-pgsql/dbconfig-install: false
bacula-director-pgsql/dbconfig-upgrade: true
bacula-director-pgsql/db_user: bacula
bacula-director-pgsql/dbconfig-remove: true
bacula-director-pgsql/upgrade-error: abort
bacula-director-pgsql/pgsql/changeconf: false
--- End Message ---
--- Begin Message ---
Source: dbconfig-common
Source-Version: 1.8.45
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.45.dsc
to main/d/dbconfig-common/dbconfig-common_1.8.45.dsc
dbconfig-common_1.8.45.tar.gz
to main/d/dbconfig-common/dbconfig-common_1.8.45.tar.gz
dbconfig-common_1.8.45_all.deb
to main/d/dbconfig-common/dbconfig-common_1.8.45_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: Tue, 23 Feb 2010 21:45:36 +0100
Source: dbconfig-common
Binary: dbconfig-common
Architecture: source all
Version: 1.8.45
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: 443279 525371 542381 569139
Changes:
dbconfig-common (1.8.45) unstable; urgency=low
.
* Change behavior for automated installs when no local database is
available (Closes: #542381)
* Make sure the admin always sees the "purge database?" question
- thanks to Brett Profitt <[email protected]> (Closes: #525371).
* Remove original fix for #542381, as the second fix is better.
* Bump debhelper compatibility level to 5
* Update lintian overrides
* Update Standards-Version to 3.8.4 (no changes needed)
* Use the upgrade prompt for migrating from non-dbc versions.
(Closes: #569139)
* Fix overzealous error checking which causes some settings not to
migrate (Closes: #443279).
Checksums-Sha1:
05e2045219a22aa2610864acf5d098c845a947e8 991 dbconfig-common_1.8.45.dsc
b938631d9b31a53890d4059518c8de7e2041e65c 358680 dbconfig-common_1.8.45.tar.gz
135ff2872190c7319b2396976b8aeeb7a9d06733 475630 dbconfig-common_1.8.45_all.deb
Checksums-Sha256:
6e4642ddb98046d9dfdfb80f1d8ae78e1a9c4a5c6fc45b47b669349fe93f7e9d 991
dbconfig-common_1.8.45.dsc
e8218fa4212f7b79c63a9d40fa46170cf02ee6fe11d14b9b0797a30d03c678b9 358680
dbconfig-common_1.8.45.tar.gz
8796247d8d5c0c1bfe9af29dac66adc32e8f9cf36d8f8b0df657d312c32c8fcb 475630
dbconfig-common_1.8.45_all.deb
Files:
c8aaac43ab88fff3624fd1c7a98cce87 991 admin optional dbconfig-common_1.8.45.dsc
71be89b1ecfc09de32cacc5d2cffbc0c 358680 admin optional
dbconfig-common_1.8.45.tar.gz
a2c1ce74d2e5c11fb613911dedfd59d0 475630 admin optional
dbconfig-common_1.8.45_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iD8DBQFLhD7CynjLPm522B0RAl11AJ0QFDLUwhwQuN8OGNoDe+aIJiiIdwCfWDYC
f23mTtAytUTsZs25h7841UY=
=h8xp
-----END PGP SIGNATURE-----
--- End Message ---
