In Manjaro XFCE, if I open root Thunar (just right click on an empty space on your desktop to get the context menu), I can then (in the root Thunar) open the relevant config file in geany as root, and do my editing graphically.
I compare the conf and the pacnew files first in Meld [normal user, not root], and pick and choose which changes I want to merge into the conf file. which I always place in the left pane, with pacnew on the right. WHen I’m happy, I open the conf file as root using geany (as described above), and copy the whole of the changed conf text in Meld over whatever’s in the conf file.
If the changes are minimal [eg just a few words/characters to be added or deleted], I just use vim in terminal. I got used to the key commands.
I don’t know much about regular expressions or ‘awk’ commands so I can only ask simple questions about this:
If a user were to use the 3 line sed command on a configuration that had only 2 lines
would the command fail ? or delete the 2 lines + third empty line?
Would it be possible to use the 3 line awk command with a 2nd awk command to remove the 3rd line if the line is empty?
Removal of community repository could have affected any system on any branch that had not removed [community] configuration from /etc/pacman.conf.
New users on Stable branch (installed after Jul 2023) were not affected by this because [community] configuration was removed from later ISOs - But they are likely to have other issues in future if .pacnew files are not maintained
There were a few savyy users on forum that were spotting systems trying to sync to
community repo last year and suggesting users remove it
Manjaro had prior warning from Arch that they would be removing their community repo
so it was expected that some Manjaro users would have problems if Manjaro community
The way I presented the alternative was - kind of - belt and suspenders and oilskin suit to avoid a possible mishap caused by blindly copy/pasting the command.
In the default configuration sections are separated by an empty line.
But if a rare condition is found - where there is no empty line between sections - the third line could be a repo definition and in such event - executing the sed would remove the repo definition and leave a dangling Include = - which may or may not refer to a third party repository.
So whille with - perhaps 99% - the command removing three (3) lines would cause no harm - it is the remaining 1% I was worried about.
Personally I didn’t see an issue as my pacman.conf was ridded of community repo long time ago.
Since Patrick has ceased his involvement with Manjaro - there is no maintainer and nobody notice.
The mentioned repo was Patrick’s personal repo. I had to create a new repo in our applications section to be able to maintain the code.
I discovered the issue when using mbn on March 3. and had no previous knowledge about the inner workings of the tool.
The issue was fixed in manjaro-check-repos without even seeing the issue you linked - updating the configuration files /etc/manjaro-check-repos.
The runtime files cached or otherwise created by mbn cannot be replaced by a package.
You will have to manually execute a forced refresh to reflect this into the mbn cache
This repository does not exist anymore.
It was still existing as an empty repo for two years
simply to avoid this very issue that now hit many -
because they didn’t heed the hints and messages telling them to tend to their .pacnew files.
Thank you so much @linux-aarhus for this manual!!! I am really very, very much appreciate that the manjaro-team always takes care to also help out the noobs like me here!!
I am running the update now with pacman and it seems to be going smoothly so far…
I do care about maintaining my system and did actually read the threads and advice about managing pacnew and pacsafe files, but somehow I never really dared to actually do it, because I was afraid to mess it up by misjudging which files I can delete. I know I should have looked deeper into it still and it was stupid of me, to think, that I would get away with it for much longer but well…my own fault. I will probably go into the threads about system maintainance again and try to get more advice there for any doubts/questions that I still have regarding that topic!
You are correct - there is several keypresses to achieve the same thing - the chosen communication was to ensure no confusion but a one-to-one correlation with the visible shortcuts communicated by the nano editor
will use pacdiff, and ask about all new config files what to do with them. One option is open with meld. It will also prompt for root when you save changes. So essentially running that command once after every update keeps you up to date with all config files
but well…my own fault. I will probably go into the threads about system maintainance again and try to get more advice there for any doubts/questions that I still have regarding that topic!