Siduction Forum
Siduction Forum => Upgrade Warnings => Topic started by: terroreek on 2014/05/23, 15:20:58
-
I was getting the same thing last night as I am this morning. Becareful performing a d-u.
The following packages will be REMOVED:
linux-headers-3.13-5.towo-siduction-amd64
linux-headers-3.13-5.towo.2-siduction-amd64
linux-headers-3.13-6.towo-siduction-amd64
linux-headers-3.13-7.towo-siduction-amd64
linux-headers-3.14-0.towo.3-siduction-amd64
linux-headers-3.14-0.towo.4-siduction-amd64
linux-headers-3.14-1.towo-siduction-amd64
linux-headers-3.14-2.towo-siduction-amd64
linux-headers-3.14-3.towo-siduction-amd64
linux-headers-3.14-3.towo.2-siduction-amd64
linux-headers-3.14-4.towo-siduction-amd64 linux-headers-siduction-amd64
The following packages have been kept back:
cpp-4.8 g++-4.8 gcc-4.8 gcc-4.8-base libasan0 libgcc-4.8-dev
libstdc++-4.8-dev
EDITed from bluelupo: Set code-tags
-
Here ist it ok.
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
Paketaktualisierung (Upgrade) wird berechnet... Fertig
Die folgenden Pakete werden aktualisiert (Upgrade):
cdbs cpp-4.8 curl foomatic-db-gutenprint g++-4.8 gcc-4.8 gcc-4.8-base git
git-man ijsgutenprint kdegames-mahjongg-data kgamma kolourpaint4 libasan0
libcurl3 libcurl3-gnutls libcurses-perl libgcc-4.8-dev libgcj14 libglib-perl
libgutenprint2 libimage-exiftool-perl libkate1 libkdcraw-data libkdcraw23
libkipi-data libkipi11 libkmahjongglib4 libpolkit-agent-1-0
libpolkit-backend-1-0 libpolkit-gobject-1-0 libpython2.7
libpython2.7-minimal libpython2.7-stdlib libsox-fmt-all libsox-fmt-alsa
libsox-fmt-ao libsox-fmt-base libsox-fmt-mp3 libsox-fmt-oss libsox-fmt-pulse
libsox2 libstdc++-4.8-dev libvorbis0a libvorbisenc2 libvorbisfile3
policykit-1 printer-driver-gutenprint python-chardet python-pkg-resources
python2.7 python2.7-minimal sox
53 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
Es müssen 49,4 MB an Archiven heruntergeladen werden.
Nach dieser Operation werden 572 kB Plattenplatz zusätzlich benutzt.
Möchten Sie fortfahren? [J/n] n
Abbruch.
-
Still getting the problem on my another machine, my guess is the NA repos haven't synced.
-
I was getting the same thing last night as I am this morning. Becareful performing a d-u.
terroreek, how is this situation for you now? I'm having a very similar situation:
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:
gccxml gobjc gobjc-4.8 linux-headers-3.13-6.towo-siduction-amd64
linux-headers-3.13-7.towo-siduction-amd64
linux-headers-3.14-1.towo-siduction-amd64
linux-headers-3.14-3.towo-siduction-amd64
linux-headers-3.14-4.towo-siduction-amd64 linux-headers-siduction-amd64
The following packages have been kept back:
cpp-4.8 g++-4.8 gcc-4.8 gcc-4.8-base gcc-4.9-base jitsi libasan0 libatomic1
libgcc-4.8-dev libgcc1 libgfortran3 libgomp1 libitm1 libobjc-4.8-dev
libobjc4 libquadmath0 libstdc++-4.8-dev libstdc++6 libtsan0
-
just wait a day - doko (the maintainer of gcc) is doing his work - and if i386 is in the repos you will get a new and shiny build of gcc - until then: Don't do a d-u unless you know exactly what you doing.
And please: This will happend about 10 to 20 times in the year. Try to remind this behavior, doko give a shit about breaking any installations - and he's right with this.
-
I was getting the same thing last night as I am this morning. Becareful performing a d-u.
terroreek, how is this situation for you now? I'm having a very similar situation:
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:
gccxml gobjc gobjc-4.8 linux-headers-3.13-6.towo-siduction-amd64
linux-headers-3.13-7.towo-siduction-amd64
linux-headers-3.14-1.towo-siduction-amd64
linux-headers-3.14-3.towo-siduction-amd64
linux-headers-3.14-4.towo-siduction-amd64 linux-headers-siduction-amd64
The following packages have been kept back:
cpp-4.8 g++-4.8 gcc-4.8 gcc-4.8-base gcc-4.9-base jitsi libasan0 libatomic1
libgcc-4.8-dev libgcc1 libgfortran3 libgomp1 libitm1 libobjc-4.8-dev
libobjc4 libquadmath0 libstdc++-4.8-dev libstdc++6 libtsan0
It was fine a couple of days ago and upgraded then, but I am getting the same thing today as you are. I would do what melmarker suggests keep looking at what d-u wants to do and wait until it doesn't want to remove the headers.
-
@melmarker: you should probably make a quick sticky about it (and lose the lxdenext sticky since siduction moved to lxqt now).
64-bit users with multiarch often encounter this issue.
-
Who says that LXDE is abandoned - not in nearer future. LXDE is atm a mature product that is in active development - and LXQt try to reach the stable and usable status :)
Edit: But you are right, we should make a sticky about updating multiarch - its not only gcc which try to destroy systems.
-
I didn't say lxde was abandoned. I was referring to your sticky about lxdenext repo being closed...
-
the reason for closing lxdenext is: the packages are now in extra, one step in the direction nearly unified repository - a separated repository for lxde, lxqt and razorqt doesn't make sense anymore. there will be a lxqt repository with builds against pure sid, which contain lxqt and razorqt packages for usage outside of siduction.
-
^Yeah, I understand that. I was just saying you don't need a sticky from 4 months ago announcing that you closed a repo (because the number of stickies is inversely proportional to the chance that people will read them...).
A warning for multiarch users that apt may want to remove kernel headers in the middle of a gcc upgrade would be a more useful sticky IMO.
-
and again - a sticky about kernel header removal would last forever - aka nobody read this sticky after a while - and btw - there is nothing wrong with the removal - except the very rare case, that one use non-free programs like virtualbox or some drivers 8)
This special breakage will come up with every gcc update so it would be sufficient to write a simple upgrade warning when it occurs - this will be better than a sticky. The point is: People need to read and understand the output of apt, if one is not willing or to lazy to read and understand i suggest a cron-job:
5,11,17,23 * * * * root /usr/bin/apt update && /usr/bin/apt dist-upgrade --assume-yes
-
just wait a day - doko (the maintainer of gcc) is doing his work - and if i386 is in the repos you will get a new and shiny build of gcc - until then: Don't do a d-u unless you know exactly what you doing.
And please: This will happend about 10 to 20 times in the year. Try to remind this behavior, doko give a shit about breaking any installations - and he's right with this.
All cleared up for me today, gcc and much more upgraded nothing removed or held back. Thanks, for your help. I especially appreciate the process overview insights.