Race during release-upgrade (was: Error while upgrading from gutsy to hardy)
Bug #228972 reported by
Frank Simon
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
command-not-found |
Won't Fix
|
Low
|
Unassigned | ||
command-not-found (Ubuntu) |
Confirmed
|
Low
|
Unassigned |
Bug Description
libapt-
Traceback (most recent call last):
File "/usr/lib/
from CommandNotFound import CommandNotFound
File "/usr/lib/
from CommandNotFound import CommandNotFound
File "/usr/lib/
import apt_pkg
ImportError: libapt-
Python version: 2.5.2 alpha 0
bash: dpkg--reconfigure: command not found
Changed in command-not-found: | |
status: | In Progress → Won't Fix |
milestone: | 0.2.42 → none |
To post a comment you must log in.
Thanks for your bugreport.
I assume this did happen *during* the upgrade (i.e. while the upgrade was running on a different terminal and you typed a command that triggered command-not-found?