How to deal with obsoleting packages messages when using check-update


I regularly update the software running on my droplet and have noticed the do-agent.x86_64 packages coming up more numerously under the Obsoleting Packages heading.

I have not been able to find any Q & A’s that cover this maintenance task.

Could someone please explain what I need to do to properly deal with the obsolete packages?


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.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

Hi @mikehermary,

You can use the package-cleanup command from the yum-utils package to list “leaf nodes” in your package dependency graph. These are packages that can be removed without affecting anything else:

$ package-cleanup --leaves

This will produce a list of “libraries” on which nothing else depends. In most cases you can safely remove these packages. If you add --all to the command line:

$ package-cleanup --leaves --all

You’ll get packages that aren’t considered libraries, also, but this list is going to be so long that it probably won’t be useful.

Having said that, you don’t actually need to remove Obsoleting Packages, they aren’t interfering with anything in terms of everything working as it is.

Additionally, if you decide to remove them, prior to removing them make sure to create a backup of your droplet, just in case.

Regards, KFSys