13 ms·
Are you sure you typed exactly that? For `apt-get install purge-old-kernels` I get E: Could not open lock file /var/lib/dpkg/lock - open (13: Permission d
by yorwba 10y ago
Are you sure you typed exactly that?
For `apt-get install purge-old-kernels` I get
E: Could not open lock file /var/lib/dpkg/lock - open (13: Permission denied)
E: Unable to lock the administration directory (/var/lib/dpkg/), are you root?
And for `sudo apt-get install purge-old-kernels`, I get
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package purge-old-kernels
But I can reproduce your error by `purge-old-kernels` alone. That is indeed strange.
EDIT: I straced bash by `strace -o bashlog -f -s 10000 bash` and found the culprit to be /usr/lib/command-not-found. Indeed, if you run `/usr/lib/command-not-found -- purge-old-kernels` directly, you get that same message about byobu.
EDIT2: I assumed this was some kind of bug with the database, but now I actually tried installing byobu and it does make purge-old-kernels available.
- pizza234 10y agoThe first of the two errors has nothing to do with the package itself - packages need root permisions to be managed, which is what exactly the error is telling you: E: Unable to lock the administration directory (/var/lib/dpkg/), are you root? ^^^^^^^^^^^^^ In your case, you didn't prepend `sudo`. Regarding the second, which is instead the core of the problem, see the man page (http://manpages.ubuntu.com/manpages/xenial/man1/purge-old-kernels.1.html http://manpages.ubuntu.com/manpages/xenial/man1/purge-old-ke...): Provided by: byobu_5.106-0ubuntu1_all bug Therefore the correct (and full) command is: sudo apt-get install byobu As pointed out in another comment, such package is arguably a poor placement for this type of utility.
- yorwba 10y agoI'm aware that the first errors don't have anything to do with the package itself, but this was the command line given. I was wondering what kind of setup might lead to an apt-get command (without sudo even) to display that error message.
- pizza234 10y agoOne case (which may be irrelevant in this context, but still a valid scenario) is auto-updates being executed in the background.