Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #264573
| From | songbird <songbird@anthive.com> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: Unattended Upgrades Ran Anyway. |
| Date | 2023-12-11 02:20 +0100 |
| Message-ID | <HJD7H-cJda-1@gated-at.bofh.it> (permalink) |
| References | <HJunM-cDPO-7@gated-at.bofh.it> <HJvMS-cENp-9@gated-at.bofh.it> <HJzdM-cGWN-5@gated-at.bofh.it> |
| Organization | the little wild kingdom |
Dan Ritter wrote: > Stefan Monnier wrote: >> On my trusty Thinkpad X30, upgrades are sufficiently taxing that having >> them run unexpectedly can be a real problem, so I tried to prevent >> unattended upgrades a few months ago. > > > I have always preferred the apticron package, which by default > updates daily and sends an email letting me know that they are > available, rather than doing the upgrade itself. as everyone can have their own reasons for what they are doing i would not expect anyone else to do what i am but since we're on the topic. :) i do not run auto updates of any kind for Debian (for either testing or stable or any other instances i may have set up). currently i don't have any oddities out there running. instead, each morning i cold start my computer (i prefer it being off when i am not using it) and it boots into testing i drag in my new e-mails and usenet group posts and then fire up the update of the indexes for the various Debian package repositories it needs. after the update finishes then i check to see what kind of updates are there. some days i scan the list and just pull it all and apply them, other days i will hold certain packages because i don't want to deal with it that day. i run a few packages from sid/unstable but they usually are self-contained enough that i don't worry about it. songbird
Back to linux.debian.user | Previous | Next — Previous in thread | Find similar | Unroll thread
Unattended Upgrades Ran Anyway. Charles Curley <charlescurley@charlescurley.com> - 2023-12-10 17:00 +0100
Re: Unattended Upgrades Ran Anyway. Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-12-10 17:20 +0100
Re: Unattended Upgrades Ran Anyway. Charles Curley <charlescurley@charlescurley.com> - 2023-12-10 19:10 +0100
Re: Unattended Upgrades Ran Anyway. David Wright <deblis@lionunicorn.co.uk> - 2023-12-10 21:20 +0100
Re: Unattended Upgrades Ran Anyway. Charles Curley <charlescurley@charlescurley.com> - 2023-12-10 21:50 +0100
Re: Unattended Upgrades Ran Anyway. David Wright <deblis@lionunicorn.co.uk> - 2023-12-10 22:00 +0100
Re: Unattended Upgrades Ran Anyway. Charles Curley <charlescurley@charlescurley.com> - 2023-12-10 22:20 +0100
Re: Unattended Upgrades Ran Anyway. Greg Wooledge <greg@wooledge.org> - 2023-12-10 23:30 +0100
Re: Unattended Upgrades Ran Anyway. Charles Curley <charlescurley@charlescurley.com> - 2023-12-11 00:20 +0100
Re: Unattended Upgrades Ran Anyway. Max Nikulin <manikulin@gmail.com> - 2023-12-11 03:50 +0100
Re: Unattended Upgrades Ran Anyway. Max Nikulin <manikulin@gmail.com> - 2023-12-10 18:00 +0100
Re: Unattended Upgrades Ran Anyway. Charles Curley <charlescurley@charlescurley.com> - 2023-12-10 19:20 +0100
Re: Unattended Upgrades Ran Anyway. Stefan Monnier <monnier@iro.umontreal.ca> - 2023-12-10 18:30 +0100
Re: Unattended Upgrades Ran Anyway. Dan Ritter <dsr@randomstring.org> - 2023-12-10 22:10 +0100
Re: Unattended Upgrades Ran Anyway. songbird <songbird@anthive.com> - 2023-12-11 02:20 +0100
csiph-web