O.K. after marking an orphan as 'explicitly installed', now the cleanup of orphans fails

So I invoked the command to protect one of my orphans (PlayonLinux), and while doing the normal sequence of maintenance the command that removes the orphans no longer functions:

[markal@markal-optiplex390 ~]$ sudo pacman -D --asexplicit playonlinux
playonlinux: install reason has been set to ‘explicitly installed’
[markal@markal-optiplex390 ~]$ paccache -r
==> Escalating privileges using sudo

==> finished: 227 packages removed (disk space saved: 3.68 GiB)
[markal@markal-optiplex390 ~]$ paccache -ruk0
==> Escalating privileges using sudo

==> finished: 13 packages removed (disk space saved: 71.41 MiB)
[markal@markal-optiplex390 ~]$ sudo pacman -Rns $(pacman -Qdtq)
error: no targets specified (use -h for help)
[markal@markal-optiplex390 ~]$ pacman -Rns $(pacman -Qdtq)
error: you cannot perform this operation unless you are root.
[markal@markal-optiplex390 ~]$ sudo pacman -Rns $(pacman -Qdtq)
error: no targets specified (use -h for help)
[markal@markal-optiplex390 ~]$

As you can see, I tried 3 times to clean the orphans, it has always worked before, and now it seems broken.

That’s pacman remove these (pacman find orphans). Since there are no orphans there’s nothing to remove, and pacman complains about the “you gave me nothing to remove”.

It’s fine.

3 Likes

Oh, (face palm). Of, course.

That does make sense. I usually end up with some, so I had never seen that output before.

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.