After a recent update to Python on unstable, the AUR helper I sometimes use - pikaur - was temporarily disabled. When I reported this somebody asked me why I didn’t use pamac for aur support. My answer to this was that I did use it when on Manjaro, but when I use Manjaro to update another arch based distro through systemd-nspawn, Pamac doesn’t work and I have to use pikaur which does.
This usage for pamac is such a niche case, that I have never bothered to report it before, but I decided to do so now. You might not think it worth the time and trouble to address the problem and to be quite honest I wouldn’t blame you especially as the workround is so easy - use pikaur (or something else possibly). The problem is this.
pamac update -a
==== AUTHENTICATING FOR org.manjaro.pamac.commit ====
Authentication is required to install, update, or remove packages
Authenticating as: manjaro
Supply the password and the job is done.
But on Manjaro terminal running through systemd-nspawn to Artix linux the result is:
pamac update -a
** (pamac:6): WARNING **: 12:30:05.522: transaction_interface_daemon.vala:47: failed to connect to dbus daemon: Could not connect: No such file or directory
Authorization not available. Check if polkit service is running or see debug message for more information.
** (pamac:6): CRITICAL **: 12:30:06.522: pamac_daemon_start_get_authorization: assertion ‘self != NULL’ failed
Obviously no authentication mechanism possible.
Same usage again but now using pikaur:
spawning container artix on /mnt/artix.
Press ^] three times within 1s to kill container.
[artix@artix ~]$ pikaur -Syu
[sudo] password for artix:
Password prompt now visible and command runs normally.
So that is the problem. Another problem is the missing man page for pamac, but I see that is under active discussion and somebody has actually written one.