Multiarch dist-upgrade should wait ;)
The following packages will be REMOVED:
g++-4.9-multilib g++-multilib gcc-4.9-multilib gcc-multilib libx32stdc++-4.9-dev linux-headers-3.15-8.towo-siduction-amd64
linux-headers-3.16-0.towo-siduction-amd64 linux-headers-siduction-amd64
The following NEW packages will be installed:
libabw-0.1-1 libcdr-0.1-1 libe-book-0.1-1 libetonyek-0.1-1 libfreehand-0.1-1 libjim0.75 libmspub-0.1-1 libmwaw-0.3-3 libodfgen-0.1-1
liborcus-0.8-0 librevenge-0.0-0 libvisio-0.1-1 libwpd-0.10-10 libwpg-0.3-3 libwps-0.3-3
The following packages have been kept back:
cpp-4.9 g++-4.9 gcc-4.9 gcc-4.9-base lib32asan1 lib32atomic1 lib32cilkrts5 lib32gcc-4.9-dev lib32gcc1 lib32gomp1 lib32itm1 lib32quadmath0
lib32stdc++-4.9-dev lib32stdc++6 lib32ubsan0 libasan1 libatomic1 libcilkrts5 libgcc-4.9-dev libgcc1 libgfortran3 libgomp1 libitm1 liblsan0
libquadmath0 libstdc++-4.9-dev libstdc++6 libtsan0 libubsan0 libx32asan1 libx32atomic1 libx32cilkrts5 libx32gcc-4.9-dev libx32gcc1
libx32gomp1 libx32itm1 libx32quadmath0 libx32stdc++6 libx32ubsan0
The following packages will be upgraded:
acpi-fakekey acpi-support acpi-support-base aspell binutils cmake cmake-data console-setup console-setup-linux debhelper devscripts
distro-defaults fonts-opensymbol ghostscript ghostscript-x git git-core git-gui git-man git-svn gnupg-agent gnupg2 initscripts iproute
iproute2 keyboard-configuration libaspell15 libavdevice54 libavutil53 libbluray1 libdatetime-timezone-perl libestr0 libexiv2-12
libfreerdp1 libfreetype6 libfreetype6:i386 libgcrypt11 libgcrypt11:i386 libgd3 libgd3:i386 libgpg-error0 libgpg-error0:i386 libgpgme11
libgps21 libgs9 libgs9-common libgssapi-krb5-2 libgudev-1.0-0 libharfbuzz-icu0 libharfbuzz0b libio-socket-ssl-perl libk5crypto3
libkactivities-bin libkactivities-models1 libkactivities6 libkrb5-3 libkrb5support0 libkscreen1 liblapack3 liblcms1 libllvm3.4
libllvm3.4:i386 liblqr-1-0 libmng1 libmpg123-0 libmpg123-0:i386 libopts25 libossp-uuid-perl libossp-uuid16 libp11-kit0 libp11-kit0:i386
libpam-systemd libparted-fs-resize0 libparted2 libpulse-mainloop-glib0 libpulse0 libqmi-glib1 libqmi-proxy libreadline6
libreoffice-base-core libreoffice-calc libreoffice-common libreoffice-core libreoffice-draw libreoffice-impress libreoffice-kde
libreoffice-math libreoffice-style-galaxy libreoffice-writer libschroedinger-1.0-0 libssl1.0.0 libsystemd-daemon0 libsystemd-id128-0
libsystemd-journal0 libsystemd-login0 libtidy-0.99-0 libudev1 libudev1:i386 libunistring0 liburiparser1 libvpx1 libvpx1:i386 libyaml-perl
libzip2 linux-libc-dev mpg123 openssh-client openssh-server openssh-sftp-server openssl parted python-wstools readline-common rsync
siduction-dynamic-dms siduction-settings-kde-paintitblack siduction-settings-lightdm-gtk-paintitblack steam:i386 systemd systemd-sysv
sysv-rc sysvinit sysvinit-utils tzdata tzdata-java udev uno-libs3 ure usb-modeswitch xsane xsane-common
131 upgraded, 15 newly installed, 8 to remove and 39 not upgraded
Piper, I'm new to using forums and siduction so bare with me. I was also under the impression that multiarch was a standard lib in debian compatible to all systems, so correct me if I wrong please. I just performed a d-u on 2 units and experienced no problems. So either my systems doesn't use multiarch, or it does and everything went well, thanks to all the contributors at siduction! :)
Multiarch is not automatically installed -- you have to choose to add it to the original architecture that you installed. Here (https://wiki.debian.org/Multiarch/HOWTO) is the wiki.
This happens very frequently. The 32-bit version of gcc always reaches the mirrors after the 64-bit version, and headers depend on gcc-x.x
If the issue cannot be permanently resolved by altering the headers' dependency on gcc (depend on build-essential?), I still suggest a sticky on the issue (replacing the outdated lxdenext sticky).
If, for some reason, it is important to get the d-u done in the moment (I don't know why, but it could be), then you can go ahead with it, and then you can simply reinstall the headers packages that you require. I've done that a couple of times, just out of curiosity, and it has always worked to put the system back as it it should be.
Quote from: seasonsThis happens very frequently. The 32-bit version of gcc always reaches the mirrors after the 64-bit version, and headers depend on gcc-x.x
If the issue cannot be permanently resolved by altering the headers' dependency on gcc (depend on build-essential?), I still suggest a sticky on the issue (replacing the outdated lxdenext sticky).
Well, it's *usually* fixed within a day or two, no rush ever on a du, patience is a virtue, and if in a hurry to do a du, stable might be a
better idea
no one should be in hurry, if planning to do a d-u. But wait. -- Hurry. This means not tested software, roll out when it compiles - omfg - that pretty much describes the way we work .... 8)
All is good again :)
perhaps next week ;)
Quote from: dibl on 2014/08/10, 12:25:39
Multiarch is not automatically installed -- you have to choose to add it to the original architecture that you installed. Here (https://wiki.debian.org/Multiarch/HOWTO) is the wiki.
Thanks Dibl for the clarification as I said I was under the impression that it came with my normal installation and then the upgrades, appreciate the feedback.