libvtv0 will be removed

Started by Jörg, 2014/06/28, 10:54:15

Previous topic - Next topic

Jörg

Since june 26th my DU shows the following output:

The following packages will be REMOVED:
   libvtv0 (4.9.0-7)
The following NEW packages will be installed:
   linux-headers-3.15-2.towo-siduction-amd64 (3.15-8)
   linux-image-3.15-2.towo-siduction-amd64 (3.15-8)
The following packages will be upgraded:
   cpp (4.9.0-3 => 4.9.0-4)
   cpp-4.8 (4.8.3-3 => 4.8.3-4)
   cpp-4.9 (4.9.0-7 => 4.9.0-9)
   cups (1.7.3-5 => 1.7.3-6)
   cups-bsd (1.7.3-5 => 1.7.3-6)
   cups-client (1.7.3-5 => 1.7.3-6)
   cups-common (1.7.3-5 => 1.7.3-6)
   cups-core-drivers (1.7.3-5 => 1.7.3-6)
   cups-daemon (1.7.3-5 => 1.7.3-6)
   cups-ppdc (1.7.3-5 => 1.7.3-6)
   cups-server-common (1.7.3-5 => 1.7.3-6)
   e2fslibs (1.42.10-1 => 1.42.10-1.1)
   e2fsprogs (1.42.10-1 => 1.42.10-1.1)
   g++ (4.9.0-3 => 4.9.0-4)
   g++-4.8 (4.8.3-3 => 4.8.3-4)
   g++-4.9 (4.9.0-7 => 4.9.0-9)
   gcc (4.9.0-3 => 4.9.0-4)
   gcc-4.8 (4.8.3-3 => 4.8.3-4)
   gcc-4.8-base (4.8.3-3 => 4.8.3-4)
   gcc-4.9 (4.9.0-7 => 4.9.0-9)
   gcc-4.9-base (4.9.0-7 => 4.9.0-9)
   libasan0 (4.8.3-3 => 4.8.3-4)
   libasan1 (4.9.0-7 => 4.9.0-9)
   libatomic1 (4.9.0-7 => 4.9.0-9)
   libbluray1 (0.6.0+dfsg-1 => 0.6.0+dfsg-2)
   libcilkrts5 (4.9.0-7 => 4.9.0-9)
   libcomerr2 (1.42.10-1 => 1.42.10-1.1)
   libcups2 (1.7.3-5 => 1.7.3-6)
   libcupscgi1 (1.7.3-5 => 1.7.3-6)
   libcupsimage2 (1.7.3-5 => 1.7.3-6)
   libcupsmime1 (1.7.3-5 => 1.7.3-6)
   libcupsppdc1 (1.7.3-5 => 1.7.3-6)
   libdata-perl-perl (0.002007-1 => 0.002009-1)
   libdb5.3 (5.3.28-4 => 5.3.28-5)
   libgcc-4.8-dev (4.8.3-3 => 4.8.3-4)
   libgcc-4.9-dev (4.9.0-7 => 4.9.0-9)
   libgcc1 (4.9.0-7 => 4.9.0-9)
   libgdbm3 (1.8.3-12 => 1.8.3-12+b1)
   libgfortran3 (4.9.0-7 => 4.9.0-9)
   libgomp1 (4.9.0-7 => 4.9.0-9)
   libgudev-1.0-0 (204-12 => 204-13)
   libitm1 (4.9.0-7 => 4.9.0-9)
   liblsan0 (4.9.0-7 => 4.9.0-9)
   libmediastreamer-base3 (3.6.1-2.3 => 3.6.1-2.3+b1)
   libortp9 (3.6.1-2.3 => 3.6.1-2.3+b1)
   libpam-systemd (204-12 => 204-13)
   libquadmath0 (4.9.0-7 => 4.9.0-9)
   libss2 (1.42.10-1 => 1.42.10-1.1)
   libstdc++-4.8-dev (4.8.3-3 => 4.8.3-4)
   libstdc++-4.9-dev (4.9.0-7 => 4.9.0-9)
   libstdc++6 (4.9.0-7 => 4.9.0-9)
   libsystemd-daemon0 (204-12 => 204-13)
   libsystemd-id128-0 (204-12 => 204-13)
   libsystemd-journal0 (204-12 => 204-13)
   libsystemd-login0 (204-12 => 204-13)
   libtasn1-6 (3.6-3 => 3.7-1)
   libtsan0 (4.9.0-7 => 4.9.0-9)
   libubsan0 (4.9.0-7 => 4.9.0-9)
   libudev1 (204-12 => 204-13)
   linux-headers-3.15-1.towo.2-siduction-amd64 (3.15-5 => 3.15-7)
   linux-headers-siduction-amd64 (3.15-5 => 3.15-8)
   linux-image-3.15-1.towo.2-siduction-amd64 (3.15-5 => 3.15-7)
   linux-image-siduction-amd64 (3.15-5 => 3.15-8)
   po-debconf (1.0.16+nmu2 => 1.0.16+nmu3)
   systemd (204-12 => 204-13)
   systemd-sysv (204-12 => 204-13)
   udev (204-12 => 204-13)
   xserver-xorg-video-ati (7.3.0-1+b1 => 7.4.0-1)
   xserver-xorg-video-radeon (7.3.0-1+b1 => 7.4.0-1)
