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 »

abandonedaccount commented on 2014-10-11 16:23

pacman-db-upgrade broke packages whose 'files' (file) contains %BACKUP%
for example %BACKUP% is right on the next line after %FILES% as if some kind of sorting happened. And this causes pacman -Qo and -Ql to not see any files and thus attempting to upgrade/downgrade those affected packages causes `exists in filesystem` for each file.
This happened after I upgraded from commit d9cf14ff1d69ac8834b84015c7971f55ce77645b
to commit(latest currently): 7ee01c86669327b2af63c8ed9390bcbf071cdac5

Ok someone(demize) just notified me of this:
https://lists.archlinux.org/pipermail/pacman-dev/2014-October/019422.html

but may be worth to know if someone else if about to update from this

abandonedaccount commented on 2014-09-07 19:47

that pacman-git bug is tracked here: https://bugs.archlinux.org/task/41862

abandonedaccount commented on 2014-09-07 18:06

Looks like noextract option inside PKGBUILD prevents that file from being softlinked into ${srcdir} and thus the need to use ${SRCDEST} to access it.
As an example of this try chromium-dev package.
Tested with: Pacman v4.1.2-406-g3e19-dirty - libalpm v8.0.2
Without noextract it is symlinked, with noextract it isn't.

rafaelff commented on 2013-04-01 07:26

Pacman 4.1.0 in [testing] since today.

graysky commented on 2013-03-31 19:42

@maggie: I believe Allan was targeting the Easter weekend for 4.1's release but likely to [testing]. I took a stab at a PKGBUILD for pacman-git that will work with the current 4.0.3 series:

https://gist.github.com/graysky2/5281746

Dave - feel free to check my math :p

graysky commented on 2013-03-31 15:05

@j - That needs to be captured in the PKGBUILD somehow, versioned dependency or at the very least, a comment.

rafaelff commented on 2013-03-31 14:24

@graysky: May I guess? 1) This is AUR and a GIT PKGBUILD is development-based; 2) Once you install pacman-git, eventual PKGBUILD updates will require the current format, otherwise will fail; -- anyway, one just have to follow the migration task using Allan's pkg tarball and it is all done.

graysky commented on 2013-03-31 14:07

@dave - why would you post a PKGBUILD that depends on development software to the AUR if what the previous poster said is true?

rafaelff commented on 2013-03-31 12:43

@maggie: Are you trying to install this package with pacman 4.0.3 ? I had this problem too and @RunningDroid's answer helped me - you need 4.1.0rc installed to support urls from VCS, like GIT.

maggie commented on 2013-03-31 11:28

I get errors when building: ==> ERROR: pkgver is not allowed to contain colons, hyphens or whitespace.

When I change the pkgver to remove the -32: ==> ERROR: There is no agent set up to handle git URLs. Check /etc/makepkg.conf.