Package Details: pacman-git 6.1.0.r15.g01e64e8b-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-2.0-or-later
Conflicts: pacman
Provides: pacman
Submitter: None
Maintainer: eclairevoyant
Last Packager: eclairevoyant
Votes: 28
Popularity: 0.65
First Submitted: 2009-09-07 17:32 (UTC)
Last Updated: 2024-04-01 21:09 (UTC)

Required by (294)

Sources (5)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7

falconindy commented on 2011-02-14 21:29 (UTC)

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

haagch commented on 2011-02-14 21:23 (UTC)

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 http://aur.pastebin.com/1AEGeR4K I am pretty sure that I am not "out of memory"... Here the culprit got introduced: http://mailman.archlinux.org/pipermail/pacman-dev/2011-February/012402.html 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 (UTC)

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

<deleted-account> commented on 2011-01-15 11:39 (UTC)

Some of the repos have only <repo-name>.db.tar.gz and no <repo-name>.db . pacman-git does not recognize those repos (see https://bbs.archlinux.org/viewtopic.php?pid=878575#p878575 ). Is this a bug or a design change in the pacman git version?

falconindy commented on 2011-01-03 14:40 (UTC)

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 (UTC)

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 (UTC)

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.

« First ‹ Previous 1 2 3 4 5 6 7