I can confirm that the change to last -w
fixed the issue.
Hi, I’ve just switched from testing
to stable
, looks like everything is good.
I don’t know how to use the pacnew-checker
, I tried to run it in console, nothing happens.
It’s only functional when upgrading which I’ve missed? (already run pamac update
, nothing to do)
If there are no pacnew files it should not do anything when you try and run it.If there are when updating it should pop up and let you know.You can then decide what to do as it is a pretty simple program.
if the output of pacdiff -o
is empty, the program will not open as there is nothing to manage.
Hei @Ste74, have you noticed the issue/bug I raised a few months ago?
Indeed my .mo
file was not placed in the proper folder in my PR. Recompiling all the languages from the current .po
files should fix it though. Or make a PR with both FR and FI .mo
files in the proper places. I sent a PR with the previous file. But better to just let Ste74 recompile all the .mo
files from the current language .po
files.
@Ste74 can you please recompile the language files for French and Finish so it fixes the Finish language and update the French one?
Hello,
I’m here from the Manjaro forums announcement, stable updates section. Within there philm has linked to here, and another page.
I’ve read as much as I can, and perhaps I’ve missed it, but I still have not found any documentation that tells me as a user what to do with .pacnew and .pacsave files if I run this tool, or pacdiff.
Cool that you have made a GUI over the pacdiff CLI tool, but there either needs to be information telling the user how to respond to each issue that comes up with this, or with pacdiff. Otherwise the tool should be doing it for you.
You are the system administrator - it is your job to know.
Educate your self on the expected content of the files at hand
Impossible - files may be changed by user or system - there is no reliable method to deduce what action should be taken.
When you have a .pacnew
file, it means one of the configuration files in the system has been modified, and the last update brought new modification of the original config file, so it creates a .pacnew
file instead of overwriting the existing config file during update (because if the file is modified, it means the user made some changes to it so probably best to not overwrite it, right?).
It is up to you to know what to do with the config file and the .pacnew
file, open them side by side and see the difference, and act after thinking about it.
Some files are NOT TO BE TOUCHED, like the /etc/passwd
or the /etc/shadow
files. There might be a .pacnew
file one day but if you overwrite these files with their .pacnew
, you basically break your system (but as a good user, you surely always have a Manjaro USB live system on hands, and surely make system snapshots with TimeShift in order to have the option to roll back the system when you crash the system by mistake, right?). So think about what you are doing when dealing with .pacnew
files, what is this file for, a music player? probably you can just overwrite with the .pacnew
. Is it for a critical system component? then double check you will not break the system, maybe ask on the forum.
//EDIT: @Ste74 Can you have a look please #11 - Mistake were made - Ste74/manjaro-pacnew-checker - Codeberg.org
Thank you omano, this is exactly the information I was looking for but could not find. Much appreciated!