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" > (which I normally use). > > 3. After some digging, I found a solution that actually works: > > chmod 644 /var/lib/command-not-found/commands.db > > 4. The actual bug is not setting a correct umask in > update-command-not-found. Was OK in stetch.
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. I'll try to get it fixed for the point release. -- debian developer - deb.li/jak | jak-linux.org - free software dev ubuntu core developer i speak de, en
