On Sun 21 May 2017 at 16:31:55 (+0200), Dejan Jocic wrote: > On 21-05-17, Richard Owlett wrote: > > I had done: > > apt-get update > > apt-get upgrade > > The tail end of the output was: > > ... > > Setting up libkde3support4 (4:4.14.26-2) ... > > Setting up libktexteditor4 (4:4.14.26-2) ... > > Setting up libkdewebkit5 (4:4.14.26-2) ... > > Setting up libkhtml5 (4:4.14.26-2) ... > > Setting up libplasma3 (4:4.14.26-2) ... > > Setting up kdelibs5-plugins (4:4.14.26-2) ... > > Processing triggers for initramfs-tools (0.130) ... > > update-initramfs: Generating /boot/initrd.img-4.9.0-2-686-pae > > I: The initramfs will attempt to resume from /dev/sda5 > > I: (UUID=5d0c821b-26b2-4d38-b7fe-dc7db1b72576) > > I: Set the RESUME variable to override this. > > Processing triggers for libc-bin (2.24-10) ... > > root@stretch-2nd:/home/richard# > > > > Before asking for confirmation to do the "upgrade" it said 3 packages would > > not be upgraded. > > If it said which packages, I didn't spot it. > > I then reran with following result. > > > > root@stretch-2nd:/home/richard# apt-get upgrade > > Reading package lists... Done > > Building dependency tree > > Reading state information... Done > > Calculating upgrade... Done > > The following packages were automatically installed and are no longer > > required: > > dconf-cli gir1.2-notify-0.7 libconfig9 libgtkspell3-3-0 libindicator3-7 > > mate-indicator-applet > > mate-indicator-applet-common python3-psutil python3-setproctitle > > Use 'apt autoremove' to remove them. > > The following packages have been kept back: > > linux-image-686-pae xorg xserver-xorg > > 0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded. > > root@stretch-2nd:/home/richard# > > > > My questions: > > > > 1. In the first run, I don't understand: > > Processing triggers for initramfs-tools (0.130) ... > > update-initramfs: Generating /boot/initrd.img-4.9.0-2-686-pae > > I: The initramfs will attempt to resume from /dev/sda5 > > I: (UUID=5d0c821b-26b2-4d38-b7fe-dc7db1b72576) > > I: Set the RESUME variable to override this. > > As /dev/sda5 is my SWAP. > > > > 2. I don't understand any implications of: > > The following packages have been kept back: > > linux-image-686-pae xorg xserver-xorg > > > > TIA > > > > > > > > > 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.) > 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.
