The gates of hell are opened ...

[linearJim]

What is your running kernel version?  If it is a 4.0.x, then you can let the old headers for 3.19 go -- you will never need them unless you revert to running a 3.19 kernel and need to compile something.

 i am not using kernel 4 since i want nvidia driver 346 for now]

i will d-u later, let it uninstall header files and i will manually install them again

[towo]

It's a typical multiarch "issue", it will happen now often, since the freeze is over.

[linearJim]

@towo
thanks, good to kwow..

because autoremove wants  to uninstall them again 

Code: [Select]

root:~$ apt-get dist-upgrade -d
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
The following packages will be REMOVED:
  linux-headers-3.19.3-towo.3-siduction-amd64
The following packages have been kept back:
  cpp-4.9 g++-4.9 gcc-4.9 gcc-4.9-base gcc-4.9-base:i386 gfortran-4.9 libasan1 libgcc-4.9-dev libgcc1 libgcc1:i386 libgfortran-4.9-dev libstdc++-4.9-dev libstdc++6
  libstdc++6:i386
0 upgraded, 0 newly installed, 1 to remove and 14 not upgraded.
After this operation, 32.4 MB disk space will be freed.
Do you want to continue? [Y/n] n
Abort.
i am leaving as is for now, all good..

[towo]

If you don't use kernel 3.19.3-towo.3-siduction-amd64, you can remove the headers for this kernel.
More important would be the output of

Code: [Select]

uname -a
dpkg -l | egrep "linux-image|linux-headers"

[linearJim]

yes i am using this kernel

Code: [Select]

root:~$ uname -a
Linux dell 3.19.3-towo.3-siduction-amd64 #1 SMP PREEMPT siduction 3.19-12 (2015-04-10) x86_64 GNU/Linux
root:~$ dpkg -l|egrep "linux-image|linux-headers"
ii  linux-headers-3.16.0-4-amd64                    3.16.7-ckt9-3                          amd64        Header files for Linux 3.16.0-4-amd64
ii  linux-headers-3.16.0-4-common                   3.16.7-ckt9-3                          amd64        Common header files for Linux 3.16.0-4
ii  linux-headers-3.19.3-towo.3-siduction-amd64     3.19-12                                amd64        Header files for Linux 3.19.3-towo.3-siduction-amd64
ii  linux-headers-amd64                             3.16+63                                amd64        Header files for Linux amd64 configuration (meta-package)
ii  linux-image-3.19.3-towo.2-siduction-amd64       3.19-11                                amd64        Linux 3.19 for 64-bit PCs
ii  linux-image-3.19.3-towo.3-siduction-amd64       3.19-12                                amd64        Linux 3.19 for 64-bit PCs

[ragupo]

I get

Code: [Select]

The following packages will be REMOVED:
  build-essential g++ g++-4.9 gcc gcc-4.9 gcc-4.9-multilib gcc-multilib
  linux-headers-3.16-0.towo-siduction-amd64
  linux-headers-3.18-3.towo-siduction-amd64
  linux-headers-3.19-0.towo.2-siduction-amd64
  linux-headers-3.19.1-towo.1-siduction-amd64
  linux-headers-3.19.2-towo.1-siduction-amd64
  linux-headers-4.0.0-towo.1-siduction-amd64 linux-headers-siduction-amd64
The following NEW packages will be installed:
  gcc-5-base gdal-bin libcmis-0.5-5 libfcgi0ldbl libisl13 libjs-leaflet libnm0
  libpagemaker-0.0-0 libqgis-analysis2.8.1 libqgis-core2.8.1 libqgis-customwidgets
  libqgis-gui2.8.1 libqgis-networkanalysis2.8.1 libqgis-server2.8.1
  libqgispython2.8.1 libqscintilla2-11 libqscintilla2-l10n libx265-43:i386
  python-gdal python-jinja2 python-libdiscid python-markupsafe python-psycopg2
  python-pygments python-pyspatialite python-qgis python-qgis-common
  python-qscintilla2 qt4-designer
The following packages have been kept back:
  cpp-4.9 gcc-4.9-base gcc-4.9-base:i386 lib32asan1 lib32gcc-4.9-dev libasan1
  libgcc-4.9-dev libgcc1 libgcc1:i386 libgomp1 libgomp1:i386 libstdc++-4.9-dev
  libstdc++6 libstdc++6:i386 libx32asan1 libx32gcc-4.9-dev
Im running kernel 4.0.0.-towo.1. Do i need the headers for that kernel?

[dibl]

Im running kernel 4.0.0.-towo.1. Do i need the headers for that kernel?

YES, if you build/compile your own packages or kernel modules.


NO, if you don't do any compiling.

[KrunchTime]

Variety. I've got the resources, so why not? Of course, if it came down to a "Desert-Island-Distro", I'd have to go with Xfce.

You mentioned tint2. I added it to both of them:

Nice...what's that on the right in the second screenshot?  Is that conky?  I like it.

Correct.  I did not intend to suggest that removals are always a bad thing.  But I do suggest that any removals always be examined thoughtfully -- the fact that something is to be removed is your signal to be extra careful before the next press of "Enter".  For example, this morning the build-essential and linux-headers packages were removed on one of my systems.  I let them go, because I can reinstall them the next time something needs to be compiled, but that is the type of removal that can be disruptive for a less experienced user.

Thank you for the clarification.

YES, if you build/compile your own packages or kernel modules.  NO, if you don't do any compiling.

I think dkms may require headers.

[terroreek]

I think dkms may require headers.

It does indeed.  Well at least for me if I yank the headers it wasnt to yank the nvidia-drivers and the nvidia-dkms package and the virtualbox-dkms package.

[KrunchTime]

@terroreek:  AMD/ATI proprietary graphics driver and VirtualBox here.  However, I was thinking a bit after my last post.  I believe DKMS essentially recompiles the kernel when you install/upgrade proprietary graphics drivers or VirtualBox.  Therefore, what dibl said is still correct.  I just added a bit of nuance to his statement.

[linearJim]

i believe it  rebuilds the module when you install a new kernel and if i remember correctly the package dkms has kernel headers in "Recommends" and virtualbox|nvida|whatever-dkms depends on dkms...

[terroreek]

Just applied updates today about 200+ nothing removed so far so good.