69 upgraded, 2 newly installed, 1 to remove and 0 not upgraded.

After setting libvtv0 on hold, DU gives:

The following packages will be REMOVED:
   build-essential (11.6)
   g++ (4.9.0-4)
   g++-4.9 (4.9.0-9)
   gcc (4.9.0-4)
   gcc-4.9 (4.9.0-9)
   libgcc-4.9-dev (4.9.0-9)
   libstdc++-4.9-dev (4.9.0-9)
   linux-headers-3.15-0.towo.3-siduction-amd64 (3.15-3)
   linux-headers-3.15-1.towo-siduction-amd64 (3.15-4)
   linux-headers-3.15-1.towo.2-siduction-amd64 (3.15-7)
   linux-headers-siduction-amd64 (3.15-8)
The following NEW packages will be installed:
   linux-image-3.15-2.towo-siduction-amd64 (3.15-8)
The following packages have been kept back:
   cpp-4.9 (4.9.0-7 => 4.9.0-9)
   gcc-4.9-base (4.9.0-7 => 4.9.0-9)
   libasan1 (4.9.0-7 => 4.9.0-9)
   libatomic1 (4.9.0-7 => 4.9.0-9)
   libcilkrts5 (4.9.0-7 => 4.9.0-9)
   libgcc1 (4.9.0-7 => 4.9.0-9)
   libgfortran3 (4.9.0-7 => 4.9.0-9)
   libgomp1 (4.9.0-7 => 4.9.0-9)
   libitm1 (4.9.0-7 => 4.9.0-9)
   liblsan0 (4.9.0-7 => 4.9.0-9)
   libquadmath0 (4.9.0-7 => 4.9.0-9)
   libstdc++6 (4.9.0-7 => 4.9.0-9)
   libtsan0 (4.9.0-7 => 4.9.0-9)
   libubsan0 (4.9.0-7 => 4.9.0-9)
