| 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: | |
| Conflicts: | |
| Provides: | |
| Submitter: | None |
| Maintainer: | eschwartz |
| Last Packager: | eschwartz |
| Votes: | 26 |
| Popularity: | 1.43 |
| First Submitted: | 2009-09-07 17:32 |
| Last Updated: | 2020-12-21 12:27 |
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.
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.
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!
@eschwartz: I'm using this package because of the new parallel downloads feature (which works very well!). However, I wonder, since pacman 5.2.2 has been available since 2020-07-14, if a new pacman-git version shouldn't be available as well. Or are the changes in 5.2.2 already included in this pacman-git version?
What is the purpose of providing libalpm.so? The purpose of providing pacman seems to be fairly evident, since anything that uses pacman depend on pacman. On the other hand, nothing in the official repos depends on libalpm.so (and I don't believe anything other than yay-git depends on it) -- what's the objective here?
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.
@eschwartz The official pacman from core provides libalpm.so (see https://git.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/pacman ) so it would be better to change it to that combined with provides=("pacman=${pkgver%.*.*}").
Edit: here is the diff/patch:
diff --git a/PKGBUILD b/PKGBUILD
index bca53b8..d73a3ca 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -5,7 +5,7 @@
# Contributor: Andres Perera <aepd87@gmail.com>
pkgname=pacman-git
-pkgver=5.1.1.r221.g8f89e509
+pkgver=5.2.1.r53.g87b74fcd
pkgrel=1
pkgdesc="A library-based package manager with dependency support"
arch=('i686' 'x86_64' 'arm' 'armv6h' 'armv7h' 'aarch64')
@@ -18,6 +18,7 @@ optdepends=('pacman-contrib: various helper utilities'
makedepends=('git' 'asciidoc' 'meson')
checkdepends=('python' 'fakechroot')
provides=("pacman=${pkgver%.*.*}")
+provides+=('libalpm.so')
conflicts=('pacman')
backup=("etc/pacman.conf"
"etc/makepkg.conf")
Why does pacman-git doesn't provide pacman 5.2
But it does, because
$ pacman -Qi pacman-git
[...]
Provides : pacman=5.2.0
yay-git still fails because of libalpm.so line
So, 'libalpm.so' doesn't look like 'pacman' to me.
I'm unsure why it was added to the yay-git package, and I'll tell you right now that using sonames won't work the way AUR package maintainers expect -- the result will simply be that you cannot upgrade pacman until you uninstall yay, then pacman -Syu, then rebuild and reinstall yay. Using sonames makes it harder, not easier, to use the AUR.
(There is exactly one AUR helper where it helps, and that is aurutils which can rebuild yay-git without first uninstalling it in order to upgrade pacman.)
@rafaelff Thanks, pacman --version shows Pacman v5.2.0-6-gf37a - libalpm v12.0.0 and yay-git still fails because of libalpm.so line, maybe I should report it there. Editing yay-git PKGBUILD locally fixed it for me.
@hugegameartgd: That version is exactly what is in the PKGBUILD, but this is a VCS package so its version gets updated when building the package. Even if the pkgver doesn't show 5.2.0, it is updated with the pacman master branch. So it does provide latest state of this repository.
Regarding the error about libalpm, removing 'pacman' to install 'pacman-git' breaks the AUR helper dependency. Please build pacman-git without an AUR helper, as they depends on pacman. Follow https://wiki.archlinux.org/index.php/Arch_User_Repository#Installing_packages
yay shows version 5.1.1
[user@archlinux ~]$ yay -S --devel --timeupdate pacman-git
:: Checking for conflicts...
:: Checking for inner conflicts...
==> Package conflicts found:
-> Installing pacman-git will remove: pacman
==> Conflicting packages will have to be confirmed manually
[Aur: 1] pacman-git-5.1.1.r221.g8f89e509-1
and later when trying to replace pacman with pacman-git
:: pacman-git and pacman are in conflict. remove pacman? [y / n] y
Error: Could not prepare the operation (Can not fulfill dependencies)
:: Removing pacman violates dependency 'libalpm.so> = 12', needed by yay-git
[user @ archlinux ~] $
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 https://wiki.archlinux.org/index.php/Unofficial_user_repositories#eschwartz
The packages are signed using my [community] packaging key and are therefore trustworthy. :)