Your message dated Thu, 20 Nov 2014 13:42:29 +0100
with message-id <546de1b5.2000...@debian.org>
and subject line Re: Bug#769335: otrs2: fails to upgrade from 'wheezy':
/usr/share/dbconfig-common/scripts/otrs2/upgrade/pgsql/3.2.1 exited with
non-zero status
has caused the Debian Bug report #769335,
regarding otrs2: fails to upgrade from 'wheezy':
/usr/share/dbconfig-common/scripts/otrs2/upgrade/pgsql/3.2.1 exited with
non-zero status
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 ow...@bugs.debian.org
immediately.)
--
769335: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769335
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: otrs2
Version: 3.3.9-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'wheezy'.
It installed fine in 'wheezy', then the upgrade to 'jessie' fails.
>From the attached log (scroll to the bottom...):
Setting up otrs2 (3.3.9-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_3.1.7+dfsg1-8+deb7u4.pgsql.
applying upgrade script for 3.1.7+dfsg1-8+deb7u4 -> 3.2.1.
Can't locate /etc/otrs/database.pm: Permission denied at
/usr/share/otrs/Kernel/Config.pm line 27.
BEGIN failed--compilation aborted at /usr/share/otrs/Kernel/Config.pm line 37.
Compilation failed in require at ./scripts/DBUpdate-to-3.2.pl line 32.
BEGIN failed--compilation aborted at ./scripts/DBUpdate-to-3.2.pl line 32.
error encountered processing
/usr/share/dbconfig-common/scripts/otrs2/upgrade/pgsql/3.2.1:
/usr/share/dbconfig-common/scripts/otrs2/upgrade/pgsql/3.2.1 exited with
non-zero status
dbconfig-common: otrs2 configure: aborted.
dbconfig-common: flushing administrative password
dpkg: error processing package otrs2 (--configure):
subprocess installed post-installation script returned error exit status 1
Setting up libsoap-lite-perl (1.11-1) ...
Processing triggers for libc-bin (2.19-12) ...
Processing triggers for ca-certificates (20141019) ...
Updating certificates in /etc/ssl/certs... 10 added, 8 removed; done.
Running hooks in /etc/ca-certificates/update.d....done.
Errors were encountered while processing:
otrs2
cheers,
Andreas
otrs2_3.3.9-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Hi,
I am closing this invalid bug (fixed with dbconfig-common).
Am 14.11.2014 um 17:36 schrieb Patrick Matthäi:
Am 14.11.2014 um 10:54 schrieb Paul Gevers:
=> dbconfig creates and handle database.pm and it is generated with the
following values:
dbc_generate_include_owner="otrs:www-data"
dbc_generate_include_perms="0640"
=> Can't locate /etc/otrs/database.pm: Permission denied at
/usr/share/otrs/Kernel/Config.pm line 27.
=> line 26 checks for the existance of database.pm. if it exists (-f)
then a require is executed in line 27, which is the case here, but you
have got wrong permissions? which ones?
=> this whole issue is not triggered in my manual wheezy->jessie upgrade
process
=> and again, dbconfig-common handles this file, but I think the bug is
in your testing suite/piuparts
We had a bug in dbconfig-common exactly in this area. It might be that
this bug is a duplicate of bug 767248 that was fixed recently.
Much thanks for pointing to this Paul!
@Andreas:
Could you please retest with an up-to-date dbconfig-common?
--
/*
Mit freundlichem Gruß / With kind regards,
Patrick Matthäi
GNU/Linux Debian Developer
Blog: http://www.linux-dev.org/
E-Mail: pmatth...@debian.org
patr...@linux-dev.org
*/
--- End Message ---
