Package Details: pacman-git 5.0.1.84.gad27aa3-1

Git Clone URL: https://aur.archlinux.org/pacman-git.git (read-only)
Package Base: pacman-git
Description: A library-based package manager with dependency support. git version.
Upstream URL: http://www.archlinux.org/pacman/
Licenses: GPL
Conflicts: pacman, pacman-contrib
Provides: libalpm.so, pacman=5.0.1.84.gad27aa3, pacman-contrib
Submitter: None
Maintainer: falconindy
Last Packager: falconindy
Votes: 19
Popularity: 0.004236
First Submitted: 2009-09-07 17:32
Last Updated: 2016-10-13 19:39

Dependencies (10)

Required by (135)

Sources (1)

Latest Comments

polyzen commented on 2016-10-11 12:39

contrib/ was removed from pacman. Please update the pkgbuild so a pacman-contrib package can be added.

Edit: https://aur.archlinux.org/packages/pacman-contrib-git Once there's a release, pacman-contrib will be available in the repos.

AWhetter commented on 2016-05-01 20:10

Please could we start patching /etc/pacman.conf to replace 'pacman' in the HoldPkg list with 'pacman-git'.

eworm commented on 2016-01-29 09:27

makepkg bails out with an error:

==> ERROR: pkgver is not allowed to contain colons, hyphens or whitespace.
==> ERROR: Could not download sources.

Can we remove the colon, please?

Scimmia commented on 2016-01-05 18:46

pkgver is invalid.

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.

All comments