I have a droplet running Debian 11 and want to upgrade to Debian 12.
Re: https://www.cyberciti.biz/faq/update-upgrade-debian-11-to-debian-12-bookworm/
This how-to strongly recommends removing any non-Debian packages and reinstalling afterwards. The only non-Debian packages on my vanilla system are:
do-agent/main,now 3.16.7 amd64 [installed]
droplet-agent-keyring/main,now 2.0.0 amd64 [installed]
droplet-agent/main,now 1.2.7 amd64 [installed]
Question: Will these packages interfere with the upgrade and should they be removed prior to upgrading?
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!
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.
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.
Heya,
As mentioned the best approach will be to backup your data with snapshot or simply backup your information using rsync or SFTP and then proceed with the upgrade.
These specific packages are designed to support the functioning and management of your DigitalOcean Droplet, and they are usually well-maintained to be compatible with newer Debian releases.
Regards
Hey!
Those should not really cause any issues, but if you wish to be on the safe side you can feel free to remove them. This is the DigitalOcean monitoring agent and if you need to you can always reinstall it by following the steps here:
Also, make sure to first backup your Droplet before starting so that you can revert back if needed.
What I personally do in such cases is to actually, first take a snapshot of my Droplet. Then spin up a new Droplet from that snapshot and try to do the upgrade there. That way main production Droplet remains intact and I can test the whole process on a separate instance before actually proceeding with the upgrade of the production Droplet itself.
Best,
Bobby
Heya @jhg,
They shouldn’t interfere with the upgrade however what you can do is disable any repositories that are not part of the main ones.
Also, make sure to create a snapshot prior to starting the upgrade process.
https://docs.digitalocean.com/products/images/snapshots/
Snapshots are on-demand disk images of DigitalOcean Droplets and volumes saved to your account. Use them to create new Droplets and volumes with the same contents.