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 Next › Last »

EndlessEden commented on 2018-04-22 18:22

@Eschwartz - "Split contrib" Ahh, sorry for the confusion. - I was unaware of that, as its not something i have any interest in normally.

"Stock Configurations" - ^_^ makes sense, ty for clarifying.

"signature checking completely disabled" - While I do agree on that, it is the way their repositories are set up ( I don't know who currently maintaining packages, but I don't believe they are currently signed. Thats something I would ask Kevin Mihelich about. But, I would recommend you did, as I am not very familiar with arch repos and packaging security. it's typically not my concern, as in, not a packager.

patches -

0001-Sychronize-filesystem.patch From what I can tell Sync was added to prevent data loss. As a precaution on slow-writing mediums(Or poor flash media) - As I was just raising compliance, in my GitHub version of this package and not focused on reasons for its use.(as its just harmless sync() before starting package operations.) In the patch-notes dating back to 2014, it states ###[Since many problems arise from improper flushing of the filesystem, particularly package installations followed by a reboot very shortly after, this will perform a sync() after installations and removals to ensure a consistent filesystem state after package operations.]###

0002-Revert-close-stdin-before-running-install-scripts.patch Specifically, on ArchlinuxArm, closing stdin can be an issue during install/remove scripts and some other functions. But again I am not a developer and this function seems harmless, although could potentially be an issue for security if done on the archlinux-x86 platforms as there is no cleanup process. As Taken from the notes.

[This reverts commit e374e6829cea3512f0b4a4069c5a6168f0f8d8a0.

Arch Linux ARM packages have use cases for this feature, such as prompting the user to flash a new kernel to a bare partition. Removing this feature will undoubtedly cause more problems than it intends to solve.]### - If you want me to ask I can ask them for clarification?

0003-Revert-alpm_run_chroot-always-connect-parent2child-p.patch - This is no longer required, as these changes have already occurred upstream. As such I've removed it.

eschwartz commented on 2018-04-22 03:31

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

@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 ( //// "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

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: -- 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

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

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

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: 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.