Package Details: pamac-aur 11.7.2-2

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: 400
Popularity: 1.60
First Submitted: 2013-12-05 12:57 (UTC)
Last Updated: 2024-10-29 07:24 (UTC)

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 .. 16 17 18 19 20 21 22 23 24 25 26 .. 40 Next › Last »

friday commented on 2020-01-16 22:36 (UTC)

@agentcobra We clearly have seen it. Following those instructions didn't fix this build. They changed it so that libx11 now depends on xorgproto again though, so it's not likely anyone will get that build error any more.

agentcobra commented on 2020-01-16 22:23 (UTC)

@webreflection see https://www.archlinux.org/news/xorg-cleanup-requires-manual-intervention/

webreflection commented on 2020-01-07 11:23 (UTC)

fwiw, I agree with what friday said, as this doesn't build anymore as is due xorgproto missing

friday commented on 2019-12-21 04:20 (UTC)

I think xorgproto should be listed as a make dependency until the point it's no longer needed to build pamac. Pretty sure it's not needed to run pamac.

zfkerr commented on 2019-12-20 23:19 (UTC)

I guess it should be deleted as dependency, because Xorg havn,t need it anymore as dependency.

webreflection commented on 2019-12-20 18:39 (UTC)

on a clean GNOME install, this package doesn't build anymore because it's missing xorgproto so ... I guess it should be added as dependency

FredBezies commented on 2019-10-23 14:43 (UTC)

@j1simon: with pacman 5.2 you need both commits:

https://gitlab.manjaro.org/applications/pamac/commit/d19dec498ce5bc037c44eb3e2b2df59d46941213

and

https://gitlab.manjaro.org/applications/pamac/commit/ec8218929d4b999ba12f02f040aeb3c0181b11a0

j1simon commented on 2019-10-23 14:00 (UTC)

It doesn't compile the ...-2 version:

...
Found ninja-1.9.0 at /usr/bin/ninja
[12/64] Compiling C object 'src/25a6634@@pamac@sha/meson-generated_alpm_utils.c.o'.
FAILED: src/25a6634@@pamac@sha/meson-generated_alpm_utils.c.o
cc -Isrc/25a6634@@pamac@sha -Isrc -I../src -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/lib/libffi-3.2.1/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/json-glib-1.0 -I/usr/include/libappstream-glib -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/uuid -I/usr/include/libsoup-2.4 -I/usr/include/libxml2 -fdiagnostics-color=always -pipe -w -O3 -march=native -mtune=native -O3 -fno-plt -D_FORTIFY_SOURCE=2 -fPIC -pthread '-DGETTEXT_PACKAGE="pamac"' -D_FILE_OFFSET_BITS=64 -MD -MQ 'src/25a6634@@pamac@sha/meson-generated_alpm_utils.c.o' -MF 'src/25a6634@@pamac@sha/meson-generated_alpm_utils.c.o.d' -o 'src/25a6634@@pamac@sha/meson-generated_alpm_utils.c.o' -c 'src/25a6634@@pamac@sha/alpm_utils.c'
src/25a6634@@pamac@sha/alpm_utils.c: In function 'pamac_alpm_utils_trans_commit_real':
src/25a6634@@pamac@sha/alpm_utils.c:6316:9: error: 'ALPM_ERR_DLT_INVALID' undeclared (first use in this function); did you mean 'ALPM_ERR_DB_INVALID'?
 6316 |    case ALPM_ERR_DLT_INVALID:
      |         ^~~~~~~~~~~~~~~~~~~~
      |         ALPM_ERR_DB_INVALID
src/25a6634@@pamac@sha/alpm_utils.c:6316:9: note: each undeclared identifier is reported only once for each function it appears in
src/25a6634@@pamac@sha/alpm_utils.c: In function 'cb_event':
src/25a6634@@pamac@sha/alpm_utils.c:8050:8: error: 'ALPM_EVENT_DELTA_PATCH_START' undeclared (first use in this function); did you mean 'ALPM_EVENT_DISKSPACE_START'?
 8050 |   case ALPM_EVENT_DELTA_PATCH_START:
      |        ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
      |        ALPM_EVENT_DISKSPACE_START
src/25a6634@@pamac@sha/alpm_utils.c:8053:4: error: unknown type name 'alpm_delta_t'; did you mean 'alpm_event_t'?
 8053 |    alpm_delta_t* _tmp76_;
      |    ^~~~~~~~~~~~
      |    alpm_event_t
src/25a6634@@pamac@sha/alpm_utils.c:8057:4: error: unknown type name 'alpm_delta_t'; did you mean 'alpm_event_t'?
 8057 |    alpm_delta_t* _tmp80_;
      |    ^~~~~~~~~~~~
      |    alpm_event_t
src/25a6634@@pamac@sha/alpm_utils.c:8061:18: error: 'alpm_event_t' {aka 'union _alpm_event_t'} has no member named 'delta_patch'
 8061 |    _tmp76_ = data->delta_patch.delta;
      |                  ^~
src/25a6634@@pamac@sha/alpm_utils.c:8062:21: error: request for member 'to' in something not a structure or union
 8062 |    _tmp77_ = _tmp76_->to;
      |                     ^~
src/25a6634@@pamac@sha/alpm_utils.c:8066:18: error: 'alpm_event_t' {aka 'union _alpm_event_t'} has no member named 'delta_patch'
 8066 |    _tmp80_ = data->delta_patch.delta;
      |                  ^~
src/25a6634@@pamac@sha/alpm_utils.c:8067:21: error: request for member 'delta' in something not a structure or union
 8067 |    _tmp81_ = _tmp80_->delta;
      |                     ^~
[21/64] Compiling C object 'src/25a6634@@pamac@sha/meson-generated_database.c.o'.
ninja: build stopped: subcommand failed.
==> ERROR: A failure occurred in build().
    Aborting...

webreflection commented on 2019-10-23 10:46 (UTC)

incremental updates worked well, but I couldn't update a PC left without updates for a little while ... I ended up using pamac-aur-git instead, which built just fine.

I'll try to go back to regular pamac-aur soon, but "not today".