[Bug 1844651] Re: command-not-found-data package is unnecessary

[Launchpad Bug Tracker]

This bug was fixed in the package command-not-found - 19.10.0

---------------
command-not-found (19.10.0) eoan; urgency=medium

  * If the database is absent, do not crash with a backtrace, but tell the
    user to run apt update.
  * Remove the command-not-found-data package (LP: #1844651)

 -- Julian Andres Klode <juliank at ubuntu.com>  Mon, 07 Oct 2019 17:08:21
+0200

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

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to command-not-found in Ubuntu.
https://bugs.launchpad.net/bugs/1844651

Title:
  command-not-found-data package is unnecessary

Status in command-not-found package in Ubuntu:
  Fix Released
Status in command-not-found source package in Eoan:
  Fix Released

Bug description:
  The command-not-found package has been modified to get command
  information (Commands-* files) from the Ubuntu archive subsequently
  the command-not-found-data package, which requires regular manually
  updating, should be removed. As a reference here is a previous
  changelog entry regarding dropping the package.

  command-not-found (18.04.0~pre1) bionic; urgency=medium

    * New version:
      - switch from gdbm to sqlite (smaller files and faster searches)
      - will fetch "dists/bionic/*/binary-*/cnf/Commands-* files
        once the archive provides them
      - CLI output follows what is outlined in LP: #1749777
      - command-not-found-data switched to consume Commands-* files
        (package can be dropped/emptied once server side Commands-* files
         are available)
      - support for suggestions based on snap packages
      - add autopkgtest to the package

   -- Michael Vogt <michael.vogt at ubuntu.com>  Wed, 28 Feb 2018 14:26:58
  +0100

  That being said it would be good if the commands.db (/usr/share
  /command-not-found/commands.db) was built during the image building
  process so that command-not-found will work immediately after
  installation.

  Additionally, if commands.db does not exist command-not-found should
  produce an error message along the lines of "No command-not-found
  database generated yet, please run "sudo apt update"".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/1844651/+subscriptions