Package Details: pamac-flatpak 11.7.2-1

Git Clone URL: https://aur.archlinux.org/pamac-flatpak.git (read-only, click to copy)
Package Base: pamac-flatpak
Description: A GUI frontend for libalpm. With Flatpak support
Upstream URL: https://github.com/manjaro/pamac
Licenses: GPL3
Conflicts: pamac, pamac-all, pamac-aur, pamac-nosnap
Provides: pamac
Submitter: Santi-Burgos
Maintainer: Santi-Burgos
Last Packager: Santi-Burgos
Votes: 6
Popularity: 0.96
First Submitted: 2024-04-23 03:58 (UTC)
Last Updated: 2024-11-03 20:22 (UTC)

Dependencies (19)

Required by (4)

Sources (1)

Pinned Comments

Santi-Burgos commented on 2024-04-27 17:16 (UTC) (edited on 2024-04-27 17:16 (UTC) by Santi-Burgos)

If you come from pamac-nosnap, you need to perform the following:

  • Uninstall libpamac-nosnap and pamac-nosnap first
  • Install libpamac-flatpak in order to get the libraries and dependencies needed
  • Install pamac-flatpak (this one will need libpamac-flatpak as previous dependency)

If you have an AUR helper, that one may help you by just installing either libpamac-flatpak and pamac-flatpak (libpamac-flatpak as conflict/replace of libpamac-nosnap and pamac-flatpak as conflict/replace of pamac-nosnap), in case it gives error in the installation due to conflicts, perform the uninstallation first.

In either case, please clean you pacman/AUR helper cache and/or perform an installation in a clean environment

Latest Comments

1 2 Next › Last »

Jimmon89 commented on 2024-11-04 21:27 (UTC)

@Santi-Burgos: you're okay, i'm glad things are sorted out now, and i hope things are a bit better now IRL, It happens to us all

Santi-Burgos commented on 2024-11-04 16:55 (UTC)

@adrianinsaval @Jimmon89: Yeah, I didn't receive any information and, due to IRL issues, I have been unable to update the package until recently, for now this one should have the update on not conflicting on pamac-cli plus the migration to Github (which is a new for me), I appreciate the messages but always check if the other packages (or Github page) has any version, flag it as out-of-date and I will perform it on my earliest convenience

Jimmon89 commented on 2024-10-30 17:39 (UTC) (edited on 2024-10-30 17:52 (UTC) by Jimmon89)

@adrianinsaval that is a very good question, as far as i know, the CLI component is completely missing from all of the other pamac-* packages after the Manjaro team split pamac-cli into it's own separate package so i have to imagine that the maintainer of this AUR package never got the memo, unless you and i are missing something

--edit--

after downloading the package build and removing the line that makes pamac-cli a conflict and then running makepkg to install pamac-flatpak, then doing the same for pamac-cli, not only is there no conflict, but now i have the ability to use pamac from the terminal

adrianinsaval commented on 2024-09-27 00:12 (UTC)

excuse my ignorance but why does this conflict with pamac-cli?

cuvtixo commented on 2024-09-26 20:43 (UTC)

@Santi-Burgos this solution has been going 'round the internet, but I've also got this advice: Do not symlink different SO libraries for something that handles your system files, a package manager is the last thing you want to break on undefined behavior, the SO bump happened for a reason. "sudo ln -s /usr/lib/libalpm.so.15.0.0 /usr/lib/libalpm.so.14" as I understand it, downgrades all SO libraries, and this may not be a good thing, particularly when libalpm updates (I don't know if it will become apparent in 15.0.1 or not until 16.0.0, but whatever the case, things that should not be changed, are being changed by that command

KarlofDuty commented on 2024-09-18 16:33 (UTC)

I can confirm uninstalling both libpamac-flatpak and pamac-flatpak and then installing them again as @letty said fixes the libalpm.so.14 linking issue.

You should probably select clean build when yay asks though (or in whichever aur helper you use).

Just a normal reinstall without first uninstalling did not work for me.

Santi-Burgos commented on 2024-09-17 13:29 (UTC)

@letty @god: I might need to check updates on my VM, but for now and since this also affects yay, paru and other AUR helpers as well as the same pamac, please try to run the following command:

sudo ln -s /usr/lib/libalpm.so.15.0.0 /usr/lib/libalpm.so.14

I had to do that in a production machine, and after that, I was able to run both pamac and yay (probably other AUR helpers as well)

letty commented on 2024-09-17 05:57 (UTC) (edited on 2024-09-17 05:58 (UTC) by letty)

Not working because of "pamac-manager: error while loading shared libraries: libalpm.so.14: cannot open shared object file: No such file or directory"

Remove libpamac-flatpak and pamac-flatpak via yay -R libpamac-flatpak pamac-flatpak and then reinstall via yay -S pamac-flatpak.

This fixed it for me even without update.

god commented on 2024-09-16 00:23 (UTC)

Needs update. Not working because of "pamac-manager: error while loading shared libraries: libalpm.so.14: cannot open shared object file: No such file or directory"

Santi-Burgos commented on 2024-04-27 17:16 (UTC) (edited on 2024-04-27 17:16 (UTC) by Santi-Burgos)

If you come from pamac-nosnap, you need to perform the following:

  • Uninstall libpamac-nosnap and pamac-nosnap first
  • Install libpamac-flatpak in order to get the libraries and dependencies needed
  • Install pamac-flatpak (this one will need libpamac-flatpak as previous dependency)

If you have an AUR helper, that one may help you by just installing either libpamac-flatpak and pamac-flatpak (libpamac-flatpak as conflict/replace of libpamac-nosnap and pamac-flatpak as conflict/replace of pamac-nosnap), in case it gives error in the installation due to conflicts, perform the uninstallation first.

In either case, please clean you pacman/AUR helper cache and/or perform an installation in a clean environment

1 2 Next › Last »