mohnkern
May 8th, 2008, 02:11 PM
The other day I used aptitude to install Bugzilla, and it failed. After reading some other posts regarding modifications, it finally was able to configure and run. However now whenever I run sudo apt-get upgrade I get:
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0B of additional disk space will be used.
Do you want to continue [Y/n]? Y
Setting up bugzilla (2.22.1-2.2ubuntu1) ...
dbconfig-common: writing config to /etc/dbconfig-common/bugzilla.conf
Not replacing deleted config file /etc/bugzilla/dbconfig-params
.: 77: Can't open /etc/bugzilla/dbconfig-params
dpkg: error processing bugzilla (--configure):
subprocess post-installation script returned error exit status 2
Errors were encountered while processing:
bugzilla
E: Sub-process /usr/bin/dpkg returned an error code (1)
Problem is, I don't want to remove Bugzilla, now that I've got it working. I just want it to act as those its configured, or alternatively, get the configure not to mess things up.
I ran dpkg --configure bugzilla and it generated the same error.
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0B of additional disk space will be used.
Do you want to continue [Y/n]? Y
Setting up bugzilla (2.22.1-2.2ubuntu1) ...
dbconfig-common: writing config to /etc/dbconfig-common/bugzilla.conf
Not replacing deleted config file /etc/bugzilla/dbconfig-params
.: 77: Can't open /etc/bugzilla/dbconfig-params
dpkg: error processing bugzilla (--configure):
subprocess post-installation script returned error exit status 2
Errors were encountered while processing:
bugzilla
E: Sub-process /usr/bin/dpkg returned an error code (1)
Problem is, I don't want to remove Bugzilla, now that I've got it working. I just want it to act as those its configured, or alternatively, get the configure not to mess things up.
I ran dpkg --configure bugzilla and it generated the same error.