Unresolvable pamac and libpamac conflicts

Issues & Assistance
1

Trying to install the pamac GUI and I ran into a version conflict:

loading packages...
resolving dependencies...
looking for conflicting packages...
:: libpamac-aur-11.7.3-2 and libpamac-full-1:11.7.3-1 are in conflict (libpamac). Remove libpamac-full? [y/N]
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: libpamac-aur-11.7.3-2 and libpamac-full-1:11.7.3-1 are in conflict
loading packages...
resolving dependencies...
looking for conflicting packages...
:: libpamac-aur-11.7.3-2 and libpamac-full-1:11.7.3-1 are in conflict (libpamac). Remove libpamac-full? [y/N]
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: libpamac-aur-11.7.3-2 and libpamac-full-1:11.7.3-1 are in conflict
loading packages...
resolving dependencies...
looking for conflicting packages...
:: libpamac-aur-11.7.3-2 and libpamac-full-1:11.7.3-1 are in conflict (libpamac). Remove libpamac-full? [y/N]
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: libpamac-aur-11.7.3-2 and libpamac-full-1:11.7.3-1 are in conflict
error: packages failed to build: pamac-aur-11.7.3-1  pamac-all-11.7.3-1

Is this a problem with pamac upstream that needs to be fixed by Manjaro, or is this an issue with the packages maintained in Cachy’s repo? Is there a way to force the installer to ignore libpamac-aur and pamac-aur and only install the -full versions, or is this some weird cross-dependency that can’t be fixed?

I don’t mind using Discover and octopi separately in the meantime but I’d like to have a one-stop shop for both AUR and flatpak.

2

Fair warning that pamac is perpetually broken - both due to oddities in how it interfaces with ALPM (it does not use pacman as a backend) and oddities in its own ideas about how to parse information. It might also break permissions of its own build directory, etc.
I would suggest to not use pamac at all.

Fair warning not to use discover to manage packages (themes or flatpaks should be alright) - as it would be using packagekit (not ALPM) which is both buggy on Arch/Cachy and opens up system permissions (unsecure).

What command did you use exactly to try to install it?

3

Is there another tool which will give me more of a “storefront” for AUR like Pamac or Discover?

Whatever version is provided in Cachy repos only offers flatpak, there doesn’t seem to be a version which provides support for system packages.

First I just tried

paru -S pamac-all

before finding another thread here which suggested

yay -a pamac-all

I did attempt to clean/remove conflicting packages before attempting both, but both commands ended with the same conflict.

4

The error message is simply telling you that you can not have both pamac-all and pamac-aur installed at the same time. They conflict with each other.

You can have one or the other but not both.

5

I’ve been using Manjaro for four days now. Not because I’m convinced, but to either refute or confirm the statements of previous users. The minimal installation with Wayland and my preferred kernel runs perfectly.
But using Manjaro’s Pamac on other distros is just plain stupid.

6

The problem is, something (I can’t figure out what) is attempting to install both at the same time, and I don’t know why. If it was that easy I wouldn’t be here asking for help.

7

Alright, then I won’t bother asking for further help, despite the number of people who recommend using pamac in other Arch-based distros as an alternative to the command line.

8

You’re always welcome to do whatever you want, just keep your installation media handy.

9

You have CachyOS Package Installer and Octopi already installed.
If you use Cachy, you have to follow the advice of people who use Cachy and not people who use other distros!

10

sudo pacman -S pamac-aur

11

Would you personally recommend Pamac for CachyOS?

12

Sadly its one of the “best” in terms of usability - the only problem is that it uses its own pacman backend and we need to patch it to be compatible with cachyos and its opimized repositorys.

Would be another huge project working on a proper gui manager for archlinux

13

Thank you for your detailed answer.

14

Never got a notification for a response on this, but thank you for the clarification.