Package Details: pamac-aur 11.7.3-1

Git Clone URL: https://aur.archlinux.org/pamac-aur.git (read-only, click to copy)
Package Base: pamac-aur
Description: A Gtk frontend, Package Manager based on libalpm with AUR and Appstream support
Upstream URL: https://github.com/manjaro/pamac
Keywords: gui installer libalpm package pacman yay
Licenses: GPL-3.0-or-later
Conflicts: pamac, pamac-cli, pamac-tray-appindicator
Provides: pamac, pamac-cli
Submitter: Zeph
Maintainer: Zeph
Last Packager: Zeph
Votes: 408
Popularity: 1.89
First Submitted: 2013-12-05 12:57 (UTC)
Last Updated: 2025-05-05 21:46 (UTC)

Dependencies (20)

Required by (8)

Sources (2)

Pinned Comments

Zeph commented on 2022-06-04 13:58 (UTC) (edited on 2024-10-29 07:25 (UTC) by Zeph)

For some problems with pamac, check or create issues on

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 40 Next › Last »

Musikolo commented on 2024-05-04 03:43 (UTC)

@Zeph, I tried to report upstream a segmentation fault error I get in my box. After a week awaiting, it's been impossible to get a user to log it in GitLab. So, I'm sharing here the details I have just in case it helps anyone. pacman -Syu works seamlessly in my box, but pamac upgrade crashes:

If I ever get a user in GitLab, I'll be happy to log in this issue upstream.

I hope it helps.

Thanks.

Firestar commented on 2024-04-27 08:46 (UTC) (edited on 2024-04-27 13:16 (UTC) by Firestar)

I got this error in build:

INFO: autodetecting backend as ninja                                                                          
INFO: calculating backend command to run: /usr/bin/ninja
[1/9] Generating data/doc/pamac.conf.5 manpage with a custom command
FAILED: data/doc/pamac.conf.5 
/usr/bin/a2x -f manpage -D data/doc ../data/doc/pamac.conf.5.asciidoc
a2x: ERROR: "xmllint" --nonet --noout --valid "/home/firestar/.cache/yay/pamac-aur/src/pamac-cli-3985c4d7e95312f79bb2a7f33766912c329f4697/builddir/data/doc/pamac.conf.5.xml" returned non-zero exit status 4

[2/9] Generating data/doc/pamac.8 manpage with a custom command
FAILED: data/doc/pamac.8 
/usr/bin/a2x -f manpage -D data/doc ../data/doc/pamac.8.asciidoc
a2x: ERROR: "xmllint" --nonet --noout --valid "/home/firestar/.cache/yay/pamac-aur/src/pamac-cli-3985c4d7e95312f79bb2a7f33766912c329f4697/builddir/data/doc/pamac.8.xml" returned non-zero exit status 4

[3/9] Compiling Vala source ../src/version.vala ../src/transaction-cli.vala ../src/cli.vala

full log: https://paste.c-net.org/DingleGrind

FredBezies commented on 2024-03-29 17:20 (UTC)

There is a patch added to the code to give compatibility for Gnome 46 -> https://gitlab.manjaro.org/applications/pamac/-/commit/61b7570aace3def9b048668fa23a52f08423ecf1

Hebgbs commented on 2024-03-20 16:53 (UTC) (edited on 2024-03-20 16:55 (UTC) by Hebgbs)

I've been using the May 7th build of pamac-aur and libpamac-aur because it's the only one I had found which compiles without issues which my preferred build of pamac-aur providing pamac-manager likes without having to do the hokey-pokey.

For persons desperately wanting a GTK3 release of Pamac that is compliant with GTK3 theming to use outside of GNOME Shell, it's the only thing I found which works. Mind, the advice I am providing below is a little insane, but so far I have been able to manage packages with it.

So, to build libpamac-aur from May 7th ("V11.5.4", a7ed088c…) edit its PKGBUILD file to remove from depends 'pacman<6.1' and save, then build it. After, since the files from pamac-aur from May 7th ("Gnome 44", 8ddb0d04…) expect libalpm 1.3 (libalpm.13.so), run sudo ln -s libalpm.14.so libalpm.13.so.

(Don't forget — you can enable Snap and Flatpak support here, too. Never tested what to build for best results, but maybe later I'll update this comment with some more abject stupidity.)

Then you can build 8ddb0d04 with no trouble and everything just works after that. I understand this is VERY STUPID so if someone can lead me to something better that isn't hacking my own copy of Manjaro's pamac-gtk3 to work, let the world know in-kind. Thank you.

Hebgbs commented on 2024-03-18 01:18 (UTC)

Hey, Zeph, curious — has there been consideration to either update pamac-classic so it uses the recent work of Manjaro team via their pamac-gtk3 package, or adjusting this package so gtk4 and libadwaita are required only if a boolean for GTK3 is set false?

I was sticking with the May 7th build from 2023 for a good long while until the Pacman version update stuffed my setup, and while this isn't your fault; I'm not fond of being flash-banged early in the morning when updating my packages because of libadwaita's per-application theming sucking balls to use outside of GNOME Shell.

elppans commented on 2024-03-17 21:56 (UTC)

The following dependency should be modified, so as not to be tied to just the maintainer's version, with other variants doing the same:

Dependency:

'libpamac-aur>=11.6'

How it should be:

'libpamac'

I installed the libpamac-full package and then downloaded the pamac-aur package and before installing with makepkg, I modified this dependency leaving the line like this:

depends=('libnotify' 'libhandy' 'libadwaita' 'gtk4' 'desktop-file-utils' 'libpamac' 'gnutls>=3.4' 'git')

After editing, I installed the package with makepkg:

makepkg -Cris

And the pamac application worked normally, including support for AUR, Flatpak and Snapd

G4Zz0L1 commented on 2024-02-13 08:54 (UTC)

The PKGBUILD seems to have wrong sha256sums for the cli tar.gz.

update-aurto[987780]: ==> Retrieving sources...
update-aurto[987780]:   -> Found pamac-11.7.1-2.tar.gz
update-aurto[987780]:   -> Found pamac-cli-11.6.0-4.tar.gz
update-aurto[987780]: ==> Validating source files with sha256sums...
update-aurto[987780]:     pamac-11.7.1-2.tar.gz ... Passed
update-aurto[987780]:     pamac-cli-11.6.0-4.tar.gz ... FAILED
update-aurto[987780]: ==> ERROR: One or more files did not pass the validity check!
update-aurto[987780]: ==> ERROR: Could not download sources.
update-aurto[987780]: FAILED: pamac-aur.stamp
update-aurto[987780]: [1/1]  pamac-aur  [FAIL]

terminalmage commented on 2024-02-08 02:15 (UTC)

The PKGBUILD is missing "systemd" in makedepends. Without it there, this will not build in a chroot.

vlatkoB commented on 2023-12-18 06:06 (UTC)

Depending on your AUR helper. I'm using 'yay', and the cache is in ~/.cache/yay

iestynapmwg commented on 2023-12-17 20:50 (UTC)

Where is "the cache directory" to delete "the file" from? Been searching through /var/cache/ and found nothing relevant.

« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 40 Next › Last »