command-not-found-data package is unnecessary
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
command-not-found (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Eoan |
Fix Released
|
Medium
|
Unassigned |
Bug Description
The command-not-found package has been modified to get command information (Commands-* files) from the Ubuntu archive subsequently the command-
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/
once the archive provides them
- CLI output follows what is outlined in LP: #1749777
- command-
(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 <email address hidden> Wed, 28 Feb 2018 14:26:58 +0100
That being said it would be good if the commands.db (/usr/share/
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"".
Changed in command-not-found (Ubuntu Eoan): | |
status: | New → Triaged |
importance: | Undecided → Medium |
tags: | added: id-5d8357f8b3d2016342810458 |
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.