Siduction Forum
Siduction Forum => Upgrade Warnings => Topic started by: melmarker on 2015/04/26, 16:02:27
-
and the first evil packages just landed in in sid
# LANG=C sudo apt dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be REMOVED:
python-samba samba samba-common-bin samba-dsdb-modules
samba-vfs-modules
The following packages have been kept back:
libflac8 libldb1 python-ldb vlc-data
The following packages will be upgraded:
bzr devscripts flac libasn1-8-heimdal libflac++6
libgssapi3-heimdal libhcrypto4-heimdal libhdb9-heimdal
libheimbase1-heimdal libheimntlm0-heimdal libhx509-5-heimdal
libkadm5clnt7-heimdal libkadm5srv8-heimdal libkafs0-heimdal
libkdc2-heimdal libkrb5-26-heimdal libotp0-heimdal
libroken18-heimdal libsl0-heimdal libtalloc2 libtevent0
libvisio-0.1-1 libwind0-heimdal links2 lynx lynx-cur
python-bzrlib python-ecdsa python-talloc python3-ecdsa usbview
vim vim-common vim-gtk vim-gui-common vim-runtime
36 upgraded, 0 newly installed, 5 to remove and 4 not upgraded.
Need to get 16.1 MB of archives.
After this operation, 20.8 MB disk space will be freed.
Do you want to continue? [Y/n] n
Abort.
So be prepared ...
-
I'm all good except for waiting for 32-bit version of libflac to hit the repo. Crank it up a notch!
-
Looks like the storm has arrived...be ready for a bumpy ride ;)
-
only a side note - we should eventually consider that it is clever to use the new apt wrapper instead of apt-get - only a thought. Standard behaviour of apt is --with-new-pkgs by default which could be helpful in situations like this - hmm, this trigger should be helpful allways.
-
One more side note, or question. If moderator want to move this to somewhere else, do that.
How safe is it to use apt-get upgrade instead of apt-get dist-upgrade when the later want to take away packages and the first put packages on hold and upgrade everything else?
dist-upgrade:
root@T420:/home/vilde# LANG=En 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:
gvfs-backends libsmbclient mplayer2 samba-libs smplayer
The following NEW packages will be installed:
libisl13 libx265-43
The following packages will be upgraded:
binutils libass5 libav-tools libavcodec56 libavdevice55 libavfilter5
libavformat56 libavresample2 libavutil54 libbluray1 libcloog-isl4
libdrm-intel1 libdrm-intel1:i386 libdrm-nouveau2 libdrm-nouveau2:i386
libdrm-radeon1 libdrm-radeon1:i386 libdrm2 libdrm2:i386 libdvbpsi9 libldb1
libswscale3 libtdb1 libteamdctl0 libva-drm1 libva-x11-1 libva1 va-driver-all
28 upgraded, 2 newly installed, 5 to remove and 0 not upgraded.
Need to get 10.2 MB of archives.
After this operation, 24.5 MB disk space will be freed.
Do you want to continue? [Y/n] n
Abort.
upgrade:
root@T420:/home/vilde# LANG=En apt-get upgrade -d
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
libavcodec56 libcloog-isl4 libldb1
The following packages will be upgraded:
binutils libass5 libav-tools libavdevice55 libavfilter5 libavformat56
libavresample2 libavutil54 libbluray1 libdrm-intel1 libdrm-intel1:i386
libdrm-nouveau2 libdrm-nouveau2:i386 libdrm-radeon1 libdrm-radeon1:i386
libdrm2 libdrm2:i386 libdvbpsi9 libswscale3 libtdb1 libteamdctl0 libva-drm1
libva-x11-1 libva1 va-driver-all
25 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
Need to get 5884 kB of archives.
After this operation, 134 kB disk space will be freed.
Do you want to continue? [Y/n] n
-
One more side note, or question. If moderator want to move this to somewhere else, do that.
How safe is it to use apt-get upgrade instead of apt-get dist-upgrade when the later want to take away packages and the first put packages on hold and upgrade everything else?
dist-upgrade:
root@T420:/home/vilde# LANG=En 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:
gvfs-backends libsmbclient mplayer2 samba-libs smplayer
The following NEW packages will be installed:
libisl13 libx265-43
The following packages will be upgraded:
binutils libass5 libav-tools libavcodec56 libavdevice55 libavfilter5
libavformat56 libavresample2 libavutil54 libbluray1 libcloog-isl4
libdrm-intel1 libdrm-intel1:i386 libdrm-nouveau2 libdrm-nouveau2:i386
libdrm-radeon1 libdrm-radeon1:i386 libdrm2 libdrm2:i386 libdvbpsi9 libldb1
libswscale3 libtdb1 libteamdctl0 libva-drm1 libva-x11-1 libva1 va-driver-all
28 upgraded, 2 newly installed, 5 to remove and 0 not upgraded.
Need to get 10.2 MB of archives.
After this operation, 24.5 MB disk space will be freed.
Do you want to continue? [Y/n] n
Abort.
upgrade:
root@T420:/home/vilde# LANG=En apt-get upgrade -d
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
libavcodec56 libcloog-isl4 libldb1
The following packages will be upgraded:
binutils libass5 libav-tools libavdevice55 libavfilter5 libavformat56
libavresample2 libavutil54 libbluray1 libdrm-intel1 libdrm-intel1:i386
libdrm-nouveau2 libdrm-nouveau2:i386 libdrm-radeon1 libdrm-radeon1:i386
libdrm2 libdrm2:i386 libdvbpsi9 libswscale3 libtdb1 libteamdctl0 libva-drm1
libva-x11-1 libva1 va-driver-all
25 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
Need to get 5884 kB of archives.
After this operation, 134 kB disk space will be freed.
Do you want to continue? [Y/n] n
Not really a good idea to use apt-get upgrade vis-a-vis apt-get dist-upgrade IMO so best to wait till the dust settles :)
-
How safe is it to use apt-get upgrade instead of apt-get dist-upgrade
It is probably safe enough, for awhile. But upgrade will not add new packages released by Debian for the core OS. So after some time of using only update, you don't have a Debian distribution any more. :'(
p.s. Bye-bye samba -- don't need it anymore, anyway.
-
How safe is it to use apt-get upgrade instead of apt-get dist-upgrade
It is probably safe enough, for awhile. But upgrade will not add new packages released by Debian for the core OS. So after some time of using only update, you don't have a Debian distribution any more. :'(
p.s. Bye-bye samba -- don't need it anymore, anyway.
A good reason to not make it a real habit to do only apt-get upgrade...too many things end up getting broken that way ;)
All I need is the samba client to access a Windows share really
-
Is waiting for a few days really such a big blocker??? Do any essential thing not work and must be fixed wihin a hour? NO? - Ok, wait a few days is the better idea.
Of course - one can learn a lot by messing up a system :D
-
same pc same time
apt-get dist-upgrade
apt-get[b]dist-upgrade
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
Paketaktualisierung (Upgrade) wird berechnet... Fertig
Die folgenden Pakete werden ENTFERNT:
python-samba samba samba-common-bin samba-dsdb-modules smbclient
Die folgenden NEUEN Pakete werden installiert:
libisl13
Die folgenden Pakete sind zurückgehalten worden:
libldb1 python-ldb
Die folgenden Pakete werden aktualisiert (Upgrade):
binutils clamav clamav-base clamav-docs clamav-freshclam devscripts ding libasn1-8-heimdal libass5 libav-tools libavcodec56
libavdevice55 libavfilter5 libavformat56 libavresample2 libavutil54 libbluray1 libclamav6 libcloog-isl4 libdrm-intel1 libdrm-intel1:i386
libdrm-nouveau2 libdrm-nouveau2:i386 libdrm-radeon1 libdrm-radeon1:i386 libdrm2 libdrm2:i386 libdvbpsi9 libflac++6 libflac8 libglib-perl
libgssapi3-heimdal libgtk2-perl libhcrypto4-heimdal libhdb9-heimdal libheimbase1-heimdal libheimntlm0-heimdal libhx509-5-heimdal
libkdc2-heimdal libkrb5-26-heimdal libmusicbrainz5-1 libroken18-heimdal libswscale3 libtalloc2 libtdb1 libteamdctl0 libtevent0
libva-drm1 libva-glx1 libva-x11-1 libva1 libvisio-0.1-1 libwind0-heimdal libwireshark-data libwireshark5 libwiretap4 libwsutil4
python-talloc python-tdb qlandkartegt-garmin tdb-tools trans-de-en vim vim-common vim-runtime wireshark wireshark-common
67 aktualisiert, 1 neu installiert, 5 zu entfernen und 2 nicht aktualisiert.
apt upgrade
apt upgrade
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
Paketaktualisierung (Upgrade) wird berechnet... Fertig
Die folgenden NEUEN Pakete werden installiert:
libisl13
Die folgenden Pakete sind zurückgehalten worden:
libldb1 python-ldb
Die folgenden Pakete werden aktualisiert (Upgrade):
binutils clamav clamav-base clamav-docs clamav-freshclam devscripts ding libasn1-8-heimdal libass5 libav-tools libavcodec56
libavdevice55 libavfilter5 libavformat56 libavresample2 libavutil54 libbluray1 libclamav6 libcloog-isl4 libdrm-intel1 libdrm-intel1:i386
libdrm-nouveau2 libdrm-nouveau2:i386 libdrm-radeon1 libdrm-radeon1:i386 libdrm2 libdrm2:i386 libdvbpsi9 libflac++6 libflac8 libglib-perl
libgssapi3-heimdal libgtk2-perl libhcrypto4-heimdal libhdb9-heimdal libheimbase1-heimdal libheimntlm0-heimdal libhx509-5-heimdal
libkdc2-heimdal libkrb5-26-heimdal libmusicbrainz5-1 libroken18-heimdal libswscale3 libtalloc2 libtdb1 libteamdctl0 libtevent0
libva-drm1 libva-glx1 libva-x11-1 libva1 libvisio-0.1-1 libwind0-heimdal libwireshark-data libwireshark5 libwiretap4 libwsutil4
python-talloc python-tdb qlandkartegt-garmin tdb-tools trans-de-en vim vim-common vim-runtime wireshark wireshark-common
67 aktualisiert, 1 neu installiert, 0 zu entfernen und 2 nicht aktualisiert.
-
Is waiting for a few days really such a big blocker??? Do any essential thing not work and must be fixed wihin a hour? NO? - Ok, wait a few days is the better idea.
Of course - one can learn a lot by messing up a system :D
I am in no hurry, my question was because apt-get upgrade was mentioned somewhere else for some time ago on the forum, I did react because as I remember we have always been told only to use apt-get dist-upgrade. Now I have got some clear answers about that and that's good.
Beside that I do mess up my system then and then, no big deal for me, I have my imported things saved and if I shall mess up a system totally siduction is the best to do that with. I have never had another os that can be installed and ready with my files and programs in so short time as siduction. ;)
-
(...) But upgrade will not add new packages released by Debian for the core OS. So after some time of using only update, you don't have a Debian distribution any more. :'( (...)
The wrapper 'apt' (instead of apt-get) has the switch --with-new-pkgs enabled by default, see man(8 ) apt -> Differences to apt-get. So:
Using 'apt-get upgrade' will work on upgradable packages, not remove anything, not install new ones.
Using ' apt upgrade ' will work on upgradable packages, not remove anything, but install new ones if necessary.
Therefore I mentioned the usage of apt upgrade somewhere else as a kind of workaround if one really needs it and cannot wait some days. However, and ever being true, to keep a Sid distro up and rolling the recommended way still is usage of apt-get dist-upgrade and brain. Everything else happens here in virtual machines only.
-
I was planning on installing Siduction Xorg. I guess with the recent Debian Stable release, I should probably sit tight for awhile until things settle down some.
-
Is waiting for a few days really such a big blocker???
Sometimes I use the following hack:
First I download only:
apt-get update; apt-get dist-upgrade -dy
If DU seems not appropriate, because something would get removed, I type
apt-get install -s
and copy only 1 line of the "apt-get -dy" output and append it to "apt-get install -s".
If output seems OK, I repeat this command, but without the "-s" flag.
Then I try again with the next line of "apt-get -dy" output until "apt-get install -s" finally says, it would remove something.
This procedure is cumbersome and error prone, because you might overlook important messages of " apt-get install -s".
But just not DUing, sometimes leaves me in unrest too :)
C
-
Not in a hurry, but curious what the opened gates of the hell will bring me, I get:
[13:03:12] root@thinkpad-s540:/home/jorg# apt-get dist-upgrade -dV
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
libisl13 (0.14-2)
libx265-43 (1.5-1)
The following packages will be upgraded:
binutils (2.25-6 => 2.25-7)
debianutils (4.4+b1 => 4.5)
libasn1-8-heimdal (1.6~rc2+dfsg-9 => 1.6~rc2+dfsg-10)
libass5 (0.10.2-3 => 0.12.1-2)
libav-tools (11.3-1 => 11.3-2)
libavcodec56 (11.3-1 => 11.3-2)
libavdevice55 (11.3-1 => 11.3-2)
libavfilter5 (11.3-1 => 11.3-2)
libavformat56 (11.3-1 => 11.3-2)
libavresample2 (11.3-1 => 11.3-2)
libavutil54 (11.3-1 => 11.3-2)
libbluray1 (0.6.2-1 => 0.7.0-2)
libcloog-isl4 (0.18.2-1+b2 => 0.18.3-1)
libdrm-intel1 (2.4.58-2 => 2.4.60-3)
libdrm-nouveau2 (2.4.58-2 => 2.4.60-3)
libdrm-radeon1 (2.4.58-2 => 2.4.60-3)
libdrm2 (2.4.58-2 => 2.4.60-3)
libdvbpsi9 (1.2.0-1 => 1.2.0-2)
libflac++6 (1.3.0-3 => 1.3.1-2)
libflac8 (1.3.0-3 => 1.3.1-2)
libgeoip1 (1.6.2-4 => 1.6.5-2)
libgssapi3-heimdal (1.6~rc2+dfsg-9 => 1.6~rc2+dfsg-10)
libharfbuzz-icu0 (0.9.35-2 => 0.9.40-2)
libharfbuzz0b (0.9.35-2 => 0.9.40-2)
libhcrypto4-heimdal (1.6~rc2+dfsg-9 => 1.6~rc2+dfsg-10)
libheimbase1-heimdal (1.6~rc2+dfsg-9 => 1.6~rc2+dfsg-10)
libheimntlm0-heimdal (1.6~rc2+dfsg-9 => 1.6~rc2+dfsg-10)
libhx509-5-heimdal (1.6~rc2+dfsg-9 => 1.6~rc2+dfsg-10)
libkrb5-26-heimdal (1.6~rc2+dfsg-9 => 1.6~rc2+dfsg-10)
libldb1 (1.1.17-2 => 1.1.20-1)
libmusicbrainz5-1 (5.1.0-2 => 5.1.0-3)
libp11-kit0 (0.20.7-1 => 0.23.1-2)
libpciaccess0 (0.13.2-3+b1 => 0.13.3-1)
libperl5.20 (5.20.2-3 => 5.20.2-4)
libroken18-heimdal (1.6~rc2+dfsg-9 => 1.6~rc2+dfsg-10)
libsmbclient (4.1.17+dfsg-2 => 4.1.17+dfsg-3)
libswscale3 (11.3-1 => 11.3-2)
libtalloc2 (2.1.1-2 => 2.1.2-3)
libtasn1-6 (4.2-3 => 4.4-3)
libtdb1 (1.3.4-1 => 1.3.4-2)
libteamdctl0 (1.12-2 => 1.17-1)
libtevent0 (0.9.22-1 => 0.9.24-1)
libupower-glib3 (0.99.1-3.2 => 0.99.2-3)
libva-drm1 (1.4.1-1 => 1.5.1-2)
libva-glx1 (1.4.1-1 => 1.5.1-2)
libva-x11-1 (1.4.1-1 => 1.5.1-2)
libva1 (1.4.1-1 => 1.5.1-2)
libvlc5 (2.2.0-1 => 2.2.1-1)
libvlccore8 (2.2.0-1 => 2.2.1-1)
libwbclient0 (4.1.17+dfsg-2 => 4.1.17+dfsg-3)
libwind0-heimdal (1.6~rc2+dfsg-9 => 1.6~rc2+dfsg-10)
libxdmcp6 (1.1.1-1+b1 => 1.1.2-1)
libxshmfence1 (1.1-4 => 1.2-1)
links (2.8-2+b3 => 2.9-3)
nmap (6.47-3+b1 => 6.47-4)
perl (5.20.2-3 => 5.20.2-4)
perl-base (5.20.2-3 => 5.20.2-4)
perl-modules (5.20.2-3 => 5.20.2-4)
python-talloc (2.1.1-2 => 2.1.2-3)
rkhunter (1.4.2-0.4 => 1.4.2-1)
samba-common (4.1.17+dfsg-2 => 4.1.17+dfsg-3)
samba-dsdb-modules (4.1.17+dfsg-2 => 4.1.17+dfsg-3)
samba-libs (4.1.17+dfsg-2 => 4.1.17+dfsg-3)
sed (4.2.2-4+b1 => 4.2.2-5)
tzdata (2015c-1 => 2015d-1)
upower (0.99.1-3.2 => 0.99.2-3)
vim (7.4.488-7 => 7.4.712-1)
vim-common (7.4.488-7 => 7.4.712-1)
vim-runtime (7.4.488-7 => 7.4.712-1)
vlc (2.2.0-1 => 2.2.1-1)
vlc-data (2.2.0-1 => 2.2.1-1)
vlc-nox (2.2.0-1 => 2.2.1-1)
vlc-plugin-pulse (2.2.0-1 => 2.2.1-1)
xkb-data (2.12-1 => 2.14-1)
xterm (312-2 => 318-2)
75 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 46.9 MB of archives.
That does look safe to me, but I am not absolutely sure ... what's your opinion!?
Greetings,
Jörg
-
When it says "0 to remove", it is normally safe. Of course with sid, there is always a small chance of a buggered new package coming in, but those don't normally damage the system.
-
I was planning on installing Siduction Xorg. I guess with the recent Debian Stable release, I should probably sit tight for awhile until things settle down some.
Just for fun, I tried that today, new installation, d-u, installed xfce, everything went bery smooth, no problem. but that was then, late, no onen knows
-
So far everything on gnome is smooth.
-
So far everything on gnome is smooth.
Now everyone is waiting for apt already telling us some packages get removed during d-u ... and someone not reading it ... 8)
-
Thank you for your support, Dibl! Made a backup first, then DU-ed and everything still worked allright.
Greetings,
Jörg
-
Hello,
I tried an d-u today, there were quite a bundle of kde-programs to be updated. But as there was quite a number also to be deinstalled I didn't carry it through and wait a some more time until this is settled.
Regards
Reiner
-
All went well here
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
libcmis-0.5-5 libisl13 libpagemaker-0.0-0 libqt5core5a libqt5dbus5 libqt5gui5 libqt5network5 libqt5script5 libqt5widgets5 libqt5xml5 libxcb-icccm4
libxcb-render-util0 libxcb-xkb1 libxkbcommon-x11-0
The following packages will be upgraded:
binutils clamav clamav-base clamav-freshclam console-setup console-setup-linux curl debianutils devscripts exfat-utils fonts-opensymbol i965-va-driver
inxi keyboard-configuration libabw-0.1-1 libasn1-8-heimdal libass5 libavdevice55 libcapture-tiny-perl libcdr-0.1-1 libclamav6 libcloog-isl4 libcurl3
libcurl3-gnutls libcurl4-openssl-dev libdrm-dev libdrm-dev:i386 libdrm-intel1 libdrm-intel1:i386 libdrm-nouveau2 libdrm-nouveau2:i386 libdrm-radeon1
libdrm-radeon1:i386 libdrm2 libdrm2:i386 libe-book-0.1-1 libevdev2 libflac++6 libflac8 libflac8:i386 libgeoip1 libgltf-0.0-0 libgssapi3-heimdal
libharfbuzz-dev libharfbuzz-gobject0 libharfbuzz-icu0 libharfbuzz0b libharfbuzz0b:i386 libhcrypto4-heimdal libheimbase1-heimdal libheimntlm0-heimdal
libhx509-5-heimdal libidn11 libkrb5-26-heimdal libldb1 libmspub-0.1-1 libmtp-common libmtp-runtime libmtp9 libmusicbrainz5-1 libmwaw-0.3-3
libmyth-0.27-0 libmythavcodec54 libmythavformat54 libmythavutil52 libmythpostproc52 libmythswresample0 libmythswscale2 libmythzmq1 libntlm0
libodfgen-0.1-1 libp11-kit0 libp11-kit0:i386 libpciaccess0 libpciaccess0:i386 libperl5.20 libreoffice-base libreoffice-base-core
libreoffice-base-drivers libreoffice-calc libreoffice-common libreoffice-core libreoffice-draw libreoffice-gnome libreoffice-gtk libreoffice-gtk3
libreoffice-help-de libreoffice-help-en-gb libreoffice-help-en-us libreoffice-help-it libreoffice-help-pl libreoffice-help-pt-br libreoffice-impress
libreoffice-kde libreoffice-l10n-de libreoffice-l10n-en-gb libreoffice-l10n-it libreoffice-l10n-pl libreoffice-l10n-pt-br libreoffice-l10n-ro
libreoffice-math libreoffice-report-builder-bin libreoffice-style-galaxy libreoffice-writer librevenge-0.0-0 libroken18-heimdal libsmbclient libtalloc2
libtasn1-6 libtasn1-6:i386 libtdb1 libteamdctl0 libtevent0 libupower-glib3 libva-drm1 libva-glx1 libva-x11-1 libva1 libvisio-0.1-1 libvlc5 libvlccore8
libwbclient0 libwind0-heimdal libwps-0.3-3 libxdmcp-dev libxdmcp-dev:i386 libxdmcp6 libxdmcp6:i386 libxshmfence-dev libxshmfence1 libxshmfence1:i386
links linux-libc-dev linux-libc-dev:i386 mythlogserver mythtv mythtv-backend mythtv-common mythtv-database mythtv-frontend mythtv-transcode nmap
openssh-client openssh-server openssh-sftp-server perl perl-base perl-modules php-mythtv python-ecdsa python-markdown python-mythtv python-talloc
python3-uno rkhunter samba-common samba-libs sed smplayer tzdata tzdata-java uno-libs3 upower ure va-driver-all vim vim-common vim-runtime vlc vlc-data
vlc-nox vlc-plugin-notify vlc-plugin-pulse wpasupplicant x11proto-core-dev x11proto-randr-dev xkb-data xterm
178 upgraded, 14 newly installed, 0 to remove and 0 not upgraded.
Need to get 44.3 MB/199 MB of archives.
-
And one more :)
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
libepsilon1 libfreexl1 libgnupg-interface-perl libgnutls-deb0-28 libgnutls-deb0-28:i386 libgnutls-openssl27 libkml0 libqt5core5a libqt5dbus5 libqt5gui5
libqt5network5 libqt5widgets5 libqt5xml5 libudisks2-0 mysql-workbench mysql-workbench-data mythweather python-six udisks2
19 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 21.1 MB of archives.
-
After reading through these posts, I updated my LXDE and Xfce, (both are 32bit) ...no problems after rebooting.
-
@dibl: Interesting...I know I've ok'd the removal of packages in the past, even under stable using the Backports repo, without experiencing any issues.
@vilde: Thank you for the info. I may go ahead and give it a try then. I plan on using Openbox and Tint2 as a desktop environment, similar to CrunchBang or the soon-to-be BunsenLabs Hydrogen. For the benefit of those who might be interested in setting up the same, check out this post (http://www.crunchbang.org/forums/viewtopic.php?id=38994) over at the CrunchBang/BunsenLabs forums.
@Millie: Great! I'm curious why you're using both LXDE and XFCE unless you're just trying both out.
-
@Millie: Great! I'm curious why you're using both LXDE and XFCE unless you're just trying both out.
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:
(http://thumbnails110.imagebam.com/39902/e67597399012082.jpg) (http://www.imagebam.com/image/e67597399012082)
(http://thumbnails110.imagebam.com/39578/4529bf395779254.jpg) (http://www.imagebam.com/image/4529bf395779254)
-
@dibl: Interesting...I know I've ok'd the removal of packages in the past, even under stable using the Backports repo, without experiencing any issues.
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.
-
@dibl
i have the same issue with kernel 3.19.*-towo.*-siduction-amd64 headers
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.1-siduction-amd64 linux-headers-3.19.3-towo.2-siduction-amd64 linux-headers-3.19.3-towo.3-siduction-amd64
The following NEW packages will be installed:
gcc-5-base libisl13 python-pbr
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
The following packages will be upgraded:
cpp-4.8 gcc-4.8 gcc-4.8-base libasan0 libatomic1 libcilkrts5 libcloog-isl4 libfreexl1 libgcc-4.8-dev libgfortran3 libglyr1 libgomp1 libitm1 liblsan0 libquadmath0
libtsan0 libubsan0 libxml-libxml-perl python-stevedore
19 upgraded, 3 newly installed, 3 to remove and 14 not upgraded.
Need to get 12.8 MB/13.3 MB of archives.
After this operation, 95.0 MB disk space will be freed.
Do you want to continue? [Y/n] n
Abort.
have not pressed enter yet, i fear that when i will need header files for compiling in the future something else will want to uninstall..i was wondering which package is responsible for this..[ i am not using kernel 4 since i want nvidia driver 346 for now]
any thoughts?
----
i have made only selective upgrades so far with install --only-upgrade
-
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.
-
Just made a D-U all solid here.
-
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
-
It's a typical multiarch "issue", it will happen now often, since the freeze is over.
-
@towo
thanks, good to kwow..
because autoremove wants to uninstall them again :P
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..
-
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
uname -a
dpkg -l | egrep "linux-image|linux-headers"
-
yes i am using this kernel
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
-
I get
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?
-
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.
-
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:
(http://thumbnails110.imagebam.com/39902/e67597399012082.jpg) (http://www.imagebam.com/image/e67597399012082)
(http://thumbnails110.imagebam.com/39578/4529bf395779254.jpg) (http://www.imagebam.com/image/4529bf395779254)
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.
-
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.
-
@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.
-
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...
-
Just applied updates today about 200+ nothing removed so far so good.