Package Details: pacman-git 6.0.0alpha1.r86.gc294b7cb-1

Git Clone URL: https://aur.archlinux.org/pacman-git.git (read-only, click to copy)
Package Base: pacman-git
Description: A library-based package manager with dependency support
Upstream URL: https://www.archlinux.org/pacman/
Licenses: GPL
Conflicts: pacman
Provides: pacman=6.0.0alpha1
Submitter: None
Maintainer: eschwartz
Last Packager: eschwartz
Votes: 27
Popularity: 1.18
First Submitted: 2009-09-07 17:32
Last Updated: 2021-04-08 00:19

Required by (189)

Sources (5)

Pinned Comments

eschwartz commented on 2019-05-31 04:58

For convenience I provide an unofficial repository containing prebuilt versions of this and a number of other AUR packages. See https://wiki.archlinux.org/index.php/Unofficial_user_repositories#eschwartz

The packages are signed using my [community] packaging key and are therefore trustworthy. :)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 Next › Last »

eschwartz commented on 2019-10-29 17:52

It does, check again.

hugegameartgd commented on 2019-10-29 17:40

Why does pacman-git doesn't provide pacman 5.2? It's already in the main repo.

brikler commented on 2019-10-25 07:56

i am not able to build because wrong reverence… a idea how to solve it?

pacman -Q gpgme
gpgme 1.13.1-1
../lib/libalpm/signing.c:177: error: undefined reference to 'gpgme_check_version_internal'
../lib/libalpm/signing.c:179: error: undefined reference to 'gpgme_set_locale'
../lib/libalpm/signing.c:181: error: undefined reference to 'gpgme_set_locale'
../lib/libalpm/signing.c:192: error: undefined reference to 'gpgme_engine_check_version'
../lib/libalpm/signing.c:196: error: undefined reference to 'gpgme_set_engine_info'
../lib/libalpm/signing.c:198: error: undefined reference to 'gpgme_get_engine_info'
../lib/libalpm/signing.c:207: error: undefined reference to 'gpgme_strerror'
../lib/libalpm/signing.c:235: error: undefined reference to 'gpgme_new'
../lib/libalpm/signing.c:254: error: undefined reference to 'gpgme_release'
../lib/libalpm/signing.c:240: error: undefined reference to 'gpgme_get_key'
../lib/libalpm/signing.c:249: error: undefined reference to 'gpgme_strerror'
../lib/libalpm/signing.c:251: error: undefined reference to 'gpgme_key_unref'
../lib/libalpm/signing.c:552: error: undefined reference to 'gpgme_key_unref'
../lib/libalpm/signing.c:276: error: undefined reference to 'gpgme_new'
../lib/libalpm/signing.c:293: error: undefined reference to 'gpgme_strerror'
../lib/libalpm/signing.c:295: error: undefined reference to 'gpgme_release'
../lib/libalpm/signing.c:326: error: undefined reference to 'gpgme_new'
../lib/libalpm/signing.c:418: error: undefined reference to 'gpgme_strerror'
../lib/libalpm/signing.c:421: error: undefined reference to 'gpgme_release'
../lib/libalpm/signing.c:329: error: undefined reference to 'gpgme_get_keylist_mode'
../lib/libalpm/signing.c:333: error: undefined reference to 'gpgme_set_keylist_mode'
../lib/libalpm/signing.c:338: error: undefined reference to 'gpgme_get_key'
../lib/libalpm/signing.c:421: error: undefined reference to 'gpgme_release'
../lib/libalpm/signing.c:446: error: undefined reference to 'gpgme_new'
../lib/libalpm/signing.c:453: error: undefined reference to 'gpgme_op_import_keys'
../lib/libalpm/signing.c:455: error: undefined reference to 'gpgme_op_import_result'
../lib/libalpm/signing.c:279: error: undefined reference to 'gpgme_get_keylist_mode'
../lib/libalpm/signing.c:281: error: undefined reference to 'gpgme_set_keylist_mode'
../lib/libalpm/signing.c:285: error: undefined reference to 'gpgme_get_key'
../lib/libalpm/signing.c:289: error: undefined reference to 'gpgme_key_unref'
../lib/libalpm/signing.c:289: error: undefined reference to 'gpgme_key_unref'
../lib/libalpm/signing.c:348: error: undefined reference to 'gpgme_get_key'
../lib/libalpm/signing.c:770: error: undefined reference to 'gpgme_data_release'
../lib/libalpm/signing.c:771: error: undefined reference to 'gpgme_data_release'
../lib/libalpm/signing.c:629: error: undefined reference to 'gpgme_data_new_from_stream'
../lib/libalpm/signing.c:642: error: undefined reference to 'gpgme_data_new_from_mem'
../lib/libalpm/signing.c:651: error: undefined reference to 'gpgme_op_verify'
../lib/libalpm/signing.c:653: error: undefined reference to 'gpgme_op_verify_result'
../lib/libalpm/signing.c:646: error: undefined reference to 'gpgme_data_new_from_stream'
collect2: Fehler: ld gab 1 als Ende-Status zurück

eschwartz commented on 2019-05-31 04:58

For convenience I provide an unofficial repository containing prebuilt versions of this and a number of other AUR packages. See https://wiki.archlinux.org/index.php/Unofficial_user_repositories#eschwartz

The packages are signed using my [community] packaging key and are therefore trustworthy. :)

eschwartz commented on 2018-05-13 02:26

Sure, and I got another wonderful surprise over the weekend because allan accepted my fix for the gcc8 warnings. :D

yan12125 commented on 2018-05-12 16:51

Hi, could you drop support-file-5.33-pie-executable.patch? It's landed as https://git.archlinux.org/pacman.git/commit/?id=03272ad57142a1c7dacf1d9933d52650d3936225

eschwartz commented on 2018-05-09 17:12

--enable-debug enables -Werror in addition to #define PACMAN_DEBUG

This causes issues because gcc8 has new warnings. I've been waiting to see if Allan can write a patch over the weekend that fixes these, in which case the issue will naturally disappear.

polygamma commented on 2018-05-09 16:58

It is currently not possible to build the package. makepkg output:

cc1: all warnings being treated as errors
make[3]: *** [Makefile:825: libalpm_la-remove.lo] Error 1
make[2]: *** [Makefile:928: all-recursive] Error 1
make[1]: *** [Makefile:984: all-recursive] Error 1
make: *** [Makefile:893: all] Error 2

EndlessEden commented on 2018-04-23 01:53

@Eschwartz - Fair enough. Thank you for all your work. - I wasnt aware that they were using package signing right now. Ill switch my repos to signed. thank you for that info as well.

(P.S. - Gosh those edits are so clean. Amazing work.)

eschwartz commented on 2018-04-22 18:42

I've asked on their IRC channel, and they were sort of vague about why they wanted the sync patch but admitted it "may not be needed as much anymore with most installations shipping with initramfs".

The stdin patch reverts https://git.archlinux.org/pacman.git/commit/?id=e374e6829cea3512f0b4a4069c5a6168f0f8d8a0 which we added to pacman for good reason, and they indicated that while some packages prompt the user in the install script to e.g. flash the u-boot images, their install scripts know how to handle lack of stdin. I see no reason to revert this, since the user can very well follow the fallback prompts and this "feature" is broken in many cases.

For the signature checking I was told "it's up to the user to initialize their keys". I have even less than zero interest in supporting this use case.

I'm uploading a new version which adds the necessary CARCH support and uses pacman.conf.arm configured with their repositories. This seems sufficient to me.