Pacman 7.0.0.r3.g7736133-1 update

Important notifications
64

Yeah i waited a few days (i was busy with work anyway) and today(since I’m free) I updated with no issue.

Yay still work i installed an AUR package and it worked.

Great work to the EndeavourOS dev team! :+1: :enos: :purple_heart:
You make EndeavourOS the best and most stable Distro! :enos_flag:

3 Likes
65

Thanks for correcting me there.

However, it still shouldn’t break things.
Basically what the command does is it changes the group ownership without changing the user ownership.

@DenalB

you can change it back by replacing yourGroup with the group of the root user I think.
sudo chown :yourGroup -R /path/to/local/repo
so:
sudo chown :root -R /path/to/local/repo

Can somebody else confirm this?

2 Likes
66

Please consider that yay is in the endeavouros repo and this means the guys managing the endeavouros repo have to deal with this. Those people do all their work in their free time without getting paid. So, we should say thank you instead of blaming them.

Just my 2 Cents.

4 Likes
67

@manfredlotz you misunderstood me.

I was referring to some “wrong” advice I gave.

68

Thanks for the heads up, I’ll look into this.

In the mean time, installing paru-git will work too, it just asks to change the package name from paru to paru-git because of the specified conflict.
When the upstream paru gets the fix, the same conflict detection will set things back to normal.

Edit: a fixed paru is released in the EndeavourOS repo! See my post below.

1 Like
69

I’m not sure what you’re referring to here? But the yay problem is solved, and a new version is available on the EndeavourOS mirrors.

2 Likes
71

For paru users I just released a fixed version (paru 2.0.3-1.1) based on the tip referred above (thanks @PatJK !).

8 Likes
72

Does pamac- all:
Aur file, have any impact or influence on the system overall if not updated?

Rich;)

73

AUR file? or package? if installed it could cause package version conflict and leaves system partly updated.

74

Thank you for your attention. . . makes sense. . .

Rich;)

75

That was correct! Just checked the other files in /etc/pacman.d with ls -l and the group is root. So I switched back to root for both repo files.

sudo chown :root -R /etc/pacman.d/endeavouros-mirrorlist
sudo chown :root -R /etc/pacman.d/mirrorlist

Thanks again, @huebi ! :+1:

1 Like
76

I just noticed this during the update.

Creating group 'alpm' with GID 961.
Creating user 'alpm' (Arch Linux Package Management) with UID 961 and GID 961.

also with this config file mentioned above

DownloadUser = alpm

Can anybody explain to me why is this new user now used for package downloads? What is the reason for this change?

77

Here you go: https://archlinux.org/news/manual-intervention-for-pacman-700-and-local-repositories-required/

And earlier reference in this thread: Pacman 7.0.0.r3.g7736133-1 update - #45 by huebi

2 Likes
78

Thanks. I think I understand “how” it is more a question about “why”.
Does that mean that some unprivileged user alpm downloads a package but root still intall it? And when the download does something bad it will just influence the alpm user? I do not know if I understand this change correctly.

79

It basically means more security when updating, but here’s a more detailed explanation:

It’s not something that will affect most users.

Hope this answers your “why” somehow.

1 Like
80

For those using paru, it’s updated and working again now.

81

This must be for paru and paru-bin, as paru-git has been working correctly since 09/15.

82

it is indeed paru and paru-bin, sorry should have mentioned it.

83

No apologies necessary. Was just pointing it out. :wink:

1 Like
84

good to know. works like a charm.