GreyXor
commented
7 months ago https://github.com/Morganamilo/paru/tree/alpm-v3 will soon be working again For now you can try https://aur.archlinux.org/packages/paru-alpm-v3-git
Closed JohnyEZ closed 7 months ago
GreyXor
commented
7 months ago https://github.com/Morganamilo/paru/tree/alpm-v3 will soon be working again For now you can try https://aur.archlinux.org/packages/paru-alpm-v3-git
JohnyEZ
commented
7 months ago https://github.com/Morganamilo/paru/tree/alpm-v3 For now you can build https://aur.archlinux.org/packages/paru-alpm-v3-git
That works thank you
Crylia
commented
7 months ago https://github.com/Morganamilo/paru/tree/alpm-v3 For now you can build https://aur.archlinux.org/packages/paru-alpm-v3-git
It also fails for me, but for another reason
$ makepkg -si
==> Erstelle Paket: paru-alpm-v3-git 2.0.1.r25.g2a8e257-2 (Fr 15 Mär 2024 01:43:30 CET)
==> Prüfe Laufzeit-Abhängigkeiten...
==> Prüfe Buildtime-Abhängigkeiten...
==> Empfange Quellen...
-> Aktualisiere das paru git Repo...
==> Überprüfe source Dateien mit sha256sums...
paru ... Übersprungen
==> Entpacke Quellen...
-> Erstelle Arbeitskopie des paru git Repos...
Setze Branch 'makepkg' neu
==> Beginne prepare()...
Updating crates.io index
==> Beginne pkgver()...
==> Entferne existierendes $pkgdir/ Verzeichnis...
==> Beginne build()...
Updating crates.io index
error: failed to get `dirs-sys` as a dependency of package `dirs v5.0.1`
... which satisfies dependency `dirs = "^5.0.1"` (locked to 5.0.1) of package `paru v2.0.1 (/home/crylia/Dokumente/git/paru-alpm-v3-git/src/paru)`
Caused by:
failed to query replaced source registry `crates-io`
Caused by:
attempting to make an HTTP request, but --frozen was specified
==> FEHLER: Ein Fehler geschah in build().
Breche ab...
Morganamilo
commented
7 months ago Try paru-git. Not the package the other person made.
Crylia
commented
7 months ago Try paru-git. Not the package the other person made.
I did, but I got the same error as OP. Hence why I tried the other above package
Gin-no-kami
commented
7 months ago This issue (with paru-git) occurs when building in a paru chroot.
Morganamilo
commented
7 months ago You need to have pacman 6.1.0 in your chroot for paru to build against.
Elixity1
commented
7 months ago https://github.com/Morganamilo/paru/tree/alpm-v3 For now you can build https://aur.archlinux.org/packages/paru-alpm-v3-git
That works thank you
Worked for me too, thanks
aaronliu0130
commented
7 months ago pacman 6.1 is now in core. A new release should probably be made.
Morganamilo
commented
7 months ago Release was made days ago. Pkgbuillds need to be updated. You can do this yourself in the meantime if you wish.
aaronliu0130
commented
7 months ago Ah, I thought it wasn't released as it wasn't in the changelog.
bioxz
commented
7 months ago This issue leaves paru in an unusable state, you either have to downgrade pacman again or install the new version of paru by hand. Would it be possible to avoid such situation in the future by depending on a maximum version of pacman, so you, in this example, cannot go to pacman 6.1 without upgrading paru as well?
aaronliu0130
commented
7 months ago Pacman's version does not report the libalpm version.
mmonsen
commented
7 months ago I apologize if I'm missing something, I'm still new to Arch Linux, pacman, and paru.
The front page (README.md) says to use these steps to install paru:
sudo pacman -S --needed base-devel
git clone https://aur.archlinux.org/paru.git
cd paru
makepkg -siThe master branch in the repository at https://aur.archlinux.org/paru.git doesn't have any commits after v2.0.1 on December 1 2023. This version won't compile against the current version of pacman (from what I've gathered from previous comments on this issue.)
Should I be using the repository here on Github instead of the repository in AUR?
Morganamilo
commented
7 months ago This issue leaves paru in an unusable state, you either have to downgrade pacman again or install the new version of paru by hand. Would it be possible to avoid such situation in the future by depending on a maximum version of pacman, so you, in this example, cannot go to pacman 6.1 without upgrading paru as well?
With standard linking you can't do this. Binary repos solve this by building everything against the new alpm version and pushing all the updates as one atomic action. As the aur is source based it's on the user to do this.
Lulonaut
commented
7 months ago I apologize if I'm missing something, I'm still new to Arch Linux, pacman, and paru.
The front page (README.md) says to use these steps to install paru:
sudo pacman -S --needed base-devel git clone https://aur.archlinux.org/paru.git cd paru makepkg -siThe master branch in the repository at https://aur.archlinux.org/paru.git doesn't have any commits after v2.0.1 on December 1 2023. This version won't compile against the current version of pacman (from what I've gathered from previous comments on this issue.)
Should I be using the repository here on Github instead of the repository in AUR?
You can use paru-git instead, so
git clone https://aur.archlinux.org/paru-git.git
This works fine for me (I just compiled it)
Morganamilo
commented
7 months ago I apologize if I'm missing something, I'm still new to Arch Linux, pacman, and paru. The front page (README.md) says to use these steps to install paru:
sudo pacman -S --needed base-devel git clone https://aur.archlinux.org/paru.git cd paru makepkg -siThe master branch in the repository at https://aur.archlinux.org/paru.git doesn't have any commits after v2.0.1 on December 1 2023. This version won't compile against the current version of pacman (from what I've gathered from previous comments on this issue.) Should I be using the repository here on Github instead of the repository in AUR?
You can use paru-git instead, so
git clone https://aur.archlinux.org/paru-git.gitThis works fine for me (I just compiled it)
The current release of paru works with the new pacman. The aur package still points to the previous release because current release won't work with old pacman.
The options are use paru-git. Bump the paru pkgbuild yourself, or wait for me to finish walking home.
LRitzdorf
commented
7 months ago @mmonsen In case it helps, here's an attempt to clarify how the AUR system (typically) works:
So, when you install from the AUR, you'll get v2.0.1, even though v2.0.3 is released on GitHub. To "fix" this situation, we just need the AUR maintainer (Morganamilo in this case, though the AUR maintaner need not be the main dev) to make the pkgbuild point to the new source tarball.
hth!
DarkXero-dev
commented
7 months ago @mmonsen In case it helps, here's an attempt to clarify how the AUR system (typically) works:
- An AUR pkgbuild specifies a URL to the relevant source tarball(s) (in this and many other cases, these are downloaded from GitHub)
- That source tarball is available for multiple different versions of paru
- In this case, the pkgbuild still points to the 2.0.1 version of the source tarball
So, when you install from the AUR, you'll get v2.0.1, even though v2.0.3 is released on GitHub. To "fix" this situation, we just need the AUR maintainer (Morganamilo in this case, though the AUR maintaner need not be the main dev) to make the pkgbuild point to the new source tarball.
hth!
I did that locally still does not work doesn't have the alpm-v3 stuff.. I will replace -bin with -git on my repo make latter replace the former.. with replaces=(paru-bin)
Paru-bin (2.0.3) from AUR error
aru: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory@DarkXero-dev I haven't messed around with the -bin or -git versions, personally — my notes above were for the source-based paru package.
At this point, the easiest option is probably just to give Morganamilo a few moments to update the pkgbuilds, do a git pull in your clone of the AUR repo (to get that new pkgbuild), and makepkg -si to install. I wouldn't expect them to take very long :)
Morganamilo
commented
7 months ago The aur packages are updated as of now.
DarkXero-dev
commented
7 months ago @Morganamilo
The aur packages are updated as of now.
Error in 2.0.3 on AUR built now
aru: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory@DarkXero-dev :
install openssl-1.1 to fix that.
What distro and architecture are you on? Binaries may have targeted the wrong ssl version.
DarkXero-dev
commented
7 months ago @Morganamilo
I am on Vanilla Arch with Plasma 6. Why not add it as dependency in PKGBUILD ?
Morganamilo
commented
7 months ago I have for now. Will build a new binary that links against the correct openssl.
DarkXero-dev
commented
7 months ago @Morganamilo
Thanks bud .. Will have to tell my users to replace Yay with Paru for now as it still hasn't been updated lol..
Morganamilo
commented
7 months ago I'm pretty sure yay is also updated for what it's worth. You can use either.
aaronliu0130
commented
7 months ago Yay will install correctly as long as you rebuild it after upgrading pacman.
DarkXero-dev
commented
7 months ago @Morganamilo @aaronliu0130 I compile -bin usually from AUR and host on my repos I sorta avoid -git..
aaronliu0130
commented
7 months ago Well, it's either build it or install it from the EndeavourOS repos, bud
DarkXero-dev
commented
7 months ago @aaronliu0130 I am and I do not care for custom repos besides my own and AUR..
I am now getting weird error when I try to rebuild my repo DB
error: read package paru-bin-2.0.3-2-x86_64.pkg.tar.zst: unknown field 'xdata' in .PKGINFO.Does the server you build the db on have an old version of pacman?
DarkXero-dev
commented
7 months ago @aaronliu0130 Nope it's the same PC that just got new pacman
Morganamilo
commented
7 months ago I don't see that error string anywhere in pacman. So I don't know what tool you're running to get that.
DarkXero-dev
commented
7 months ago @aaronliu0130 I use repoctl to update db I have my own repo .. Been using it for years never had that issue before
Morganamilo
commented
7 months ago repoctl isn't an arch tool. Pacman added a new field and it seems repoctl errors on it instead of just throwing a warning. Throw an issue their way.
aaronliu0130
commented
7 months ago Please stop pinging me.
b02860de585071a2
commented
7 months ago The aur packages are updated as of now.
Working perfectly after a makepkg --install with the new package, thank you for the quick fix!
liluzibird
commented
7 months ago What worked for me was just installing paru from the aur again
git clone https://aur.archlinux.org/paru.git
cd paru
makepkg -si
raman08
commented
7 months ago What worked for me was just installing paru from the aur again
git clone https://aur.archlinux.org/paru.git cd paru makepkg -si
Got ==> ERROR: Cannot find the debugedit binary required for including source files in debug packages. doing same
raman08
commented
7 months ago When use sudo ln -s /usr/lib/libalpm.so.14.0.0 /usr/lib/libalpm.so.13 it works.
Morganamilo
commented
7 months ago No that will break things. Don't do that.
devrajneupane
commented
7 months ago What worked for me was just installing paru from the aur again
git clone https://aur.archlinux.org/paru.git cd paru makepkg -siGot
==> ERROR: Cannot find the debugedit binary required for including source files in debug packages.doing same
Consider installing the base-devel package, which includes debugedit. Alternatively, standalone debugedit package can be installed.
Morganamilo
commented
7 months ago Anyway paru is updated to match the new pacman. If paru (or anything else depending on pacman via libalpm) is broken you need to rebuild the package.
Davidster
commented
7 months ago paru is still unable to build without upgrading to an unreleased version of pacman. could someone provide instructions for how to upgrade to pacman 6.1 so that we can compile paru?
Morganamilo
commented
7 months ago Wait for your distro to update to the new pacman.
Affected Version
paru v2.0.1
Description
Pacman v6.1.0 provides libalpm.so.14, conflicting with paru's requirement
Output
paru: error while loading shared libraries: libalpm.so.13: cannot open shared object file: No such file or directory
makepkg -si ==> Making package: paru 2.0.1-1 (Wed 13 Mar 2024 01:28:44 PM EDT) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Found paru-2.0.1.tar.gz ==> Validating source files with sha256sums... paru-2.0.1.tar.gz ... Passed ==> Extracting sources... -> Extracting paru-2.0.1.tar.gz with bsdtar ==> Starting prepare()... ==> Removing existing $pkgdir/ directory... ==> Starting build()... Compiling serde_derive v1.0.193 Compiling tokio-macros v2.2.0 Compiling futures-macro v0.3.29 Compiling openssl-macros v0.1.1 Compiling thiserror-impl v1.0.49 Compiling phf_macros v0.11.2 Compiling regex v1.10.2 Compiling crossbeam-epoch v0.9.15 Compiling crossbeam-queue v0.3.8 Compiling alpm v2.2.2 (https://github.com/archlinux/alpm.rs?rev=8da396#8da39602) Compiling ahash v0.8.3 Compiling selectors v0.25.0 Compiling html5ever v0.26.0 Compiling backtrace v0.3.69 Compiling cssparser-macros v0.6.1 Compiling num-traits v0.2.17 Compiling ipnet v2.8.0 error: failed to run custom build command for
alpm v2.2.2 (https://github.com/archlinux/alpm.rs?rev=8da396#8da39602)Caused by: process didn't exit successfully:
/home/johnyez/paru/src/paru-2.0.1/target/release/build/alpm-66f804f119040d76/build-script-build(exit status: 101) --- stderr thread 'main' panicked at /home/johnyez/.cargo/git/checkouts/alpm.rs-a0070a235cf20bfa/8da3960/alpm/build.rs:25:13: this version of alpm.rs does not support libalpm v14.0.0 only v13.x.x is supported note: run withRUST_BACKTRACE=1environment variable to display a backtrace warning: build failed, waiting for other jobs to finish... ==> ERROR: A failure occurred in build(). Aborting..