I am trying to install Bottles and Bitwig Studio, both are on AUR but are not showing in a search under pamac-GTK (pamac-manager). I have enabled AUR support under the Third party tab and refreshed the databases.
Moderator edit: Topic title edited to removed erroneous reference to Pacman.
I have only ever updated this system using pacman -Syu or pacman -Syuu. I am unsure what these packages are for. I am unsure how to fix this. I cannot seem to remove those packages and I guess they are left overs.
For the rest of the AUR packages … they should likely be removed as well, especially if you dont know what they are, especially if they are never updated. Though some you may have inadvertently recieved as a replacement for a regular package. llvm-libs-git is an example - maybe you dont need the AUR package once you remove other unneeded third party packages, but you do wish to have llvm-libs from the repos.
It will be up to you to sort through these and make such determinations.
But there should be no problem simply removing the more obvious roadblock python-shiboken2 and pyside2 packages.
OK removed them and got much further… Is the landlock warning due to my kernel version ?
pamac update --aur --force-refresh
Preparing…
==== AUTHENTICATING FOR org.manjaro.pamac.commit ====
Authentication is required to install, update, or remove packages
Authenticating as: David (david)
Password:
==== AUTHENTICATION COMPLETE ====
Synchronizing package databases…
Error: restricting filesystem access failed because the landlock rule for the temporary download directory could not be added!
Refreshing core.db…
Refreshing extra.db…
Refreshing community.db…
Refreshing multilib.db…
Error: restricting filesystem access failed because the landlock rule for the temporary download directory could not be added!
Refreshing core.files…
Refreshing extra.files…
Refreshing community.files…
Refreshing multilib.files…
Refreshing AUR…
Nothing to do.
Transaction successfully finished.
Likely, yes, as the feature was not available until kernel ~6.2 (?).
You can also disable the sandbox feature thing for pacman via the option in its config and/or --disable-sandbox flag. I have no idea how this affects pamac or how pamac is using it etc. Pamac is supposedly built directly on ALPM and intended to be a pacman replacement, but still uses various pacman resources.
BONUS
We might be interested in your foreign packages in general. Or orphans. To print both groups:
pacman -Qmq
pacman -Qdtq
And you still need to manage your pacnews. To print them all:
pacdiff -o
(if you dont have pacdiff … then please install pacman-contrib package)
For most of these it will be up to you to decide whether they are desirable or not.
But i can point out a few that dont even exist in the AUR … so are very very likely candidates for removal.
But I will make a note again that its possible you somehow have some of these packages instead of the defaults. Make sure you have grub-theme-manjaro for example. Or if you want what ipw2***-fw provided to install ipw2x00-firmware from the AUR instead. I dont know the composition of that alien systemd-fsck-silent package, but make sure you have regular systemd installed.
The rest are … simply regular AUR packages. gcolor2 is a GTK2 color selector application. Maybe you want it. I do not know (though with the gtk2 toolkit being so old, it is probably an odd choice).
Orphans are a slightly different scenario. These are all packages that were installed as a dependency of another package, but are now not required by any other package.
Sometimes this can include still desirable packages. In that case the package should be marked as ‘explicitly installed’ - which will make it no longer an orphan.
Managing orphans is a whole other subject so here is the Archwiki on that;
I am a bit concerned in removing some of these such as the systemd one for example and the web-installer-url-handler which says is used to download software from software.manjaro.org.
All of these should be removed.
The only extra considerations are
1 - Make sure to have regular systemd installed.
2 - If that ipw2** firmware is desirable for you then it should be replaced with ipw2x00-firmware (AUR - Firmware for ipw2100 and ipw2200 drivers)
3 - The firmware packages you have retained makes me wonder about any desire for the current packages as they are split, with all of these available in the repos;
But as you can see the majority are for very specific pieces of hardware and are only helpful in the case you are actually using those devices.
So if we assume you dont need any of the firmware replacements (again even removing these is not in question - only whether you want something similar that does exist), and we make extra double sure you have systemd;
This is covered above. You dont need that package, but if it is somehow replacing regular systemd, then install systemd which will replace it. If not, then its simply ok to remove.
This was never actually very helpful.
It was supposed to make it easier to click on links at that web URL and then install a package that way.
(I wont get into the actual makeup … both the software and the site had issues)
But that address does not even truly exist anymore and now redirects to a third-party branch-compare tool Branch compare for Manjaro.
The package has absolutely no practical use today.
Thank you for all the help. I will continue to clean up any foreign packages but may just leave the orphan ones for now. Systemd was already installed so the systemd-fsck-silent was not needed. No idea what it even does.
At one point it was used to set the systemd automatic filesystem check during boot to ‘silent’ (not print text on the screen).
Its not needed, could be set other ways, but is also usurped by the current default boot setup (that does not even use systemd’s fsck* and also uses plymouth boot splash with no text on screen).
If my memory serves - the package doesnt exist anymore, so I cant really inspect it.
* This doesnt mean you dont have fsck check. If you look in /etc/mkinitcpio.conf you should see fsck on the end of the HOOKS line - this means that the filesystem check will happen before mounting. For more info see: fsck - ArchWiki
Cheers. Happy penguining.
And dont forget to manage those pacnews.
( We are confident you have some, because one such would be /etc/pacman.conf.pacnew, which would show the [community] repo removed among other changes. )
I have cleared the remaining foreign left over packages and all is well now. I will check through the orphans and maybe remove any that are not likely to be needed again. pacnews is now installed to keep tabs on important info. And I have now installed BitWig Studio from AUR which is what started all this off.
Thankyou Again.
PS I am definitely not a Linux expert but have gone from Fedora → Ubuntu → Solus → Manjaro since 2004. Learning all the time still.