sudo apt upgrade, offers some questions?

I created a droplet(which I understand is a digitalocean virtual machine), that went fine. I went to the console, and I did sudo apt update,(which went fine), and then I did sudo apt upgrade. But when doing sudo apt upgrade, I ran into things that aren’t normal.

For the droplet I went with the default, which is Ubuntu 23.04 x64

I did sudo apt update that’s fine

Then I did sudo apt upgrade and this screen appeared which isn’t normal

I’ve done sudo apt upgrade and not have this happen

image alt text
image caption

Should I not do sudo apt upgrade, like is it not generally recommended?

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Site Moderator
Site Moderator badge
October 25, 2023
Accepted Answer


It’s alright to do an apt update & apt upgrade, infact it’s needed.

The prompt you’re seeing is a common one for the OpenSSH server (sshd) configuration file (/etc/ssh/sshd_config), especially if you’ve made any customizations to it.

You’ll typically be presented with a few options:

  1. Install the package maintainer’s version: This will overwrite your customizations with the new version from the package. This is not usually recommended if you have intentionally made changes that you wish to keep.

  2. Keep the local version currently installed: This will retain your customized version and ignore the version in the package. This is the option to pick if you’ve made changes and know they’re still compatible with the new package version.

  3. Show the differences between the versions: This option will give you a side-by-side diff of the two versions, showing what has changed.

  4. Merge the two versions (manually): Some systems will offer an option to manually merge the changes, allowing you to decide line-by-line what to keep.

  5. Start a new shell to examine the situation: This lets you drop into a shell to investigate further before making a decision.

Given the sensitivity of the SSH configuration (it governs how you can remotely access the machine), it’s usually a good idea to carefully consider these options. If you’ve made changes to sshd_config and are confident about them, you might opt to keep the local version. However, if you’re unsure or if you believe the package update might contain important changes or fixes, you might want to see the differences first and then decide.

With that said, I’ve tested it and keeping the local changes is fine.

Try DigitalOcean for free

Click below to sign up and get $200 of credit to try our products over 60 days!

Sign up

Featured on Community

Get our biweekly newsletter

Sign up for Infrastructure as a Newsletter.

Hollie's Hub for Good

Working on improving health and education, reducing inequality, and spurring economic growth? We'd like to help.

Become a contributor

Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.

Welcome to the developer cloud

DigitalOcean makes it simple to launch in the cloud and scale up as you grow — whether you're running one virtual machine or ten thousand.

Learn more
DigitalOcean Cloud Control Panel