Caution -- Linux headers to be removed

[dibl]

Full-upgrade at this moment will give you:

Code Auswählen Erweitern

.......
.
.
The following packages will be REMOVED:
  gcc-10 linux-headers-5.6.12-towo.2-siduction-amd64 linux-headers-5.6.13-towo.1-siduction-amd64
  linux-headers-siduction-amd64
.
.
...


EDIT: That was on an HP laptop.  On an older Dell laptop, there is no problem -- so .....

EDIT #2: One machine shows this problem, three machines do not have the problem.  It might be a configuration issue of some kind with my HP laptop -- if that is it, sorry tor the noise!

[bevo]

not so with

Code Auswählen Erweitern

apt upgrade strange 

[oduffo]

Same for me

Code Auswählen Erweitern

Die folgenden Pakete werden ENTFERNT:
  gcc-10 linux-headers-5.6.12-towo.1-siduction-amd64 linux-headers-5.6.13-towo.1-siduction-amd64 linux-headers-siduction-amd64

on my desktop

Code Auswählen Erweitern


System:    Host: kronos Kernel: 5.6.13-towo.1-siduction-amd64 x86_64 bits: 64 Desktop: KDE Plasma 5.17.5
           Distro: siduction 16.1.0 Patience - kde - (201612232347)
CPU:       Quad Core: Intel Core i5-6600K type: MCP speed: 3772 MHz min/max: 800/3900 MHz
----

Code Auswählen Erweitern

apt upgrade

doesn't want to remove anything.

Indeed, strange.

Gruß oduffo

[vilde]

It's not at all strange, that's how it shall be.
Apt upgrade never remove anything, it shall not, can not.

[unklarer]

You are not alone. Same here!

Code Auswählen Erweitern

Die folgenden Pakete werden ENTFERNT:
  gcc-10 linux-headers-5.6.12-towo.1-siduction-amd64 linux-headers-5.6.13-towo.1-siduction-amd64 linux-headers-siduction-amd64

wait   

[vilde]

For me as a lacy user who not do a du so often the full-upgrade did install the kernel 5.6.13-towo.1-siduction-amd64 x86_64 probably with headers and also installed gcc-10.

BUT it removed gcc-7. I let that go even if I have no idea if I need it or not. My installations is rather messy anyway, I go on as long it works . Maybe gcc-7 is a problem?

[hendrikL]

Here™, nothing to be removed!

And I always do a full-upgrade, I never only use "apt upgrade".
Doing "apt upgrade" is the best way to shoot in your own feet, on a debian unstable/sid, my two cents.
What i do, is, i cherry-pick important security updates, if a  big remove will perform during "apt full-upgrade" because of a  transition.

Code Auswählen Erweitern


:~$ LANG=C apt full-upgrade -s
[ ... ]
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

:~$ LANG=C apt policy gcc-10
gcc-10:
  Installed: 10.1.0-2
  Candidate: 10.1.0-2
  Version table:
*** 10.1.0-2 500
        500 http://deb.debian.org/debian unstable/main amd64 Packages
        100 /var/lib/dpkg/status

l:~$ LANG=C inxi -Sx
System:    Host: hhl Kernel: 5.6.13-towo.1-siduction-amd64 x86_64 bits: 64 compiler: gcc v: 10.1.0 Desktop: KDE Plasma 5.18.5
           Distro: siduction 18.3.0 Patience - kde - (201809172151) base: Debian GNU/Linux bullseye/sid


Take a deeper look to gcc-10, maybe there is the reason why!?

[ReinerS]

Looks like really the gcc stuff somehow triggers this problem on some boxes.
I donot have it on my AMD Phenom II X6 big box but on my I5-3360 based HP-Laptop I get it as soon as I try to mark/update a gcc/cpp10 package for update.
Both boxes were softwarewise much the same, the laptop had been newly installed a while ago, the big box around a year ago.
regards
Reiner

[unklarer]

@hendrikL,
I swear never to do anything different:

Code Auswählen Erweitern

apt update && apt dist-upgrade


The difference to you is patience 16.1.0 and plasma 5.17.5

Code Auswählen Erweitern

$ LANG=C apt policy gcc-10
gcc-10:
  Installed: 10.1.0-1
  Candidate: 10.1.0-2
  Version table:
     10.1.0-2 500
        500 http://deb.debian.org/debian unstable/main amd64 Packages
*** 10.1.0-1 100
        100 /var/lib/dpkg/status

Code Auswählen Erweitern

$ LANG=C inxi -Sx
System:    Host: sidukde Kernel: 5.6.13-towo.1-siduction-amd64 x86_64 bits: 64 compiler: gcc
           v: 10.1.0 Desktop: KDE Plasma 5.17.5
           Distro: siduction 16.1.0 Patience - kde - (201702251051)
           base: Debian GNU/Linux bullseye/sid

[dibl]

I got curious and started playing on the HP laptop that caused me to make the original post.  The bad actor appears to be libgcc1, which falsely claims there is a problem with the installed gcc-10-base package. Here is how I fixed it:

Code Auswählen Erweitern

apt full-upgrade

Let it rip out all the packages.

Code Auswählen Erweitern

apt remove libgcc1

apt install linux-headers-siduction-amd64

This pulled back in everything that was removed.

The system is stable and nothing else appears to have been changed.

[hendrikL]

@unklarer
mh, try "apt full-upgrade gcc-10+"

or first "apt install gcc-10"

[unklarer]

@dibl,
thank you very much! That's the way it went.   

Code Auswählen Erweitern

~$ LANG=C apt policy gcc-10
gcc-10:
  Installed: 10.1.0-2
  Candidate: 10.1.0-2
  Version table:
*** 10.1.0-2 500
        500 http://deb.debian.org/debian unstable/main amd64 Packages
        100 /var/lib/dpkg/status

@hendrikL,
I'm sorry, but I've already taken the path of dibl.   

[hendrikL]

Code Auswählen Erweitern

$ LANG=C apt policy libgcc1
libgcc1:
  Installed: (none)
  Candidate: 1:10.1.0-1

@unklarer, everything is okay, no reason to be sorry

[unklarer]

^^I'm glad you're here.   

[vilde]

I got curious and started playing on the HP laptop that caused me to make the original post.  The bad actor appears to be libgcc1, which falsely claims there is a problem with the installed gcc-10-base package. Here is how I fixed it:

Code Auswählen Erweitern

apt full-upgrade

Let it rip out all the packages.

Code Auswählen Erweitern

apt remove libgcc1

apt install linux-headers-siduction-amd64

This pulled back in everything that was removed.

The system is stable and nothing else appears to have been changed.

I did a check, I don't have libgcc1 installed, probably the reason that I got another behavior.