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

Git Clone URL: (read-only, click to copy)
Package Base: pacman-git
Description: A library-based package manager with dependency support
Upstream URL:
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

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

Latest Comments

« First ‹ Previous 1 2 3 4 5 6

Anonymous comment on 2011-10-18 00:05

Please change the "provides" option in the PKGBUILD for the pacman-git package to pacman=4.0.

misc commented on 2011-03-27 20:44

Since curl replaced wget as makepkg's default, shouldn't it be added as dependency (and switched from the extra into the core repo, as is wget)?

falconindy commented on 2011-02-14 21:29

This isn't the place for such reports. Bring this to the bug tracker.

haagch commented on 2011-02-14 21:23

I have a problem.
On 64 bit everything still works fine but on my 32 bit netbook I got a problem with installing or upgrading packages.

"pacman -Suu --debug" ("pacman -S" too) gives

I am pretty sure that I am not "out of memory"...

Here the culprit got introduced:

I don't know the code of pacman but there seems to be another reason that _alpm_pkghash_create(est_count * 2) returns NULL. Before that commit (03.02.2011) it worked fine, after the commit (08.02.2011) it doesn't, though I have not checked yet if _alpm_pkghash_create returned NULL before.

falconindy commented on 2011-01-15 14:36

Expected behavior. Please subscribe to pacman-dev if you are to be using this package.

Anonymous comment on 2011-01-15 11:39

Some of the repos have only <repo-name>.db.tar.gz and no <repo-name>.db . pacman-git does not recognize those repos (see ). Is this a bug or a design change in the pacman git version?

falconindy commented on 2011-01-03 14:40

Please make sure you run pacman-db-upgrade to update your local DB to the new pacman 3.5 format, otherwise your local DB will not be recognized properly.

falconindy commented on 2010-12-21 11:14

Well, there's a bigger issue with the db-upgrade script -- you put in a check to see if pacman is running. If this is intended to be run as part of an install scriptlet, there's going to be a lot of broken databases. Pulling it out for now.

Allan commented on 2010-12-21 04:27

I'm not sure the vercmp line in your install script works... comparing the version to 3.5.0 will not work for the git package.

You might also want to add "--enable-git-version" to the configure line.