Dapper: installation failure in debconfig
This bug report was converted into a question: question #47312: Dapper: installation failure in debconfig.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
debconf (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: debconf
I failed to upgrade from dapper to hardy, then try to reinstall dapper. After modified the /etc/apt/
Reading package lists...
Building dependency tree...
debconf is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
3 not fully installed or removed.
After this operation, 0B of additional disk space will be used.
Setting up hwtest (0.1-0ubuntu10) ...
Traceback (most recent call last):
File "/usr/share/
from debconf import Debconf, DebconfCommunicator
ImportError: No module named debconf
dpkg: error processing hwtest (--configure):
subprocess post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of hwtest-gtk:
hwtest-gtk depends on hwtest; however:
Package hwtest is not configured yet.
dpkg: error processing hwtest-gtk (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of ubuntu-desktop:
ubuntu-desktop depends on hwtest-gtk; however:
Package hwtest-gtk is not configured yet.
dpkg: error processing ubuntu-desktop (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
hwtest
hwtest-gtk
ubuntu-desktop
I have manually sudo dpkg-reconfigure debconf, answer a couple question the program prompted me, then reinstall the debconf -- STILL FAILED at the same point. I am not sure this is my system's env problem or the debconf has change name/link for import???
If this is not a bug, please post it to the community forum as a problem.
Thanks!
Cuebee
Dapper has been sucessfully installed before, and work as a production's backend, so I think this may be just some env variable missing or system config file missing. On the other hand, it may due to the debconf developing team has changed in the last two years??? Anybody knows the answer, please kindly post an answer. Thanks!