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: Morganamilo
Votes: 30
Popularity: 0.013717
First Submitted: 2009-09-07 17:32 (UTC)
Last Updated: 2025-10-29 23:29 (UTC)

Required by (461)

Sources (5)

Latest Comments

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

eschwartz commented on 2018-04-22 03:31 (UTC)

Regarding contrib, the Arch package version did not "supply it as part of its package", the contrib stuff was simply included in the pacman codebase and therefore enabled. Current development versions have split it out again, which is why it is a separate package, but it hasn't been decided whether to make it mandatory...

Stock configurations won't work, they assume pacman can be run by any consumer and don't contain the necessary options... like configured repository names.

But these ARM changes look sort of fishy to me, why is signature checking completely disabled with references to something that was changed in arch, 6 years ago, why is libalpm patched to add some questionable feature and remove another one, why is makepkg.conf only modified in order to remove -mtune=generic?

EndlessEden commented on 2018-04-21 00:51 (UTC)

@Eschwartz: "Potentially incorrect what?" - Upstream changes that dont find their way back into the static configurations. (Which i experienced last year, when a option was not documented. Although, i cannot recall what it was, offhand). //// "There's a reason the repo package also provides its own non-stock configurations." - Im confused, why is that? //// "I'm unmotivated to support the arm pacman.conf" - i already have a local version of this package with all the patches, etc. converted. if you were interested (https://github.com/EndlessEden/pacman-all-git) //// "pacman-contrib is already ... why it should be a hard dependency" - The Arch Package Version, has supplied this as part of its package since commit "b41b136a3"@2013-04-04 / Inclusion of it just makes more sense to me. But this i think is personal. I apologize if my opinion seems inaccurate.

eschwartz commented on 2018-04-20 21:06 (UTC)

Potentially incorrect what? There's a reason the repo package also provides its own non-stock configurations.

I'm unmotivated to support the arm pacman.conf, but feel free to submit PRs here: https://github.com/eli-schwartz/pkgbuilds -- I won't hunt down the necessary conf files myself, for a system I don't use.

pacman-contrib is already an optdepends, I don't see why it should be a hard dependency especially given it would be a circular dependency.

EndlessEden commented on 2018-04-20 19:52 (UTC) (edited on 2018-04-20 19:55 (UTC) by EndlessEden)

I have a few questions... 1. This package already generates pacman.conf and makepkg.conf, why include it? (its only included in the Generic packages from arch-team, to be more CPU generic and include additional mirror info for x86_64) - Wouldnt it be much cleaner to just sed or patch the data in, rather than replace with potentially incorrect files.

  1. Since this is a git package, why not add additional support for non-x86 platforms(IE: Arm). Its not hard to merge their patches here.

  2. Since Pacman-contrib was merged into Pacman, wouldn't it be smarter to make Pacman-contrib-git a dependency or include it into your package?

timofonic commented on 2017-07-23 05:01 (UTC)

pactree is missing. Is it in pacman-contrib-git?

polyzen commented on 2016-10-11 12:39 (UTC) (edited on 2016-10-12 21:11 (UTC) by polyzen)

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

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

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

pkgver is invalid.

abandonedaccount commented on 2014-10-11 16:23 (UTC)

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

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