severity #665207 important
tags #665207 + wontfix
thanks
As discussed on IRC this can not be fixed until the fixed version itself
is in testing.
I will close the bug, if the package migrates to testing.
Am 22.03.2012 16:47, schrieb Andreas Beckmann:
Package: otrs2
Version: 3.1.2+dfsg1-3
Severity: serious
User: [email protected]
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 'sid' fails.
From the attached log (scroll to the bottom...):
Setting up otrs2 (3.1.2+dfsg1-3) ...
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.2+dfsg1-2.pgsql.
applying upgrade script for 3.1.2+dfsg1-2 -> 3.1.2+dfsg1-2.1.
DBD::Pg::db do failed: ERROR: column "freekey1" does not exist
LINE 1: SELECT freekey1, freetext1, freetime1 FROM ticket
^ at /usr/share/otrs/Kernel/System/DB.pm line 478.
no connection to syslog available
- /dev/log is not a socket at
/usr/share/otrs/Kernel/System/Log/SysLog.pm line 66
Migration started...
Step 1 of 23: Refresh configuration cache...
If you see warnings about 'Subroutine Load redefined', that's fine, no need
to worry!
done.
Step 2 of 23: Check framework version... done.
Step 3 of 23: Creating DynamicField tables (if necessary)... done.
Step 4 of 23: Create new dynamic fields for free fields (text, key, date)...
error encountered processing
/usr/share/dbconfig-common/scripts/otrs2/upgrade/pgsql/3.1.2+dfsg1-2.1:
/usr/share/dbconfig-common/scripts/otrs2/upgrade/pgsql/3.1.2+dfsg1-2.1
exited with non-zero status
dbconfig-common: otrs2 configure: aborted.
dbconfig-common: flushing administrative password
dpkg: error processing otrs2 (--configure):
subprocess installed post-installation script returned error exit status 1
configured to not write apport reports
Errors were encountered while processing:
otrs2
cheers,
Andreas
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
