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)
--
Uploaded 19.10.0 without that package, and with some test suite fixes to
make it work even on systems where no database has been populated yet.
We do not expect there to be any images that do not have a pre-populated
database, hence there should be no need for a UI freeze exception, as
the new
Additionally, after installing the system the commands.db file was
located in /var/lib/command-not-found/ and contained the updated
information regarding installing mlocate for locate.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
With regards to the image building process I booted an Ubuntu 19.10 Beta
iso with serial 20191001.2 and the commands.db file was located in
/var/lib/command-not-found/ with a date of October 1st. So it seems that
image building process, at least for desktop CDs, already includes the
updated
dists/bionic/*/binary-*/cnf/Commands-* do not exist at all on the mirror
network, so it's not clear to me that the replacement for command-not-
found-data is actually implemented at all or where the metadata lives.
** Changed in: command-not-found (Ubuntu Eoan)
Status: Triaged =>
ok, I confirmed they are present for disco and later.
http://archive.ubuntu.com/ubuntu/dists/disco/main/cnf/
** Changed in: command-not-found (Ubuntu Eoan)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Tags added: id-5d8357f8b3d2016342810458
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1844651
Title:
command-not-found-data package is unnecessary
To manage notifications about this bug go to:
