Automatic Updates
Dec. 25th, 2009 11:55 am![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
grimsnifferJust a very quick rant, might expand on it later if I have time:
Yes, it's true - you are always asked to confirm a system update.
Yes, it's true - you can browse all the packages that are being updated, changed and can easily find out what changes are going to be done exactly.
Yes, it's true - most of these updates have release notes alerting for specific issues that the updates might cause.
But for fuck's sake - when I update I usually have 30+ updates (especially in this past month or two since Kubuntu 9.10 came out), and I'm sorry, but I just cba to start going over each and every one of them to see how my custom changes might be affected.
And seeing as I come from the "if stuff asks to be updated, it's probably important and should be updated right away" mentality, I rather often find myself with essential little services simply not working.
So when KpackageKit updates paths in my custom Bind9 files (God knows why), I find myself spending almost an hour finding out exactly what happened and why I can't access my Apache server the day after. An hour I really wanted to spend actually fixing bugs. Bleh.
Might just have to stop automatically confirming updates and just leave them for a specific time during the week in which I actually go over everything they're doing, because this is the third time in the past month this has happened (you'd think I'd learn to narrow it down quicker by now, eh? Or at least learn that whenever this happens, I should drink a cup of coffee, smoke a cigarette, calm down and THEN start finding out why I can't test the code I've just written... angry/frustrated system-work is sloppy system work).
Yes, it's true - you are always asked to confirm a system update.
Yes, it's true - you can browse all the packages that are being updated, changed and can easily find out what changes are going to be done exactly.
Yes, it's true - most of these updates have release notes alerting for specific issues that the updates might cause.
But for fuck's sake - when I update I usually have 30+ updates (especially in this past month or two since Kubuntu 9.10 came out), and I'm sorry, but I just cba to start going over each and every one of them to see how my custom changes might be affected.
And seeing as I come from the "if stuff asks to be updated, it's probably important and should be updated right away" mentality, I rather often find myself with essential little services simply not working.
So when KpackageKit updates paths in my custom Bind9 files (God knows why), I find myself spending almost an hour finding out exactly what happened and why I can't access my Apache server the day after. An hour I really wanted to spend actually fixing bugs. Bleh.
Might just have to stop automatically confirming updates and just leave them for a specific time during the week in which I actually go over everything they're doing, because this is the third time in the past month this has happened (you'd think I'd learn to narrow it down quicker by now, eh? Or at least learn that whenever this happens, I should drink a cup of coffee, smoke a cigarette, calm down and THEN start finding out why I can't test the code I've just written... angry/frustrated system-work is sloppy system work).
