> ack. I misremembered. It's funny that it works fine for its
> entire lifetime in Ubuntu, and only Debian users seem to be
> using different umasks for root. Kind of a niche thing.
Though it's getting off-topic, a reason may be that Ubuntu is used
more often on personal desktops (where, honestly,
On Thu, Jul 11, 2019 at 12:36:34AM +0200, Frank Heckenbach wrote:
> > It's a minor issue of a missing database that fixes itself the
> > next time you run apt update.
>
> 1. If it's so easy, why wasn't it mentioned before?
>
> 2. Didn't work for me, neither "apt update", nor "apt-get update"
>
> It's a minor issue of a missing database that fixes itself the
> next time you run apt update.
1. If it's so easy, why wasn't it mentioned before?
2. Didn't work for me, neither "apt update", nor "apt-get update"
(which I normally use).
3. After some digging, I found a solution that actuall
On Wed, Jul 10, 2019 at 11:22:13PM +0200, Frank Heckenbach wrote:
> I get the same crash every time!
>
> Is there any workaround? Otherwise, it seems the package is totally
> broken. Shouldn't this be "grave" then?
>
> And why include it in the stable release at all if it doesn't work?
> I've see
I get the same crash every time!
Is there any workaround? Otherwise, it seems the package is totally
broken. Shouldn't this be "grave" then?
And why include it in the stable release at all if it doesn't work?
I've seen packages banned for less severe reasons.
Apparently, the problem has been kno
I confirm the bug on a stretch upgraded to buster just now.
Regards,
--
Matteo Croce
per aspera ad upstream
Package: command-not-found
Version: 18.04.5-1
Followup-For: Bug #917455
Dear Maintainer,
After installing command-not-found on a debian buster fresh install
update-command-not-found was an unknown command.
It appeared also that the "useradd" command was an unknow command. After a few
trials, a
Hi Aspen (cc bug#917455),
Thanks for reporting this issue!
Please consider mention more prominently when you file bugreports
upstream. Included data hints that you run PureOS, but it can be
helpful for the work tracking down the cause of the bug if you highlight
that detail e.g. by mentioning
Package: command-not-found
Version: 18.04.5-1
Severity: important
Tags: a11y
Dear Maintainer,
command-not-found version: 0.3
Python version: 3.7.2 candidate 1
Distributor ID: PureOS
Description:PureOS GNU/Linux 8
Release:8
Codename: green
Exception information:
local variable
9 matches
Mail list logo