

32·
23 hours agoThis is also a great way to just break everything you’ve set up.
This is also a great way to just break everything you’ve set up.
OK, so that’s a possibility, but when you start adding a ~$30 fee on top of the cost of the part and shipping from Fairphone you’re looking at about $100 per repair, which stops making sense pretty quickly. You’re better off spending a little more money on a good device that is dust- and moisture-sealed and taking care of it for a few years.
I really wanted to buy the Fairphone 5, but they don’t ship replacement parts to where I live which makes the entire concept pointless.
The issue is more that trying to upgrade everything at the same time is a recipe for disaster and a troubleshooting nightmare. Once you have a few interdependent services/VMs/containers/environments/hosts running, what you want to do is upgrade them separately, one at a time, then restart that service and anything that connects to it and make sure everything still works, then move on to updating the next thing.
If you do this shotgun approach for the sake of expediency, what happens is something halfway through the stack of upgrades breaks connectivity with something else, and then you have to go digging through the logs trying to figure out which piece needs a rollback.
Even more fun if two things in the same environment have conflicting dependencies, and one of them upgrades and installs its new dependency version and breaks whatever manual fix you did to get them to play nice together before, and good luck remembering what you did to fix it in that one environment six months ago.
It’s not FUD, it’s experience.