Update package manager

stormschip · 15 March 2024 20:03

yay: error while loading shared libraries: libalpm.so.13: cannot open shared object file: No such file or directory.

anybody else ?

houssem.kochat9 · 15 March 2024 20:10

same error with paru

TilliDie · 15 March 2024 20:10

Same error using garuda-update

error: failed to prepare transaction (could not satisfy dependencies)
:: installing pacman (6.1.0-3) breaks dependency ‘libalpm.so=13-64’ required by libpamac-aur
:: installing pacman (6.1.0-3) breaks dependency ‘pacman<6.1’ required by libpamac-aur

filo · 15 March 2024 20:10

https://aur.archlinux.org/packages/yay#comment-961131

github.com/Morganamilo/paru

Paru does not work with libalpm 14

opened 05:30PM - 13 Mar 24 UTC

JohnyEZ

### Affected Version paru v2.0.1 ### Description Pacman v6.1.0 provides lib…alpm.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 with `RUST_BACKTRACE=1` environment variable to display a backtrace warning: build failed, waiting for other jobs to finish... ==> ERROR: A failure occurred in build(). Aborting..

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.

Nice
Paru should be ok now
https://aur.archlinux.org/cgit/aur.git/commit/?h=paru&id=2bfa586c9fbf08144257c1e5c013481d43760e1a

Bro · 15 March 2024 22:34

It has been fixed in Testing. Allan got a bit ahead of himself.

filo · 16 March 2024 06:09

Paru should be fixed, but going back to yay, it can be fixed like here, uninstalling it and building manually (if not using another working helper)

git clone https://aur.archlinux.org/yay.git
cd yay
makepkg -si

https://aur.archlinux.org/packages/yay#comment-961552

system · 30 March 2024 06:09

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.