Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #182713
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: How did you update to stretch? |
| Date | 2017-06-26 21:40 +0200 |
| Message-ID | <tWI1A-6sb-35@gated-at.bofh.it> (permalink) |
| References | (1 earlier) <tWC5Q-2P3-11@gated-at.bofh.it> <tWFGq-56V-17@gated-at.bofh.it> <tWFGr-56V-35@gated-at.bofh.it> <tWGCu-5HI-19@gated-at.bofh.it> <tWGVP-5Oa-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Mon 26 Jun 2017 at 13:27:42 -0500, David Wright wrote: > On Mon 26 Jun 2017 at 19:01:21 (+0100), Brian wrote: > > On Mon 26 Jun 2017 at 13:06:29 -0400, Greg Wooledge wrote: > > > > > On Tue, Jun 27, 2017 at 03:04:30AM +1000, John Elliot V wrote: > > > > Can I ask why you did the apt-get upgrade before the apt-get > > > > dist-upgrade? Why not just go straight for apt-get dist-upgrade..? > > > > > > Probably because (s)he read the release notes: > > > > > > <https://www.debian.org/releases/stable/amd64/release-notes/ch-upgrading.en.html#minimal-upgrade> > > > > The notes are clear but what is the point of following this procedure? > > > > You do an upgrade, so an upgrade is done. No new packages. Fair enough. > > I have a desktop that I don't use very frequently at the moment. > Last time I booted it up, the apt-get upgrade downloaded over 70 > packages. There was probably a point-release involved. > That contrasts with my regularly used machines that apt-get -d upgrade > every three hours and email me if their cache contains any packages. > > If you watch upgrades taking place, you can see that they're phased. > Apt-ish and Dpkg-ish are setup before other packages are unpacked, > and so on. It's not all just done in one heap. > > By running upgrade before dist-upgrade, you reduce complexity by > maximising the compatibility of packages with each other. When > lenny was replaced by squeeze, even these two steps were > insufficient; the kernel and udev needed replacing as a pair after > the (lenny) upgrade and before the (squeeze) dist-upgrade. Thank you for reminding us of Lenny -> Squeeze. It is not the same this time but I have been scarred by it! 'apt-get upgrade' is such a simple step to take first for the reason you give that it would be churlish not to agree with it for the reason you give. > > You are none the wiser about what would happen if a dist-upgrade is done > > next, so it is still a dive into the unknown. > > > > Then you dist-upgrade. Why not leave out the previous step, unless there > > are packages you wish to keep? Perhaps an illustrative example of when > > the single-step process dist-upgrade fails would be helpful. The advice > > > > This has the effect of upgrading those packages which can be > > upgraded without requiring any other packages to be removed > > or installed > > > > simply repeats what apt-get(8) says without its detailed explanation. > > > > (I upgrade, reboot, dist-upgrade, But I am into cargo-cult). > > Oh, I forgot. It was necessary, of course, to reboot after replacing > the kernel and udev in the lenny/squeeze process, in order for the > newly installed kernel to be actually running as opposed to just > spinning on the drive. It was. I am a creature of habit. I still reboot between upgrade and dist-upgrade when I eventually upgrade a machine from one distribution to another. -- Brian. -- Brian.
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
How did you update to stretch? Hans <hans.ullrich@loop.de> - 2017-06-26 15:00 +0200
Re: How did you update to stretch? Jonathan Dowland <jmtd@debian.org> - 2017-06-26 15:20 +0200
Re: How did you update to stretch? John Hasler <jhasler@newsguy.com> - 2017-06-26 15:30 +0200
Re: How did you update to stretch? Hans <hans.ullrich@loop.de> - 2017-06-26 15:50 +0200
Re: How did you update to stretch? Hans <hans.ullrich@loop.de> - 2017-06-26 16:00 +0200
Re: How did you update to stretch? Eduardo M KALINOWSKI <eduardo@kalinowski.com.br> - 2017-06-26 16:50 +0200
Re: How did you update to stretch? Joe <joe@jretrading.com> - 2017-06-26 17:30 +0200
Re: How did you update to stretch? Alberto Luaces <aluaces@udc.es> - 2017-06-26 15:50 +0200
Re: How did you update to stretch? John Elliot V <jj5@jj5.net> - 2017-06-26 19:10 +0200
Re: How did you update to stretch? Greg Wooledge <wooledg@eeg.ccf.org> - 2017-06-26 19:10 +0200
Re: How did you update to stretch? John Elliot V <jj5@jj5.net> - 2017-06-26 19:20 +0200
Re: How did you update to stretch? Brian <ad44@cityscape.co.uk> - 2017-06-26 20:10 +0200
Re: How did you update to stretch? The Wanderer <wanderer@fastmail.fm> - 2017-06-26 20:20 +0200
Re: How did you update to stretch? Brian <ad44@cityscape.co.uk> - 2017-06-26 21:00 +0200
Re: How did you update to stretch? David Wright <deblis@lionunicorn.co.uk> - 2017-06-26 20:30 +0200
Re: How did you update to stretch? The Wanderer <wanderer@fastmail.fm> - 2017-06-26 20:40 +0200
Re: How did you update to stretch? Brian <ad44@cityscape.co.uk> - 2017-06-26 21:40 +0200
Re: How did you update to stretch? John Elliot V <jj5@jj5.net> - 2017-06-26 22:20 +0200
Re: How did you update to stretch? Fungi4All <fungilife@protonmail.com> - 2017-06-27 02:10 +0200
Re: How did you update to stretch? Joe <joe@jretrading.com> - 2017-06-27 09:20 +0200
Re: How did you update to stretch? deloptes <deloptes@gmail.com> - 2017-06-28 00:00 +0200
Re: How did you update to stretch? Dave Sherohman <dave@sherohman.org> - 2017-06-27 10:10 +0200
Re: How did you update to stretch? Fungi4All <fungilife@protonmail.com> - 2017-06-27 22:20 +0200
Re: How did you update to stretch? Joe <joe@jretrading.com> - 2017-06-26 19:30 +0200
Re: How did you update to stretch? Brian <ad44@cityscape.co.uk> - 2017-06-26 20:20 +0200
Re: How did you update to stretch? Jonathan Dowland <jmtd@debian.org> - 2017-06-26 23:00 +0200
Re: How did you update to stretch? Jörg-Volker Peetz <jvpeetz@web.de> - 2017-06-26 17:30 +0200
csiph-web