[Bug 1296072] Re: python-commandnotfound conflicts with command-not-found from precise

[Launchpad Bug Tracker]

This bug was fixed in the package command-not-found - 0.3ubuntu11

---------------
command-not-found (0.3ubuntu11) trusty; urgency=low

  * python-commandnotfound needs to breaks/replaces with
    command-not-found from precise.  (LP: #1296072)
 -- Rolf Leggewie <foss at rolf.leggewie.biz>   Sat, 22 Mar 2014 23:25:21 +0800

** Changed in: command-not-found (Ubuntu)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1296072

Title:
  python-commandnotfound conflicts with command-not-found from precise

Status in One Hundred Papercuts:
  Triaged
Status in “command-not-found” package in Ubuntu:
  Fix Released

Bug description:
  http://packages.ubuntu.com/trusty/all/python-commandnotfound/filelist
  http://packages.ubuntu.com/precise/all/command-not-found/filelist

  I ran into this when upgrading from precise to trusty.  Both the
  command-not-found precise package as well as the python-
  commandnotfound package in trusty ship the file /usr/lib/python2.7
  /dist-packages/CommandNotFound/__init__.py  The latter package needs
  to conflicts/breaks/replaces with the former, versions prior to
  0.3ubuntu7.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1296072/+subscriptions