Package: command-not-found
Version: 23.04.0-1
Followup-For: Bug #1041872
Dear Maintainer,
I am writing to say that I fixed (at least) one of the problems I described in
the initial bug report.
Every time I typed a wrong command, a warning about "not being able to parse
the sources file" was shown, which was bizarre because "apt" and "aptitude"
work as expected. At the moment of filling the bug report I thought it was a
problem with the file permissions because I had problems to generate the
database even working as root.
After a few weeks, reviewing the status of this bug, I noticed another one
(#1042872) reporting the same warning but with a different file name. It was
pointed out (message #10) that the source file in DEB822-format should not have
a blank line before the 1st APT source. I removed the line in my file and the
warning is gone.
What I don't know is whether this problem was also the origin of not being able
to generate the database initially.
Feel free to close the bug, although I think there should be a note somewhere
about this issue when installing this package. The sources.list(5) man page is
clear when it describes the format of the sources files in DEB822 style.
".... Individual entries are separated by an empty line; additional
empty lines are ignored, and a # character at the start of the line
marks the entire line as a comment."
Thank you for maintaining the package. Regards.
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.4.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=ca_ES.UTF-8, LC_CTYPE=ca_ES.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages command-not-found depends on:
ii apt-file 3.3
ii lsb-release 12.0-2
ii python3 3.11.4-5+b1
ii python3-apt 2.6.0
command-not-found recommends no packages.
Versions of packages command-not-found suggests:
pn snapd <none>
-- no debconf information