The following packages will be upgraded:
   cpp (4.9.0-3 => 4.9.0-4)
   cpp-4.8 (4.8.3-3 => 4.8.3-4)
   cups (1.7.3-5 => 1.7.3-6)
   cups-bsd (1.7.3-5 => 1.7.3-6)
   cups-client (1.7.3-5 => 1.7.3-6)
   cups-common (1.7.3-5 => 1.7.3-6)
   cups-core-drivers (1.7.3-5 => 1.7.3-6)
   cups-daemon (1.7.3-5 => 1.7.3-6)
   cups-ppdc (1.7.3-5 => 1.7.3-6)
   cups-server-common (1.7.3-5 => 1.7.3-6)
   e2fslibs (1.42.10-1 => 1.42.10-1.1)
   e2fsprogs (1.42.10-1 => 1.42.10-1.1)
   g++-4.8 (4.8.3-3 => 4.8.3-4)
   gcc-4.8 (4.8.3-3 => 4.8.3-4)
   gcc-4.8-base (4.8.3-3 => 4.8.3-4)
   libasan0 (4.8.3-3 => 4.8.3-4)
   libbluray1 (0.6.0+dfsg-1 => 0.6.0+dfsg-2)
   libcomerr2 (1.42.10-1 => 1.42.10-1.1)
   libcups2 (1.7.3-5 => 1.7.3-6)
   libcupscgi1 (1.7.3-5 => 1.7.3-6)
   libcupsimage2 (1.7.3-5 => 1.7.3-6)
   libcupsmime1 (1.7.3-5 => 1.7.3-6)
   libcupsppdc1 (1.7.3-5 => 1.7.3-6)
   libdata-perl-perl (0.002007-1 => 0.002009-1)
   libdb5.3 (5.3.28-4 => 5.3.28-5)
   libgcc-4.8-dev (4.8.3-3 => 4.8.3-4)
   libgdbm3 (1.8.3-12 => 1.8.3-12+b1)
   libgudev-1.0-0 (204-12 => 204-13)
   libmediastreamer-base3 (3.6.1-2.3 => 3.6.1-2.3+b1)
   libortp9 (3.6.1-2.3 => 3.6.1-2.3+b1)
   libpam-systemd (204-12 => 204-13)
   libss2 (1.42.10-1 => 1.42.10-1.1)
   libstdc++-4.8-dev (4.8.3-3 => 4.8.3-4)
   libsystemd-daemon0 (204-12 => 204-13)
   libsystemd-id128-0 (204-12 => 204-13)
   libsystemd-journal0 (204-12 => 204-13)
   libsystemd-login0 (204-12 => 204-13)
   libtasn1-6 (3.6-3 => 3.7-1)
   libudev1 (204-12 => 204-13)
   linux-image-3.15-1.towo.2-siduction-amd64 (3.15-5 => 3.15-7)
   linux-image-siduction-amd64 (3.15-5 => 3.15-8)
   po-debconf (1.0.16+nmu2 => 1.0.16+nmu3)
   systemd (204-12 => 204-13)
   systemd-sysv (204-12 => 204-13)
   udev (204-12 => 204-13)
   xserver-xorg-video-ati (7.3.0-1+b1 => 7.4.0-1)
   xserver-xorg-video-radeon (7.3.0-1+b1 => 7.4.0-1)
47 upgraded, 1 newly installed, 11 to remove and 14 not upgraded.

I have read Piper's thread of a few days ago, which also contains the libvtv0-package. Does anybody have the same problem , or solution, or do I just have to wait a few days?

Greetings,
Jörg

clubex

#1
After reading the following:
Quote
osdir.com/ml/general/2014-06/msg45524.html
I let the du remove libvtv0. If you need it then you need advice from someone more knowledgeable than me.








devil

Jörg, please look at the code of your post. Please use these code boxes next time as well. That makes lengthy output more readable.


greetz
devil

musca

Hello Jörg,

you can try to find (one of) the dependant packages with aptitude:

$ LANG=C aptitude why libvtv0
i   linux-headers-3.15-1.towo.2-siduction-amd64 Depends gcc-4.9
i A gcc-4.9                                     Depends libgcc-4.9-dev (>= 4.9.0-7)
i A libgcc-4.9-dev                              Depends libvtv0 (>= 4.9.0-7)


The new version 4.9.0-8 of libgcc-4.9-dev is not dependant of libvtv0 anymore, so you can let it go.

Setting libvtv0 on hold will prevent installing the kernel headers for your new kernel, so you cannot compile kernel modules for some drivers, especially the proprietary ones like nvidia, fglrx or virtualbox.

greetings
musca
,,Es irrt der Mensch, solang er strebt."  (Goethe, Faust)

Jörg

DU on 32-bit and 64-bit computers went well - thanks for your comment and help, clubex, devill & musca.
BTW, why the red X next to my thread, or how can I delete it?

Greetings,
Jörg

devil

We do not delete threads at all, we mark them done (by editing your headline in your starter post and adding [solved] in front of the headline. Deleting threads would destroy helpful knowledge for other users.


greetz
devil

Jörg

Hallo devil,

thanks for your answer, but my question is: how does it happen that my thread is the only one with the red X and what does it mean?

Greetings,
Jörg

ayla

One can delete his own posts for a limited time. If this time has ended the option vanishes.

Makes sence if any errors occur.

greets
ayla