Pacman 7.0.0.r3.g7736133-1 update

Important notifications
1

With this yay needs to get rebuilded, the current version of EndeavourOS is not working with this at the very moment!

Wait till we uploaded new version or go rebuild it yourself:

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

thats the “classic way” to build a package from AUR :wink:

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

///
edit:

endeavouros/yay 12.3.5-1 ---> 12.3.5-2 0,00 MiB 3,05 MiB

It`s fixed now! update should bring in a working yay version for you.

27 Likes
2

yay can be fixed easily following your instructions. But paru doesnt. Rebuild of the paru package fails with:

error: failed to run custom build command for alpm v3.0.4 (https://github.com/archlinux/alpm.rs?rev=306342#306342ef)

Seems that alpm (rust bindings for libalpm) need an update first.

1 Like
3

Cargo.toml of paru hardcodes alpm.rs at 3.0.4 at least twice if I get it correctly.

4

If I wait a couple of days to update, do you think the issues reported will be corrected by then? Or doesn’t matter?

5

seems manuel is busy fixing it at the moment…

12 Likes
6

Happily, trizen does not appear to suffer from any of this. :sunglasses:

I hope that everyone noticed the changes to pacman.conf that the pacman update brought. Look at pacman.conf.pacnew and notice the two additional lines:

DownloadUser = alpm
#DisableSandbox

Added to the configuration file. Just a heads up.

5 Likes
7

thanks!
And if you merge – do not remove endevouros packages repo entry there :wink:

keep this like it is:

HoldPkg = pacman glibc dracut kernel-install-for-dracut eos-dracut

ILoveCandy

[endeavouros]
SigLevel = PackageRequired
Include = /etc/pacman.d/endeavouros-mirrorlist
8 Likes
8

noob here, do i need to merge these two lines or not?

9

I run meld with sudo:

sudo meld

And do a file compare. I load the pacman.conf file in one window and the pacman.conf.pacnew in the other window. Meld will highlight the differences. I carefully review the differences and then apply whatever changes I feel are apropriate to the pacman.conf file and hit the save button. At that point I can close Meld and delete the pacnew version.

2 Likes
10

To follow up on what @eznix said, you can do it like this:

sudo DIFFPROG=meld pacdiff

This will do it one command.

1 Like
12

I symlinked the latest labalpm (>= 15 on my machine) to libalpm.so.14. That fixed the issue for me.

13

please no “dirty hacks” :wink: it may work but it is by far not recommendable to do so.

3 Likes
14

Symlinking library files is a very “spit and duct tape” method of addressing the problem. I have used this method in the past, but it is far from a safe thing thing to do as we have no idea what the actual code changes are and how tricking a program into using the unintended version of a library will affect the system. In the case of aur updates, those can be done by other means. As I mentioned earlier in this thread, the program trizen appears to unaffected by this problem and functions just as well as yay or paru. Heck, simple manual installation of aur packages is far safer and quite easy.

3 Likes
15

Indeed. Quick and dirty workarounds can be a problem at best and disastrous at worst.

If one has been using yay from day one, will temporarily changing to trizen cause any issues?

16

I believe it is safe to use multiple aur helpers. I have relied on trizen solely for so long since it has never broken on me, so I don’t mix and match.

17

we have a pacdiff helper tool in welcome too:
see this old video:

Always keep an eye to not remove stuff you added or EndeavourOS added… In case you are unsure, ask here or at telegram there will always be smart user to help.

7 Likes
18

The only real issue is that alternating would make reading/comparing diffs difficult. However, if you don’t normally read diffs, then it doesn’t matter. :person_shrugging:

1 Like
19

Interesting. I’ve always avoided pacnew files since I accidentally overwrote my sudoers file and had to live boot to restore it.

20

you need to be careful indeed.

21

Yeah… I see. In my case, lots of arrows. Several pointing both ways. I exited. I don’t feel like unintentionally screwing things up.