Your message dated Sat, 07 Oct 2006 05:47:13 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#391379: fixed in dbconfig-common 1.8.24
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.23
Severity: serious
Justification: Policy 6.7
Hi,
I am trying to upgrade otrs2 to a new version and get the following errors:
# dpkg -i otrs2_2.1.1-1_all.deb
(Reading database ... 211219 files and directories currently installed.)
Preparing to replace otrs2 2.0.4p01-15 (using otrs2_2.1.1-1_all.deb) ...
Unpacking replacement otrs2 ...
Setting up otrs2 (2.1.1-1) ...
dbconfig-common: writing config to /etc/dbconfig-common/otrs2.conf
Replacing config file /etc/otrs/database.pm with new version
creating database backup in
/var/cache/dbconfig-common/backups/otrs2_2.0.4p01-15.pgsql.
chown: cannot access
`/var/cache/dbconfig-common/backups/otrs2_2.0.4p01-15.pgsql': No such
file or directory
dpkg: error processing otrs2 (--install):
subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
otrs2
The file /var/cache/dbconfig-common/backups/otrs2_2.0.4p01-15.pgsql
has *not* been created. The upgrade did work with older versions of
dbconfig-common. Fresh installations of otrs2 (without upgrade) do
work without errors. My package is available at
http://people.debian.org/~twerner/ .
Regards,
Torsten
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (986, 'testing'), (985, 'stable'), (87, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16.27
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)
Versions of packages dbconfig-common depends on:
ii debconf [debconf-2.0] 1.5.5 Debian configuration management sy
ii ucf 2.0015 Update Configuration File: preserv
dbconfig-common recommends no packages.
-- debconf information:
dbconfig-common/import-oldsettings:
* dbconfig-common/remote-questions-default: false
dbconfig-common/pgsql/revertconf: 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/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.24
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.24.dsc
to pool/main/d/dbconfig-common/dbconfig-common_1.8.24.dsc
dbconfig-common_1.8.24.tar.gz
to pool/main/d/dbconfig-common/dbconfig-common_1.8.24.tar.gz
dbconfig-common_1.8.24_all.deb
to pool/main/d/dbconfig-common/dbconfig-common_1.8.24_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: Sat, 07 Oct 2006 14:37:48 +0200
Source: dbconfig-common
Binary: dbconfig-common
Architecture: source all
Version: 1.8.24
Distribution: unstable
Urgency: high
Maintainer: sean finney <[EMAIL PROTECTED]>
Changed-By: sean finney <[EMAIL PROTECTED]>
Description:
dbconfig-common - common framework for packaging database applications
Closes: 391379 391557
Changes:
dbconfig-common (1.8.24) unstable; urgency=high
.
* updated spanish debconf translations from Javier Fernández-Sanguino Peña
(closes: #391557)
* don't try to chown a non-existant file in _dbc_pg_dump(). thanks to
Torsten Werner for finding this (closes: #391379).
* rc bugfix <=> high priority.
Files:
8a6aa9826d8d858e196de2650227a3e6 561 admin optional dbconfig-common_1.8.24.dsc
c67d00f555ed3c6c12dcf217ae1254b6 247564 admin optional
dbconfig-common_1.8.24.tar.gz
3510ac48d3019c9132e6b6e44f64df42 429814 admin optional
dbconfig-common_1.8.24_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFJ6CdynjLPm522B0RAuN4AJ91HTuOJ4VFlWbr62x2w+0pq+l88wCdHONv
XEEj2b4RgFSEibkxGG+6W9Q=
=b0oN
-----END PGP SIGNATURE-----
--- End Message ---
