Update problem, Keyrings problem, startup failed to execute eos_yad and more

General system Newbie
1

Heya,

I think I have messed up and i would need your help if you are so kind to provide it! :slight_smile:

tl:dr I can’t use updates anymore. endeavouros-keyring gone by my mistake

  1. When i booted today i got this error

    image
    image712×164 27.8 KB

  2. I tried to search for it and didn’t find anything relevant so I started my morning routine by updating the system with eos-update --yay and it successfully updated alsa and pipewire.

  3. I got some problems with updating some packages though (anaconda,yacreader and dwarfs-bin), it wrote
    “error: failed to commit transaction (conflicting files)”.
    I checked the advice of https://wiki.archlinux.org/title/pacman

    image
    image984×519 135 KB

    and thought that was a conflict of same files so I WRONGLY used pacdiff & meld and overwrote 4-5 entries with ‘o’.

  4. Thats when my troubles began because when i re-run update I had the problem of “error: target not found: endeavouros-keyring”

I tried the solution provided here Keyring Issues , deleted (idiotic move from me) the gnupg folder in pacman.d, but then I could not use wget in the addresses provided because they were no longer existent :frowning:

Then i tried many things from here (including the populating keys and refreshing them

sudo pacman-key --init
sudo pacman-key --populate archlinux endeavouros
sudo pacman-key --refresh-keys
sudo pacman -Syy

but no luck!

Any suggestions or could you point me to the right urls to retry wget?

Thank you and sorry for the trouble!
Steve

2

I would work through the steps in this guide.

https://discovery.endeavouros.com/signature-and-keyring/pacman-keyring-issues/2021/03/

3

Thank you for replying!

Unfortunately it can’t find the endeavouros keyring at all

image
image815×260 18.6 KB

also yad is newer than extra and it seems that now I dont have the other databases besides core/extra :frowning:
image

  • I confirm that my system clock is correct.

  • I confirm that my folder /var/cache/pacman/pkg/ is empty

  • I confirm that i dont have incomplete downloads

  • I backed up the -newly created- gnupg folder

  • initialized the keys and repopulated them (both for endeavouros and arch)

    image
    image1065×742 92 KB

  • again it doesnt find the endeavouros keyring

    image
    image1269×111 7.27 KB

    image
    image1266×133 7.12 KB

  • and it doesnt find the keyring packages

    image
    image915×76 4.43 KB

4

run

eos-rankmirrors

and try update again

5

Unfortunately no dice

image
image878×300 10.4 KB

6

the endeavouros repo does not sync
please post the output from:

cat /etc/pacman.conf
7

Sure thing!

image
image773×886 24.8 KB

image
image772×889 26.2 KB

(Sorry i am not familiar yet on how to post outputs in a better format than pntscn)

8

these lines are missing

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

Edit:
insert them as in the following standard file

1 Like
9

text blocks:

```
like this
```

or

[code]
like this
[/code]
2 Likes
10

use the code tags(</>) from the forum editor and insert the terminal output in it.

1 Like
11

That was it!!!
Now I can at least update!
Thank you very much for your patience and thoughtful insight!

Btw do you guys have any idea for this error that still keeps popping up?

image
image698×153 9.77 KB

Also I still have the error of not being able to update anaconda and dwarfs-bin but I am now trying a cleanbuild. Fingers crossed

1 Like
12

the error points to your home directory cache folder chances are it has been removed.as far as anaconda and dwarfs-bin i don’t use those so i couldn’t tell you what the issue is

1 Like
13

Yeap! I thought the same, but I cannot understand what element of eos_yad is this and how it is related to my startup processes. :thinking:

14

Screenshot_20230716_113547

This looks like an error message you’d get on Windows! :thinking:

1 Like
15

I dont know what to do with that information :sweat_smile:

16

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