Package Details: pamac-flatpak 11.7.2-2

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.030730
First Submitted: 2024-04-23 03:58 (UTC)
Last Updated: 2025-04-15 13:59 (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 »

KarlofDuty commented on 2025-04-15 20:20 (UTC)

@Santi-Burgos Sadly did not work, it still segfaults on launch.

Santi-Burgos commented on 2025-04-15 14:13 (UTC)

@Unboxorg: please clean your AUR helper cache, it seems that after copying from another PKGBUILD that I use as a reference, the tests didn't work properly (even in my test VM worked fine)

@KarlofDuty: I hope that with the update it can help you with the segfault, but if the issue is something related with the python-gobject package, which you can check here, that one is going to take a while since that package must be solved before something else (and several packages, inside and outside of AUR has been affected)

Unboxorg commented on 2025-04-15 08:47 (UTC)

After the last update the PKGBUILD file is incorrect

/home/unboxorg/.cache/yay/pamac-flatpak/PKGBUILD: line 62: cd: pamac-11.7.2: No such file or directory

(1/1) Arming ConditionNeedsUpdate... -> Failed to install the following packages. Manual intervention is required: pamac-flatpak - exit status 4

Replacing pamac-11.7.2 with just pamac in the PKGBUILD file solved the problem

KarlofDuty commented on 2025-04-13 12:57 (UTC)

Pamac started segfaulting on me after I updated my system yesterday. I have tried uninstalling and then installing it again using yay with a clean build of both pamac-flatpak and libpamac-flatpak without success.

Anyone else having these issues or know of a solution?

god commented on 2025-01-26 00:35 (UTC)

Seems like searching/installing from AUR has not been working for weeks.

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

1 2 Next › Last »