python-commandnotfound conflicts with command-not-found from precise
Bug #1296072 reported by
Rolf Leggewie
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
One Hundred Papercuts |
Invalid
|
Low
|
Unassigned | ||
command-not-found (Ubuntu) |
Fix Released
|
Low
|
Michael Vogt |
Bug Description
http://
http://
I ran into this when upgrading from precise to trusty. Both the command-not-found precise package as well as the python-
Related branches
description: | updated |
Changed in command-not-found (Ubuntu): | |
status: | Triaged → In Progress |
assignee: | nobody → Michael Vogt (mvo) |
Changed in command-not-found (Ubuntu): | |
status: | In Progress → Fix Committed |
Changed in hundredpapercuts: | |
status: | Triaged → Invalid |
To post a comment you must log in.
No need for Conflicts, just Breaks/Replaces is enough. Let's not complicate the apt dist-upgrade logic.