doesn't cope with db format transition
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
command-not-found (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Binary package hint: command-not-found
Python recently moved to db4.6. After this, any unknown command produces:
Unable to open binary database %s: %s /usr/share/
Unable to open binary database %s: %s /usr/share/
Unable to open binary database %s: %s /usr/share/
Unable to open binary database %s: %s /usr/share/
Unable to open binary database %s: %s /usr/share/
Unable to open binary database %s: %s /usr/share/
Unable to open binary database %s: %s /usr/share/
Unable to open binary database %s: %s /usr/share/
(ignoring the buggy error message, already filed as bug 131435)
Something needs to cope with upgrading the db format, preferably on the fly; I believe that Berkeley DB has an 'upgrade' method for this.
Changed in command-not-found: | |
status: | New → Confirmed |
Changed in command-not-found: | |
status: | Confirmed → Fix Released |
Confirming. I'm seeing this too on a fresh gutsy install.