Package Details: pamac-aur 10.2.0-1

Git Clone URL: https://aur.archlinux.org/pamac-aur.git (read-only, click to copy)
Package Base: pamac-aur
Description: A Gtk3 frontend, Package Manager based on libalpm with AUR and Appstream support
Upstream URL: https://gitlab.manjaro.org/applications
Keywords: gui installer libalpm package pacman yay
Licenses: GPL3
Conflicts: pamac, pamac-tray-appindicator
Provides: pamac=10.2.0-1
Submitter: Zeph
Maintainer: Zeph
Last Packager: Zeph
Votes: 346
Popularity: 4.92
First Submitted: 2013-12-05 12:57
Last Updated: 2021-09-12 19:15

Dependencies (27)

Required by (5)

Sources (1)

Latest Comments

« First ‹ Previous ... 5 6 7 8 9 10 11 12 13 14 15 ... Next › Last »

friday commented on 2019-12-21 04:20

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

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

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

@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

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

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".

j1simon commented on 2019-10-18 18:02

It lacks the option --buildtype=release in meson line to disable debug options.

exabits commented on 2019-09-23 01:32

Run-time dependency gtk+-3.0 found: NO (tried cmake) src/meson.build:16:0: ERROR: Could not generate cargs for gtk+-3.0: A full log can be found at /home/exabits/.cache/yay/pamac-aur/src/pamac-1656246d332bc694fb61da6d64e30137a10f10f6/builddir/meson-logs/meson-log.txt ==> ERROR: A failure occurred in build(). Aborting...

I finally tracked down this bug. It was due to the package mesa-aco-git. After installing standard mesa, gtk+-3.0 is found again and Pamac builds without problem.

xAlucardx commented on 2019-09-12 19:48

Looks like the latest issue was fixed. Zeph, can you update this?

Link to latest archive: https://gitlab.manjaro.org/applications/pamac/-/archive/master/pamac-master.tar.gz

FredBezies commented on 2019-09-10 06:04

September 10th, 2019: there is a building bug with pamac 0.46.0. See https://gitlab.manjaro.org/applications/pamac/issues/649

There is a fix: https://gitlab.manjaro.org/applications/pamac/commit/fddd7715e23a7199db9498cfee2efecad62074ef