[SOLVED] I need help with the pacman 7 manual intervention

zoltan · 2024-09-14 21:06:38

I've been trying to install something from the AUR using Paru, but have been unable to. I tried reinstalling Paru, but now when I makepkg -si, the build fails and throws an error related to alpm:

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: `/home/zoltan/software/git/aur/paru/src/paru-2.0.3/target/release/build/alpm-fe8130be9696cf00/build-script-build` (exit status: 101)
  --- stderr
  thread 'main' panicked at /home/zoltan/.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 backtrace
warning: build failed, waiting for other jobs to finish...
==> ERROR: A failure occurred in build().
    Aborting...

I saw in the news that manual intervention with pacman is required because of changes or discrepancies related to permissions for local repositories (I assume this includes cloned git repos), but I don't really understand the instructions that are posted. I tried running:

chown :alpm -R ~/software/git/aur/paru     #The custom directory where I keep aur git clones

as non-root. It didn't work, so I ran it as root and it looked like it worked. I then followed (or tried to follow) the instructions to merge the .pacnew files. I followed the link provided for this, but the article didn't specifically have any instructions on merging. It simply mentioned using pacdiff to manage .pac* files. pacdiff prompted me to Merge, Skip, Overwite, etc. several files. The instructions said merge so... I typed M for merge. It opened a vim window and displayed two copies of the first file, obviously showing the differences between the old file and the new file. I didn't know how to make them merge though, so I quit out, ran pacdiff again, and this time just hit O for Overwite on all of the files it found. This didn't work, I can only assume because overwriting was not the correct action to take here (hence the instructions saying "merge"... *facepalm*).

At this point I decided to stop trying to cheese my way through it and just follow the damn instructions. I ran pacdiff again to go back and merge like I should have done, and I was going to go ahead and commit to inevitably reading through a long chain of wiki pages that I struggle to understand so that I can get this thing done right. Alas, pacdiff found no files to act upon. Well shit... Now what? lol

I'm having a mega-noob moment here, guys. I don't understand the instructions, I don't understand the documentation I'm reading, I don't even really understand the root issue. I don't have a lot of free time on hand for the next few days, but I'm going to continue reading when I do have time. I'm a little concerned that I may have boned myself here because I can't get pacdiff to show me diffs to merge anymore since I just overwrote everything... Can someone point me in the right direction and help me pull my head out of my butt? I need to get this fixed, and I'm feeling a little in over my head. Thanks in advance for any help.

Edit: after reading just a little further, I found that the vim window that opened is called vimdiff. On the vim wiki page, there's a table for commands that it can take. Not that it matters much at this point for this specific issue, but would dp (diff put) have been the correct command to merge the file pairs?

Last edited by zoltan (2024-09-14 21:38:33)

WorMzy · 2024-09-14 21:23:37

Mod note: moving to AUR Issues

V1del · 2024-09-14 21:24:31

aur git clones are not a local repository and this isn't the issue you're facing.

The library paru integrates with has become incompatible as a new version got pushed through the pacman update. There's no formal release yet, but paru should be fixed in the git release. So git clone paru-git and install that with makepkg.

However blindly running overwrite on god knows how many pacnews (the only pacnew relevant for the pacman updates would have been /etc/pacman.conf.pacnew and /etc/makepkg.conf.pacnew... anything else would have needed other/prior considerations) might have brought you into some serious trouble if you're unlucky... in particular if you wiped /etc/shadow and/or /etc/passwd or so. look at /etc/passwd, does it still contain your user and users of packages creating users or is it empty?

Last edited by V1del (2024-09-14 21:35:32)

zoltan · 2024-09-14 21:39:12

That worked! I feel really stupid about this... Thank you for the help. Marked as solved.

V1del · 2024-09-14 21:53:46

Make sure you take note of my edit, and if what I'm fearing has happened and you will potentially have trouble to login to your user, make a new thread so we can assess the potential damage...

zoltan · 2024-09-14 23:30:19

V1del wrote:

Make sure you take note of my edit, and if what I'm fearing has happened and you will potentially have trouble to login to your user, make a new thread so we can assess the potential damage...

Had no trouble logging in, and after checking /etc/passwd, everything there seems to be in order. However, when I tried to run pacman -Syu, I did get this error:

error: failed to synchronize all databases (no servers configured for repository)

Unfortunately, I don't remember which pacnews I overwrote. I'm going to google this and read the wiki before opening another thread. This seems like it should be an easy fix. If I can't get it fixed, I'll open a new thread.

zoltan · 2024-09-14 23:37:38

zoltan wrote:

V1del wrote:
Make sure you take note of my edit, and if what I'm fearing has happened and you will potentially have trouble to login to your user, make a new thread so we can assess the potential damage...
Had no trouble logging in, and after checking /etc/passwd, everything there seems to be in order. However, when I tried to run pacman -Syu, I did get this error:
error: failed to synchronize all databases (no servers configured for repository)
Unfortunately, I don't remember which pacnews I overwrote. I'm going to google this and read the wiki before opening another thread. This seems like it should be an easy fix. If I can't get it fixed, I'll open a new thread.

And it's fixed. I just had to go into /etc/pacman.d/mirrorlist and uncomment some mirrors. I uncommented all of the https mirrors in my region, then ran pacman -Syyu.

Arch Linux

#1 2024-09-14 21:06:38

[SOLVED] I need help with the pacman 7 manual intervention

#2 2024-09-14 21:23:37

Re: [SOLVED] I need help with the pacman 7 manual intervention

#3 2024-09-14 21:24:31

Re: [SOLVED] I need help with the pacman 7 manual intervention

#4 2024-09-14 21:39:12

Re: [SOLVED] I need help with the pacman 7 manual intervention

#5 2024-09-14 21:53:46

Re: [SOLVED] I need help with the pacman 7 manual intervention

#6 2024-09-14 23:30:19

Re: [SOLVED] I need help with the pacman 7 manual intervention

#7 2024-09-14 23:37:38

Re: [SOLVED] I need help with the pacman 7 manual intervention

Board footer