Config File Changes During Apt-Upgrade

[mwdennis]

I am curious how I should handle config file changes during the apt-upgrade. Do I keep the local version or replace with the update? I just ran an apt upgrade on my proxmox ve 8.3.2 host and one of the updates was for the openssh-server. I've attached a screenshot showing the differences between versions. Do I keep local?

 

[BobhWasatch]

There is only one actual change there, the others are commented. And the change is trivial, you added a keepalive interval. So it doesn't really matter much. I would apply the change but maybe you had a reason for adding the keepalive in which case you should keep the old version.

 

[BobhWasatch]

This kind of thing only happens when you have made local changes to a config file. So it is on you to know the reason you made the change and whether or not it is still important. There is no one-size-fits-all answer to the question.

 

[mwdennis]

Thanks for the response. I went ahead and kept the local file as this was an OVH template install so I would assume they want that keepalive interval for some reason.

 

[BobhWasatch]

I should also probably mention that whichever choice you take nothing will be deleted. Either your old file will be renamed with a different extension, or the new one will be saved with an extension. So either way you can always go back.

 

[gfngfn256]

apt-upgrade

NEVER run apt upgrade or apt-get upgrade on a PVE system, only apt-get dist-upgrade. See here & these forums for more info.

 

[mwdennis]

NEVER run apt upgrade or apt-get upgrade on a PVE system, only apt-get dist-upgrade. See here & these forums for more info.

Oh I didn't do either. I merely ran the UI based refresh/upgrade which I would assume runs the appropriate upgrade process.

 

[gfngfn256]

Good. I was only responding to what I read in your OP: " .... file changes during the apt-upgrade" . Many users make this mistake & end up breaking some dependency etc. If you only use the UI it will only do a dist-upgrade.