I could not find anything on the forum when I searched for this. I tried making my self familiar with this but every time I try I break the system and updates no longer work so a total re install is required or (I can restore a snapshot) but this merging thing keeps popping up after so many updates if a reinstall is done or it is just back if a snapshot is used. This is on both my computers. I thought about just ignoring it but the Rani still shows the warning and it bothers me a bit. So I was wondering if there was is a simple way to fix this.
I just move the new server list to the right side and save it. When it asks to delete the pacnew file I first say N that I still have the file.
Then I check by upd -a and get the WARNING aabut when it’s done run the command again then this WARNING doesn’t come up anymore.
if its working i delete the pacnew file manually .
do I need to add the inxi ? I just didn’t see that being needed for this question? Thanks for the information duke. I find this interesting that this pops up even on a new install but after the updates are done. So it surprises me more people have not asked about it or mentioned it. Also it seems like some thing the devs should look into fixing so it does not come up on new installs after updates are done. Maybe I am wrong.
Its not only for new installs also if someone didnt update for a long time and have trouble with any server error list or updates failed to fix it. I also think many people watching youtube videos or delete the file if the updates working. Many ways to Rom
Thanks and my apologies, I did search the forums and nothing came up. I do recall that the contents of that screen shot. This does confuse me a lot, I feel like I should be able to get this working so I just delete the file and not merge ? I feel so dumb, why does this make me want to go off and cry. I was trying to figure it out on my own. thanks
No Problem it says ask in the Forum for it so youre not wrong dont worries. yeah Move any useful changes you want is a bit unclear thats why i do only test with the server list and go step by step if i needed. Normally the update looking itself for refreshing the Server lists itself if the System is updated each week but can trouble on a not updated system what i had because of testing different Distros. No your are fine Linux is learning by doing so feel free to ask anytime
It is not about hardware errors in garuda-inxi.
If now, as happened at the beginning of the forum, everyone decides for themselves whether garuda-inxi is necessary or not, we only inflate the forum unnecessarily, with discussions about it, as well as unnecessary inquiries about it.
The question about pacdiff is not specific to Garuda, but is already well documented on the web and forum
Thanks, I get it now. I did include it later. Doing a duckduckgo/ startpage / searx was part of what lead to my confusion. None of the results were garuda related so not helpful and I included the link the rani provided as proof I was using garuda as the link was provided by the error but didn’t find the info at the link helpful and was more confusing. From this point on I will include the needed info. Not trying to hurt the forum, I love this software and love the community as every one is really kind even in this. I just want to be honest to also be helpful. I do thank every one for being helpful.
Just 2 files mirrorlist and mirrorlist.pacnew. I backed up both to an external hard drive and deleted the mirrorlist and renamed the mirrorlist.pacnew to just mirrorlist. It was a bigger file so thought it was best to go with that one. It seems to be updating so I think that worked.
The mirrorlist package gets updated when there are changes to the mirrorlist. For example, new mirrors have been added, defunct mirrors have been removed, a URL has changed, etc. You don’t necessarily need to have the most recent changes in your file, but you are less likely to run into issues if your mirrorlist is current.
That being said, you don’t actually need the mirrorlist file as it is provided from the repo if you are using a tool like rate-mirrors to sort the mirrorlist. The mirrorlist generated by rate-mirrors will always be better because it is sorted according to mirror availability and latency, where the mirrorlist from the repo (the pacnew file) is not going to be sorted in a meaningful way.
When you run garuda-update, it automatically runs rate-mirrors for you. It fetches mirrors from the mirror status page (Arch Linux - Mirror Status) and builds the list from scratch according to what mirrors perform best for you. In this case the pacnew from the repo is entirely unneeded.
All that to say: if you are refreshing your mirrorlist with garuda-update or rate-mirrors, you can just delete the mirrorlist pacnew files whenever they come down because you don’t need them.
