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.092205
First Submitted: 2009-09-07 17:32 (UTC)
Last Updated: 2024-04-01 21:09 (UTC)

Required by (303)

Sources (5)

Latest Comments

1 2 3 4 5 6 7 Next › Last »

nadavwr commented on 2024-05-26 15:37 (UTC)

A recent commit to remove GITFLAGS support seems to have broken use cases that rely on git --mirror. I think the author left in a dash sign that was part of the ${GITFLAGS:-...} substition, leading to error: unknown option '-mirror'

https://gitlab.archlinux.org/pacman/pacman/-/commit/d74d7ec32cbeb687dea57e0f4078176914a22578

ron2138 commented on 2024-05-12 15:32 (UTC) (edited on 2024-05-12 15:42 (UTC) by ron2138)

I can build pacman-git in my usual environment for a specific git commit branch. I fail building it in a clean environment using devtools. Any suggestions are appreciated.

Specifically, with

$ git clone https://aur.archlinux.org/pacman-git.git
$ cd pacman-git/
$ makepkg --nobuild
$ cd src/pacman/
$ git switch -c 6.1.0 e3dc296ba35
$ cd ../../
$ makepkg --noextract

I get a pacman-git-6.1.0.r0.ge3dc296b-1 package.

My question is how to use devtools to create the same package within a clean environment?

While the 6.1.0 branch, at the e3dc296ba35 commit from above, is checked out, something like

# mkarchroot chroot/root base-devel
# makechrootpkg -c -u -r chroot -- --holdver

only produces a pacman-git-6.1.0.r49.g8aba032d-1 package. 8aba032d is the head of the master git branch at the time of writing. Am I doing something wrong? Is there a devtools bug?

Scrumplex commented on 2022-09-12 20:06 (UTC) (edited on 2022-09-12 20:07 (UTC) by Scrumplex)

Needs debugedit as a dependency for makepkg's strip to work, since https://gitlab.archlinux.org/pacman/pacman/-/commit/ae2f506d

eschwartz commented on 2021-06-02 06:00 (UTC)

fixed, this was overlooked in my initial #archlinuxarm discussion but is now excluded in their pacman update.

parkerlreed commented on 2021-05-27 20:43 (UTC)

fcf-protection is not valid for ARM targets. This is added to the ARM makepkg.conf which then makes compiles fail.

eschwartz commented on 2021-05-21 19:04 (UTC)

Fixed, see commit message. :(

solnce commented on 2021-05-21 13:23 (UTC)

The most recent PKGBUILD commit from today breaks the integrity checks for all four additional files. Needed to update the hashes before building.

eschwartz commented on 2021-02-14 03:37 (UTC)

The cargo cult of libdepends strikes again...

And if it did provide libalpm.so, it wouldn't help you since this is the git version which means any ABI-breaking changes won't bump the soname until release time, thus, depending on a soname version achieves precisely nothing.

I guess I could provide a (meaningless) libalpm.so, but... I've got no idea if these packages access APIs which have been changed in pacman 6.0.0alpha1, in which case it will hardly help.

katt commented on 2021-02-14 01:09 (UTC)

The fact this package doesn't provide libalpm.so like the [core] one does has now started causing issues.

Both arch-audit and arch-rebuild-order depends on it.

eschwartz commented on 2020-09-13 16:24 (UTC)

The changes are included. This package will never show a version number for maintenance-only backport releases that were never tagged from the master branch.

And thanks for testing it!

1 2 3 4 5 6 7 Next › Last »