The officially official Devuan Forum!

You are not logged in.

#1 2020-07-20 17:45:47

Altoid
Member
Registered: 2017-05-07
Posts: 416  

Devuan ascii 2.1 - 'Kept back' packages

Hello:

I was in the process of updating/upgrading a Devuan image I burn to a USB plug as an emergency recovery tool.

groucho@devuan:~$ uname -a
Linux devuan 4.9.0-12-amd64 #1 SMP Debian 4.9.210-1+deb9u1 (2020-06-07) x86_64 GNU/Linux
groucho@devuan:~$ 

The image was built with refracta snapshot 10.2.4 (20190713).

It is supposed to live inside the box, plugged into a USB socket on the MB but I've been sloppy lately so it is outside and not updated.
But I digress ...

On starting the process I came across this:

---

groucho@devuan:~$ sudo apt-get update
[sudo] password for groucho: 
Get:1 http://deb.devuan.org/merged ascii InRelease [25.6 kB]
Get:2 http://deb.devuan.org/merged ascii-security InRelease [25.6 kB]
Get:3 http://deb.devuan.org/merged ascii-updates InRelease [25.6 kB]
Get:4 http://deb.devuan.org/devuan ascii-proposed InRelease [54.5 kB]
Get:5 http://deb.devuan.org/merged ascii-backports InRelease [25.6 kB]
Get:6 http://deb.devuan.org/merged ascii/main amd64 Packages [7198 kB]
Get:7 http://deb.devuan.org/merged ascii/contrib amd64 Packages [50.8 kB]                                                                  
Get:8 http://deb.devuan.org/merged ascii/non-free amd64 Packages [78.8 kB]                                                                 
Get:9 http://deb.devuan.org/merged ascii-updates/main amd64 Packages [3504 B]                                                              
Fetched 7488 kB in 9s (767 kB/s)                                                                                                           
Reading package lists... Done
groucho@devuan:~$ sudo apt-get upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done

The following packages have been kept back:
  linux-headers-amd64 linux-image-amd64                           <------------ this

The following packages will be upgraded:
  glib-networking glib-networking-common glib-networking-services libcups2 libgnutls30 libneon27-gnutls libopenjp2-7 libperl5.24
  linux-compiler-gcc-6-x86 linux-kbuild-4.9 nfs-common perl perl-base perl-modules-5.24 tzdata wpasupplicant xdg-utils
17 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
Need to get 12.6 MB of archives.
After this operation, 63.5 kB of additional disk space will be used.
Do you want to continue? [Y/n] 

Makes me wonder because I have linux-headers-amd64 and linux-image-amd64 as essential.
¿Why are these packages being kept back?
¿Is there some application that would break if forced the upgrade?
If so, ¿how can I find out which one?

Thanks in advance,

A.

Offline

#2 2020-07-20 18:03:10

Head_on_a_Stick
Member
From: London
Registered: 2019-03-24
Posts: 841  
Website

Re: Devuan ascii 2.1 - 'Kept back' packages

The kernel & headers metapackages need to install new versions of their dependencies so use either

sudo apt-get dist-upgrade

or

sudo apt-get upgrade --with-new-pkgs

Black Lives Matter

Offline

#3 2020-07-20 19:27:36

Altoid
Member
Registered: 2017-05-07
Posts: 416  

Re: Devuan ascii 2.1 - 'Kept back' packages

Hello:

Head_on_a_Stick wrote:

The kernel & headers metapackages need to install new versions of their dependencies ...

Right ...

But why has this happened with my VM Devuan ascii ...

groucho@devuan:~$ uname -a
Linux devuan 4.9.0-12-amd64 #1 SMP Debian 4.9.210-1+deb9u1 (2020-06-07) x86_64 GNU/Linux
groucho@devuan:~$ 

... and not with my everyday rig:

groucho@devuan:~$ uname -a
Linux devuan 4.9.0-12-amd64 #1 SMP Debian 4.9.210-1+deb9u1 (2020-06-07) x86_64 GNU/Linux
groucho@devuan:~$ 

ie: what difference is there between them that causes those packages to be kept back? <- which was the reason for my OP.

There's more ... 

EDIT:
It seems that between running apt-get update and apt-get upgrade on my rig and then doing the same on the VM used for the USB plug, the repos were updated.

So it looked like two different update/upgrade processes were taking place.

ie: one machine did it on the repos just before they were updated and the other just after they were updated.

Just what are the chances?  8^D

Thanks a lot for your input.

Cheers,

A.

Last edited by Altoid (2020-07-21 02:20:15)

Offline

Board footer