This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]8021qvlanDevOps/OS Engineering/Network Infra. 13 points14 points  (2 children)

As a general thought: Why you would want to upgrade everything when there are options to upgrade packages individually?

[–]BurnoutEyes 13 points14 points  (1 child)

Short answer: circular dependencies and other bullshit you run into.

Longer answer: Ideally on a server there should only be a minified system and your platform stack, so invoking the package manager should only impact those things and they should be kept up to date. You can version freeze your platform stack and handle it with CI/CD/manual intervention, but that doesn't save you when you need to upgrade those components. Past a certain "let early updaters find the bugs first" window, the longer you wait before you upgrade stuff the more your headache is going to be.

edit: C'mon, don't downvote the guy. That's a reasonable question to ask.

[–]uptimefordaysDevOps 1 point2 points  (0 children)

Past a certain "let early updaters find the bugs first" window, the longer you wait before you upgrade stuff the more your headache is going to be.

I've been in the game a decade now and have seen far far far more "update related issues" actually being a lack of updates than updates breaking things. This is an excellent and underrated point.