-
Notifications
You must be signed in to change notification settings - Fork 170
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Both yay installations and paru installations fail but say success #377
Labels
bug
Something isn't working
Comments
Could not reproduce. |
I can confirm the same issue as @bl4xe on a new arch installation and will add that by checking the version it comes at the following. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I was trying to reinstall yay as I received an unrelated error reading something like it couldn't load libalpm.so.14. So I wanted to just reinstall them with this script and I ran into an error reading error:
failed to run custom build command for
alpm v3.0.4 (https://github.com/archlinux/alpm.rs?rev=306342#306342ef)
Caused by:
process didn't exit successfully:
/opt/paru/src/paru-2.0.3/target/release/build/alpm-fe8130be9696cf00/build-script-build
(exit status: 101)--- stderr
thread 'main' panicked at /home/bl4ze/.cargo/git/checkouts/alpm.rs-a0070a235cf20bfa/306342e/alpm/build.rs:25:13:
this version of alpm.rs does not support libalpm v15.0.0 only v14.x.x is supported
note: run with
RUST_BACKTRACE=1
environment variable to display a backtracewarning: build failed, waiting for other jobs to finish...
==> ERROR: A failure occurred in build().
Aborting...
Paru installed
To Reproduce
Steps to reproduce the behavior:
Expected behavior
just install normally
Screenshots
Additional context
I'm currently converting a shit ton of files with ffmpeg, maybe that caused the error
The text was updated successfully, but these errors were encountered: