Package: command-not-found Version: 20.10.1-1 Severity: grave Justification: renders package unusable
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917455 Bug #917455 was closed with: Marked as fixed in versions 20.10.1-1 This is *NOT* the case! After upgrading to bullseye, which includes command-not-found 20.10.1-1, the bug is there again! % foo Sorry, command-not-found has crashed! Please file a bug report at: http://www.debian.org/Bugs/Reporting Please include the following information with the report: command-not-found version: 0.3 Python version: 3.9.2 final 0 Distributor ID: Debian Description: Debian GNU/Linux 11 (bullseye) Release: 11 Codename: bullseye Exception information: unable to open database file Traceback (most recent call last): File "/usr/share/command-not-found/CommandNotFound/util.py", line 23, in crash_guard callback() File "/usr/lib/command-not-found", line 90, in main cnf = CommandNotFound.CommandNotFound(options.data_dir) File "/usr/share/command-not-found/CommandNotFound/CommandNotFound.py", line 79, in __init__ self.db = SqliteDatabase(dbpath) File "/usr/share/command-not-found/CommandNotFound/db/db.py", line 12, in __init__ self.con = sqlite3.connect(filename) sqlite3.OperationalError: unable to open database file The temporary fix still works: sudo chmod 644 /var/lib/command-not-found/commands.db But after the next update, the permissions are set wrong again. The actual fix is (and probably always has been) to set in /sbin/update-command-not-found: os.umask (0o022) I see no trace of this having been done. In fact, there's no occurrence of "umask" anywhere in the sources (including Debian patches) -- except for debian/changelog!??? (And a much older changelog entry anyway.) So it doesn't seem this bug was actually ever fixed.
