Pacnew warning request

Continuing the discussion from User seems to be deleted:

Just want to note that I got the same problem. The pacnew checker overwrites the passwd file as I click accidentally to get the whole new file. (Thanks to a backup, it was not a massive problem.)

So, maybe the pacnew checker could get a special warning for some files that could prevent the user from login? A warning with something red blinking or a guy that jumps out of the screen and slaps the user before he can click something. Should be a small feature…
:sweat_smile:

1 Like
1 Like

Wheel user password “reset itself”, now twice

To fix it there is usually a backup /etc/passwd~. Verify your username is at the end of the file and - if it is - use cp to replace the existing file.

sudo cp /etc/passwd~ /etc/passwd

No - passwords are never reset by an update.

Confused by the presence of a file named passwd.pacnew?

It would happen if you - without giving thought to the process - replace a configuration with a .pacnew file

Never automate .pacnew files - it may wreck your system completely.

2 Likes

Your post has been moved to a dedicated topic.

The question, or rather the responses it may invite, may prove interesting for many newer Members.

I envisage something more like a little green guy who jumps out and slaps a User upside the head for running commands they have little understanding of. :troll: :wink:

2 Likes

I was thinking more of if using a laptop having the lid auto slam shut and break all fingers.The time it takes for the fingers to heal should remind the person to never make that mistake again. :grinning:

1 Like

Rather brutal, but no doubt effective. :joy_cat:

4 Likes

Jeez, the user complains he has to edit config files, then somebody makes automation and ther complain about that too.

For the lazy and brainless, at the end of the road there is windows, where the user have to make no decisions at all. It auto updates, it auto spys, it auto crashes. No thinking involved.

2 Likes

Stable Updates already have a warning that includes a link to manjaro-pacnew-checker:

As far as I know, manjaro-pacnew-checker offers four choices for a .pacnew file:

  1. Open configuration file and .pacnew file to merge contents
  2. Delete .pacnew file
  3. Replace configuration file with .pacnew file
  4. Do nothing

I use a modified version of a script that only has option 1

Modified version includes request to delete .pacnew file after it has been merged in meld
BASH script to merge .pacnew files in meld · GitHub Gist - nik-gnomic