I have a slight issue here. I proceeded to perform fresh install on Garuda, and I’ve noticed that I hung up on the same issues (mirrorlists and something to do with a keyring). I don’t know it specifically as I’m new to this and I’m aware that this Arch stuff may be updated on a weekly basis. Correct me if I’m wrong.
But I got hung up on this installation, I then went to the Konsole and run an update and it shows that the system is ok and that there is nothing else to do. So I’m assuming that I’m good?
As I’ve stated before in another post, I’m a lifelong Windows user, but I’m wanting to learn this without breaking anything or having hangups during a file download or anything else that can happen. But if someone can inform me what the mirrorlist was changed to during the Broadwing update, and how I can get a keyring, i would greatly appreciate it.
Notices during install:
(Failed systemd services found: garuda-system-maintenance@keyring.service)
Error: failed retrieving file ‘linux-zen-6.17.2.zen1-1-x86_64.pkg.tar.zst’ from mirror.osbeck.com : Operation too slow
This system has pending .pacnew files, you should check and merge those.
^Referencing the error, I checked the kernel version with command ‘uname -r’ and the output is ‘6.17.2-zen1-1-zen’, so I’m assuming that it must be good now? I also need help with the .pacnew file thing.
Thank you for any and all help and please, respond in laymen’s terms for me. This is alot to take in. Lol
Please post your garuda-inxi as requested by the template. Open a terminal and enter this:
garuda-inxi
Then copy the entire output and paste it here using a code block. From the topic template you deleted before posting:
After rebooting, post the FULL output of garuda-inxi in the body of the post (not linked externally, or collapsed with the “hide details” feature)
Format terminal output (including your garuda-inxi) as a code block by clicking the preformatted text button (</>) , or put three tildes (~) >above and below the text
garuda-health ◄ 3s
--- System Health Check Report ---
23/24 checks run in 0.78 seconds ⌛
Powered by garuda-health 🦅
✅ System health check passed. No issues found.
sudo garuda-health
[sudo] password for cybertheworm:
--- System Health Check Report ---
24/24 checks run in 1.59 seconds ⌛
Powered by garuda-health 🦅
✅ System health check passed. No issues found.
It is advantageous to have only one problem per thread and to use a meaningful title in the headline.
Regarding pacnew, use the forums and web search; there are no precise instructions because there are too many possibilities. The basic rule is not to blindly overwrite the original with pacnew.
I figured instead of listing my issues separately, I could put them in one thread and people respond to what they can help with.
But while I was waiting for a response, I took the liberty to read some other notes and push through with syncing and updating the system. Only merging and saving lines that add to what is previously in the .pac file.
Oh ok, I ran a diagnostic on the system and save the report in the text file to use as a kind of reference in case i have a hiccup later. This report showed 24/24, and I forgot the command, however I believe I resolved the issue. Thank you very much for your response.
Heya. If the system update completed without further incident, you can safely ignore both of these errors.
Sometimes your internet connection or the server your computer is communicating with is not perfect and errors happen. This is expected and normal. Garuda Linux can handle these.
Pacnew files are configuration files that have either had their defaults updated or were otherwise modified in the package. You can merge them with the existing files on your system.
So far, so good. I’ve updated the system to where I didn’t have anymore notifications. I noticed that the terminal seems to be the best practice for updating anything, but I’m basing this off of former knowledge from when I was running Linux Mint months ago on the .deb system.
As to the .pacnew files, I also noticed that I only really have one option and that’s to move chunks from .pacnew to .pacsave* (it may be called something else) and I’ll save it, reboot and see that there’s no other issues. I’m also learning that I can force an update in case there’s a hiccup, but I’ve had issues in the past where I’ll do this and something on the backend gets tweaked and then I have no idea where it broke at, so I’m taking my sweet time with this. I did reinstall Garuda earlier before I made this thread, and I figured I make the thread to keep from having to scour the web for answers and come right to the source.