Package: command-not-found
Version: 20.10.1-1
Followup-For: Bug #943989
X-Debbugs-Cc: tmcconnell...@gmail.com
Dear Maintainer,
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
On Thu, Apr 08, 2021 at 06:33:55PM +0200, Julian Andres Klode wrote:
> On Sat, Apr 03, 2021 at 11:05:32AM +0200, Raphael Hertzog wrote:
> > So the latest version doesn't have the same error message (with "cnf"
> > variable being unbound) but it still doesn't fail gracefully when
> > the database is
On Sat, Apr 03, 2021 at 11:05:32AM +0200, Raphael Hertzog wrote:
> So the latest version doesn't have the same error message (with "cnf"
> variable being unbound) but it still doesn't fail gracefully when
> the database is not available.
>
> Instead of asking to file bug reports, it should tell th
On Thu, Apr 08, 2021 at 06:24:38PM +0200, Julian Andres Klode wrote:
> On Sat, Apr 03, 2021 at 11:05:32AM +0200, Raphael Hertzog wrote:
> > So the latest version doesn't have the same error message (with "cnf"
> > variable being unbound) but it still doesn't fail gracefully when
> > the database is
On Sat, Apr 03, 2021 at 11:05:32AM +0200, Raphael Hertzog wrote:
> So the latest version doesn't have the same error message (with "cnf"
> variable being unbound) but it still doesn't fail gracefully when
> the database is not available.
>
> Instead of asking to file bug reports, it should tell the
So the latest version doesn't have the same error message (with "cnf"
variable being unbound) but it still doesn't fail gracefully when
the database is not available.
Instead of asking to file bug reports, it should tell them to run "apt
update". This bad behaviour is now generating quite some noi
6 matches
Mail list logo
