Re: Questions after doing update and upgrade on Stretch
On 26-05-17, David Wright wrote:
> On Mon 22 May 2017 at 11:12:02 (+0200), Dejan Jocic wrote:
> > On 21-05-17, Brian wrote:
> > > On Sun 21 May 2017 at 22:18:11 +0200, Dejan Jocic wrote:
> > >
> > > > On 21-05-17, David Wright wrote:
> > > > > On Sun 21 May 2017 at 16:31:55 (+0200), Dejan Jocic wrote:
> > > > > > >
> > > > > > As for number 1 can't say much about it, I do not get it either. But 2
> > > > > > happens because you've used apt-get upgrade instead of apt-get
> > > > > > dist-upgrade. Packages that will uninstall some packages already
> > > > > > installed on your system and that will change some dependencies
> > > > > > require dist-upgrade.
> > > > >
> > > > > Agreed.
> > > > >
> > > > > > It happens always in case of linux-image packages.
> > > > >
> > > > > Is this¹ new with stretch? My linux-images upgrade just like any other
> > > > > package; here's the penultimate occasion for jessie:
> > > > >
> > > > > Start-Date: 2017-03-08 19:20:34
> > > > > Commandline: apt-get upgrade
> > > > > Upgrade: linux-source-3.16:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), linux-headers-3.16.0-4-586:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), linux-image-3.16.0-4-586:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), linux-libc-dev:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), linux-compiler-gcc-4.8-x86:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), linux-headers-3.16.0-4-common:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2)
> > > > > End-Date: 2017-03-08 19:22:50
> > > > >
> > > > > (The last one's log was rather larger.)
> > > >
> > > > Ehh, sorry not sure if it is new with Stretch, can't remember for
> > > > Jessie. I'm certain that it was like that on Stretch and on Ubuntu
> > > > 16.04.
> > >
> > > Rather than just a contrast, I was rather hoping to hear how David
> > > Wright's observations (which I agree with)fit in with yours.
> > >
> > Sorry, not sure what I can add to it.
> >
> > > > > > It will leave your previous working linux-image on though, but will
> > > > > > uninstall one older than that, so you will always end up with chance to
> > > > > > boot in working kernel, if new one messes up some things.
> > > > >
> > > > > Same question. My wheezy system has had at least 28 linux-image
> > > > > upgrades (3.2.57-3+deb7u2→3.2.60-1+deb7u1 to 3.2.86-1→3.2.88-1)
> > > > > but there's still only one kernel image on the system:
> > > > >
> > > > > -rw-r--r-- 1 root root 134839 Apr 27 16:52 config-3.2.0-4-686-pae
> > > > > drwxr-xr-x 3 root root 12288 Apr 28 07:44 grub
> > > > > -rw-r--r-- 1 root root 2672854 Apr 28 07:44 initrd.img-3.2.0-4-686-pae
> > > > > -rw-r--r-- 1 root root 1674268 Apr 27 16:52 System.map-3.2.0-4-686-pae
> > > > > -rw-r--r-- 1 root root 2709184 Apr 27 16:51 vmlinuz-3.2.0-4-686-pae
> > > > >
> > > > > (I have to notice these upgrades myself because they overwrite
> > > > > my edited version of /boot/grub/grub.cfg which I then replace.)
> > > > >
> > > > > Cheers,
> > > > > David.
> > > > >
> > > > > ¹ I'm not disagreeing that something is holding back the upgrade
> > > > > on this specific occasion, but this is unusual.
> >
> >
> > This is what I have in /boot and, as stated above, usual outcome of
> > upgrades, both in Stretch and in Ubuntu 16.04:
> >
> > -rw-r--r-- 1 root root 186695 Mar 30 03:16 config-4.9.0-2-amd64
> > -rw-r--r-- 1 root root 186380 May 2 17:21 config-4.9.0-3-amd64
> > drwxr-xr-x 5 root root 4096 May 19 08:55 grub
> > -rw-r--r-- 1 root root 19660713 May 17 16:43 initrd.img-4.9.0-2-amd64
> > -rw-r--r-- 1 root root 19534447 May 18 08:40 initrd.img-4.9.0-3-amd64
> > -rw-r--r-- 1 root root 3169870 Mar 30 03:16 System.map-4.9.0-2-amd64
> > -rw-r--r-- 1 root root 3176652 May 2 17:21 System.map-4.9.0-3-amd64
> > -rw-r--r-- 1 root root 4193832 Mar 30 18:43 vmlinuz-4.9.0-2-amd64
> > -rw-r--r-- 1 root root 4204320 May 2 17:21 vmlinuz-4.9.0-3-amd64
> >
> > As you can see, 2 kernels. All i do is my morning routine which consists
> > of apt-get update && apt-get upgrade, followed by apt-get dist-upgrade
> > in case of need(as stated before, usually case of need is kernel
> > upgrade). Of course, it is followed by apt-get autoremove too.I do not
> > have anything unusual on this system. It was fairly recent install of
> > jessie(few months ago), followed by upgrade to stretch right after
> > install. Was installed from unofficial net-install cd with firmware on
> > it. Also, nothing was changed in apt preferences and stuff like that.
>
> OK, I've just been looking at kernel changelogs and that explains
> what's going on here. There's nothing different about kernels in
> particular, and the reason you've got two kernels is that they
> are different kernels, so different Debian packages.
>
> I installed wheezy no earlier than May 2013 (ie not as a release
> candidate) and 3.2.0-4 came out in Sept 2012, so as I said
> I've had at least 28 upgrades of the one kernel version.
>
> OTOH the only stretch system I have is currently a basic system,
> with just 248 packages (minimal install from RC3). The kernel
> version is linux-image-4.9.0-2 at Debian version 4.9.18-1 and that
> version is obsolete. Currently we seem to be at 4.9.0-3 (4.9.25-1).
>
> So on 2 May 2017, a new kernel version came out, which you
> installed. The only reason your old one wasn't removed is
> because it's a different Debian package, with a different name
> and containing a different kernel, with an ABI of 3, not 2.
> In a nutshell:
>
> $ grep -n '\<Ben\>\|\<Bump\>\|^linux' linux_4.9.25-1_changelog | head -n 5
> 1:linux (4.9.25-1) unstable; urgency=medium
> 331: [ Ben Hutchings ]
> 335: * Bump ABI to 3
> 418: -- Ben Hutchings <ben@decadent.org.uk> Tue, 02 May 2017 16:21:44 +0100
> 420:linux (4.9.18-1) unstable; urgency=medium
> $
>
> Cheers,
> David.
>
Think that misunderstanding came from my bad English and that we were
thinking abut same thing. I sometimes miss word, or two while typing in
English. Guess that in this case word new was missed in front of
linux-images. Yes, those are new but I've thought that it was obvious.
As for reason why old one is not removed, it is because Debian keeps not
just newly installed kernel, but also one previously installed. One
before that was removed by apt-get autoremove.
Reply to: