Siduction Forum

Siduction Forum => Upgrade Warnings (DE / EN) => Topic started by: Santa on 2015/07/30, 13:18:42

Title: [closed] Large GCC-5 TRANSITION, Heavy DIST-UPGRADE pending
Post by: Santa on 2015/07/30, 13:18:42
Hi,


it's expected that tomorrow the default compiler for debian sid will be GCC 5
https://lists.debian.org/debian-devel-announce/2015/07/msg00000.html (https://lists.debian.org/debian-devel-announce/2015/07/msg00000.html)


in the pack comes a new standard library for C++ with a different ABI, this technical detail is going to make this transition particularly harder than other transitions.


Regarding KDE packaging I have been working with a person from debian and kubuntu's people to make the dist-upgrades safe as soon as possible. If you are interested in the technical details I made a few slides to sum up the KDE situation here at the "Akademy" (https://akademy.kde.org/ (https://akademy.kde.org/)):
https://gitlab.com/jmsantamaria-papers/gcc5_the_apocalypse (https://gitlab.com/jmsantamaria-papers/gcc5_the_apocalypse)


What to do to "survive gracefully":


Do NOT dist-upgrade after July 31 until you find here further instructions, we will keep you posted.

Title: Re: [URGENT] GCC 5 fallout incoming
Post by: der_bud on 2015/07/30, 13:32:40
Short german translation  //  Kurze Übersetzung ins Deutsche

ab morgen wird in Debian Sid GCC5 als Defaultcompiler erwartet, siehe https://lists.debian.org/debian-devel-announce/2015/07/msg00000.html

Neue Standardbibliotheken für C++ mit anderer ABI kommen da mit, damit wird diese Transition schwieriger als Andere.

Santa hat mit Kollegen von Debian und Kubuntu einen möglichst einfachen Übergang für uns vorbereitet, aber ganz ohne wird das trotzdem nicht. Ein paar Details dazu in der "Akademy (https://akademy.kde.org/)":  https://gitlab.com/jmsantamaria-papers/gcc5_the_apocalypse

Momentaner Rat:
Ab 31 July NICHT DIST-UPGRADEN solange hier keine Entwarnung oder weitere Hinweise kommen!
Title: Re: [URGENT] GCC 5 fallout incoming
Post by: jjjrrr3 on 2015/07/30, 20:27:53
What to do to "survive gracefully":


Do NOT dist-upgrade after July 31 until you find here further instructions, we will keep you posted.

Do not dist-upgrade after July 31 at all or do not dist-upgrade after July 31 if I use GCC?
Title: Re: [URGENT] GCC 5 fallout incoming
Post by: Santa on 2015/07/30, 20:30:18

What to do to "survive gracefully":


Do NOT dist-upgrade after July 31 until you find here further instructions, we will keep you posted.

Do not dist-upgrade after July 31 at all or do not dist-upgrade after July 31 if I use GCC?


At all.
Title: Re: [URGENT] GCC 5 fallout incoming
Post by: ralul on 2015/07/31, 13:16:28
Do not dist-upgrade after July 31 at all or do not dist-upgrade after July 31 if I use GCC?
@jjjrrr3
All of C++ code must be recompiled with GCC-5 using of the new C++ 2011 standards. The old libs won't provide what new compiled programs expect and vice versa.
Just give it the time to compile fully.
@my question: Is this also the case for packages using pure C but not C++ code?
Title: Re: [URGENT] GCC 5 fallout incoming
Post by: tux on 2015/07/31, 16:43:39
Do not dist-upgrade after July 31 at all or do not dist-upgrade after July 31 if I use GCC?
@jjjrrr3
All of C++ code must be recompiled with GCC-5 using of the new C++ 2011 standards. The old libs won't provide what new compiled programs expect and vice versa.
Just give it the time to compile fully.
@my question: Is this also the case for packages using pure C but not C++ code?
If it compiled with GCC.
Title: Re: [URGENT] GCC 5 fallout incoming
Post by: Santa on 2015/07/31, 18:07:48
@my question: Is this also the case for packages using pure C but not C++ code?


No, it's not the case for pure C programs.
The ABI breakage is in libstdc++, so programs not linked against libstdc++ (i.e. written completely in C) don't need to be rebuilt.
Title: Re: [URGENT] GCC 5 fallout incoming
Post by: ralul on 2015/07/31, 18:20:59
If it compiled with GCC.
No, it is about the adoption of the new C++ version:
https://en.wikipedia.org/wiki/C%2B%2B11
No matter what compiler (if the compiler does the upgrade in C++ standards)
Title: Re: [URGENT] GCC 5 fallout incoming
Post by: holgerw on 2015/08/02, 11:43:25
Hello,

what does this mean for fresh siduction installations? I've a Nox with current stuff from 28.07.2015. Will I run into issues when taking this iso for new installations and adding X, kf5, lxqt and further software?

Kind regards,
  Holger
Title: Re: [URGENT] GCC 5 fallout incoming
Post by: devil on 2015/08/02, 12:29:32
You might run into problems installing certain softwares. Kdepim and LO are affected, but also many more. So your milage may vary during this period.


greetz
devil
Title: Re: [URGENT] GCC 5 fallout incoming
Post by: Santa on 2015/08/02, 13:02:08

Hi Holger,

Hello,

what does this mean for fresh siduction installations? I've a Nox with current stuff from 28.07.2015. Will I run into issues when taking this iso for new installations and adding X, kf5, lxqt and further software?

Kind regards,
  Holger


indeed, like devil said you may or may not have problems with C++ software. We are swimming into the randomness, it's a russian roulette. I'm a bit busy right now but if I find some time I will try to explain you the technical details in a way you can understand how this russian roulette works.


I have checked yesterday that, at least, Plasma 5 starts with the new standard C++ library. If you have some free time and you want to help us, one thing you can do is:
For each siduction flavour providing a desktop environment:
- Do a fresh installation from the indiansumer iso
- Dist-upgrade and make sure you have the latest libstdc++6 package
- Check if the desktop environment in question starts
- Optionally check if programs which you consider important for every day use (like dolphin and konsole in the kde flavour) start


If you get any program refusing to start and saying somthing like "symbol lookup error" please tell me as soon as you can and I will see what can I do.


Cheers.
Title: Re: [URGENT] GCC 5 fallout incoming
Post by: devil on 2015/08/02, 15:02:27
Yeah, building all the flavours and testing them in the described way makes sense. This issue will not last for days but for weeks.


greetz
devil

Title: Re: [URGENT] GCC 5 fallout incoming
Post by: DeepDayze on 2015/08/02, 16:25:34
Yeah, building all the flavours and testing them in the described way makes sense. This issue will not last for days but for weeks.


greetz
devil

So then the best thing is to just sit tight until all the packages have been rebuilt?
Title: Re: [URGENT] GCC 5 fallout incoming
Post by: Santa on 2015/08/02, 16:29:57
Yeah, building all the flavours and testing them in the described way makes sense. This issue will not last for days but for weeks.


greetz
devil

So then the best thing is to just sit tight until all the packages have been rebuilt?


Until further advice as I said in the first post, we are working on this to make it as painless as possible.
Title: Re: [URGENT] GCC 5 fallout incoming
Post by: dibl on 2015/08/02, 17:21:47
If you look at all the affected packages down the left column of this page (https://release.debian.org/transitions/html/libstdc++6.html), and then look at the list of collisions at the bottom, you can get an idea of the size and scope of the job to make the complete transition.
Title: Re: [URGENT] GCC 5 fallout incoming
Post by: holgerw on 2015/08/02, 20:50:18
Hello @Santa, hello @devil,

I fetch siduction flavours of lxde, lxqt, kde and xfce in Version indiansummer amd64 now. Tomorrow I'll start with testing lxde, then lxqt, then kde and then xfce, the steps for each flavour will be following:
1. Installing flavour xxx-indiansumer amd64
2. Trying to make dist-upgrade
3. Trying to add some stuff like libreoffice, claws-mail and audacity
4. Testing, if base apps work (Filemanager, Texteditor, libreoffice, mailprogramm, browser)

I'll report the results.

Kind regards,
  Holger
Title: Re: [URGENT] GCC 5 fallout incoming
Post by: devil on 2015/08/02, 21:14:38
Sounds like a good workflow.


greetz
devil
Title: Re: [URGENT] GCC 5 fallout incoming
Post by: ralul on 2015/08/02, 23:40:11
Do we have lost all of Debian sid for the next half year?
if it takes the time as in Gentoo, e.g.:
https://bugs.gentoo.org/show_bug.cgi?id=548784#c13
:(
Title: Re: [URGENT] GCC 5 fallout incoming
Post by: ghstryder on 2015/08/02, 23:57:43
If you look at all the affected packages down the left column of this page (https://release.debian.org/transitions/html/libstdc++6.html), and then look at the list of collisions at the bottom, you can get an idea of the size and scope of the job to make the complete transition.
That is an extensive list. Wow... Thanks for tracking that down. It really underscores Devil's comment about it not being a short-lived problem.
Title: Re: [URGENT] GCC 5 fallout incoming
Post by: melmarker on 2015/08/03, 01:39:53
a sufficient amount of popcorn and beer will help a lot in the next days :)
Title: Re: [URGENT] GCC 5 fallout incoming
Post by: holgerw on 2015/08/03, 07:43:02
Hello,
I think, during this period a Debian Jessie can be an alternative tool for working with a computer.


Kind regards, Holger
Title: Re: [URGENT] GCC 5 fallout incoming
Post by: devil on 2015/08/03, 09:43:46
What is wrong with a sid/siduction install that you just don't upgrade for the time being?


greetz
devil
Title: Re: [URGENT] GCC 5 fallout incoming
Post by: drb on 2015/08/03, 10:56:15
The main issue here would be lack of libreoffice. Justing waiting . . . .
Title: Re: [URGENT] GCC 5 fallout incoming
Post by: terroreek on 2015/08/03, 13:37:45
its not just libre office, right now gnome-shell and other parts of gnome want to be removed as well. 
Title: Re: [URGENT] GCC 5 fallout incoming
Post by: tux on 2015/08/03, 23:40:19
What is wrong with a sid/siduction install that you just don't upgrade for the time being?
We need install security updates at least.
Title: Re: [URGENT] GCC 5 fallout incoming
Post by: melmarker on 2015/08/03, 23:42:50
oha - do you mean the things from http://security.debian.org sid main contrib non-free ?
Title: Re: [URGENT] GCC 5 fallout incoming
Post by: holgerw on 2015/08/03, 23:49:50
What is wrong with a sid/siduction install that you just don't upgrade for the time being?


greetz
devil

Hello Ferdinand,

I refer to Debian Stable for such situations, when something happens during a dist-upgrade, which breaks the installed siduction system.

Kind regards,
  Holger
Title: Re: [URGENT] GCC 5 fallout incoming
Post by: melmarker on 2015/08/03, 23:59:03
there are four possible ways in such situations:
Code: [Select]
1.   doing nothing (prefered)
2.1. apt update; apt upgrade
2.2  apt-get update; apt-get upgrade --with-new-pkgs
3.   apt-get dist-upgrade (and lettings some packages go)

We suggest and prefer 1! If one choose a way that differ from (1) one should have a good backup and should be familar with restoring from backups. We will not support that, so you are on your own. But it may work without flaws.
Title: Re: [URGENT] GCC 5 fallout incoming
Post by: piper on 2015/08/04, 01:17:18
Quote from: melmarker
there are four possible ways in such situations:
Code: [Select] (http://javascript:void(0);)1.   doing nothing (prefered)
2.1. apt update; apt upgrade
2.2  apt-get update; apt-get upgrade --with-new-pkgs
3.   apt-get dist-upgrade (and lettings some packages go)

We suggest and prefer 1! If one choose a way that differ from (1) one should have a good backup and should be familar with restoring from backups. We will not support that, so you are on your own. But it may work without flaws.

+1

I agree with 1, doing nothing

119 upgraded, 21 newly installed, 13 to remove and 0 not upgraded.
Need to get 201 MB of archives.
After this operation, 160 MB of additional disk space will be used.

It is early yet, probably get worse after a few days.
Title: Re: [URGENT] GCC 5 fallout incoming
Post by: melmarker on 2015/08/04, 01:25:22
@piper: i think we communicate our position very clear - but every user is free to do what $user want to. Depending on the installed packages things could become worse or not - nobody knows. I for myself has decided to not care about and take the packages as they come in. And i have no backup. So who cares - one should take a choice and have to live with this choice afterwards. As we are all more or less  responsible adults i see no problem ... :)
Title: Re: [URGENT] GCC 5 fallout incoming
Post by: piper on 2015/08/04, 01:32:17
Quote from: melmarker
@piper: i think we communicate our position very clear - but every user is free to do what $user want to. Depending on the installed packages things could become worse or not - nobody knows. I for myself has decided to not care about and take the packages as they come in. And i have no backup. So who cares - one should take a choice and have to live with this choice afterwards. As we are all more or less  responsible adults i see no problem ... (http://forum.siduction.org/Smileys/default/smiley.gif)
I agree, choice is good and up to the user, I just don't encourage it due to not everyone can fix or afford to lose some things ;)

I have a 3-4 extra partitions with siduction running and doing du's to see when/if  this brings one  box to it's knee's, so far, all is good, I too don't have back-ups. who need stinkin backups :)

Happy du'ing ;)
Title: Re: [URGENT] GCC 5 fallout incoming
Post by: terroreek on 2015/08/04, 05:05:47
So quick question, normally I du daily on my siduction boxes, however the last DU I did was back on the 25th.  I was out of town on work until the 2nd.  Would you recommend I still wait, or do an apt-get upgrade.  I never upgrade just dist-upgrade. 
Title: Re: [URGENT] GCC 5 fallout incoming
Post by: der_bud on 2015/08/04, 08:00:18
Of course we all here driving sid love to have all possible software in the newest available version, but do we really need it?
If there are are some tools you urgently need which are not working in the current version, but will do with an update, or an update brings features you can not do without, try to update those packages or try an upgrade/safe-upgrade.
But what is wrong on a reliable working machine to be in the state of mid July 2015, that is very current (see, people still run Win XP ;)). I merged to KF5 and did dist-upgrades recently in virtual machines and playboxes, but my main notebook has not seen dist-upgrades since plasma5 came in, some cherry-picked package updates only. And guess what - it is working fine. One drawback could be 'no security updates since ~ one month', but wait... are there security updates (https://www.debian.org/security/faq#unstable) in Sid (https://www.debian.org/releases/sid/)?

So still true: Question
... Would you recommend I still wait, or do an apt-get upgrade. ...

Answer
there are four possible ways in such situations:
Code: [Select]
1.   doing nothing (prefered)
2.1. apt update; apt upgrade
2.2  apt-get update; apt-get upgrade --with-new-pkgs
3.   apt-get dist-upgrade (and lettings some packages go)

We suggest and prefer 1! If one choose a way that differ from (1) one should have a good backup and should be familar with restoring from backups. We will not support that, so you are on your own. But it may work without flaws.



Title: Re: [URGENT] GCC 5 fallout incoming
Post by: tmhind2 on 2015/08/04, 09:31:54
What part of "DO NOTHING NOW" is so hard to understand? Though I've only been using Siduction a short while and have made my mistakes in the past, one thing I have learned is to respect the guidance provided from the pro's.  Thanks to all that are doing everything possible now and in the past in making this the great distribution it is!!!  :)


Respectfully,
T2
Title: Re: [URGENT] GCC 5 fallout incoming
Post by: jdhedden on 2015/08/09, 05:12:32
FWIW, I was bored and decided to try a DU.  Around 115 packages updated.  Rebooted okay.  VLC works, and other things as well.  I'll continue with this to see how it goes.
Title: Re: [URGENT] GCC 5 fallout incoming
Post by: drb on 2015/08/09, 10:15:59
I'm up to 59 packages to remove now . . . .
Title: Re: [URGENT] GCC 5 fallout incoming
Post by: melmarker on 2015/08/09, 12:06:42
@jdhedden: Not sure if you miss a thing - a update will ever work, mostly the system works after. But there is i really big BUT. One example for today is audacious - it upgrades audacious-plugins and the new v5 lib - after that audacious segfaults. So the upgrade might work ok, but it can break things (and Murphy says: it will break things)

EDIT: i hope you use apt upgrade instead of apt-get upgrade, see the reason some posts ago
Title: Re: [URGENT] GCC 5 fallout incoming
Post by: jdhedden on 2015/08/09, 13:14:56
@melmake  Understood.  I do have a Clonezilla backup in case I have issues.   Also, I use the "upgrade-system" package for updates.


To all, I classify myself as having a "lean" system, so of course, you mileage may vary.
Title: Re: [URGENT] GCC 5 fallout incoming
Post by: KrunchTime on 2015/08/09, 22:25:31
If you look at all the affected packages down the left column of this page (https://release.debian.org/transitions/html/libstdc++6.html), and then look at the list of collisions at the bottom, you can get an idea of the size and scope of the job to make the complete transition.
Thank you for sharing this, dibl.  A picture is worth a thousand words.  ;)


@melmarker:  Thank you for sharing the guidance.
Title: Re: [URGENT] GCC 5 fallout incoming
Post by: Spike_DE on 2015/08/09, 22:32:09
148 updated, 2 newly installed, 199 to remove and 74 not updated.

:-(
Title: Re: [URGENT] GCC 5 fallout incoming
Post by: piper on 2015/08/10, 04:59:39
121 upgraded, 0 newly installed, 396 to remove and 86 not upgraded :)
Title: Re: [URGENT] GCC 5 fallout incoming
Post by: musca on 2015/08/10, 12:12:45
Hello,

while KDE systems (without kdenext) suffer from heavy removals, the situation was much better on my cinnamon system this morning. When i realized that dist-upgrade only wants to remove some libs but no applications, i took a closer look at it (see http://paste.siduction.org/20150810095149.png ). I went through the whole list and found that every removed lib was covered by some *v5 replacement.  Overall statistics:
Code: [Select]
286 upgraded, 36 newly installed, 17 to remove and 0 not upgraded.
So i tried a dist-upgrade and got a working cinnamon desktop for my very limited personal package selection.

Beware! This doesn't apply for KDE systems.

greetings
musca
Title: Re: [URGENT] GCC 5 fallout incoming
Post by: piper on 2015/08/10, 14:53:28
I should try without kdenext ;)
Title: Re: [URGENT] GCC 5 fallout incoming
Post by: piper on 2015/08/10, 15:00:23
Without kdenext, not really a difference

126 upgraded, 0 newly installed, 395 to remove and 91 not upgraded.

Code: [Select]
Building dependency tree      
Reading state information... Done
Calculating upgrade... Done
The following packages will be REMOVED:
  akonadi-server amarok aptitude ark automoc baloo-kf5 breeze dolphin frameworkintegration gcc-5 gparted gwenview k3b kactivities kaffeine kate katepart kbackup kcalc
  kcmsystemd kcometen4 kde-baseapps kde-baseapps-bin kde-cli-tools kde-config-gtk-style kde-config-sddm kde-config-systemd kde-plasma-desktop kde-runtime
  kde-style-breeze kde-style-breeze-qt4 kde-style-oxygen-qt5 kde-style-polyester kde-style-qtcurve-qt5 kde-window-manager kde-workspace kde-workspace-bin
  kde-workspace-data kde-workspace-dev kdeartwork-theme-window kdebase-workspace-bin kdebase-workspace-dev kded5 kdelibs-bin kdelibs5-dev kdelibs5-plugins
  kdemultimedia-kio-plugins kdenetwork-filesharing kdepasswd kdepim-runtime kdepimlibs-kio-plugins kdeplasma-addons kdoctools kdoctools5 kfind khelpcenter kinfocenter5
  kinit kio kio-audiocd kio-extras kio-mtp kmenuedit kmix konq-plugins konqueror konqueror-nsplugins konsole konsole-kpart konsole4-kpart konversation kpackagetool5 kpat
  kross kscreen kscreensaver ksnapshot ksysguard ktexteditor-katepart kuser kwin kwin-decoration-oxygen kwin-style-breeze kwin-style-crystal kwin-style-qtcurve kwrite
  libakonadi-kcal4 libakonadi-kde4 libakonadi-kmime4 libakonadi-xml4 libatkmm-1.6-1 libattica0.4 libbaloowidgets4 libcairomm-1.0-1 libcwidget3 libdbusmenu-qt5-2
  libflac++6 libgconfmm-2.6-1c2 libglademm-2.4-1c2a libglibmm-2.4-1c2a libgtkmm-2.4-1c2a libgtkmm-3.0-1 libk3b6 libk3b6-extracodecs libkabc4 libkactivities-bin
  libkactivities6 libkatepartinterfaces4 libkcal4 libkcalutils4 libkcddb4 libkcmutils4 libkde3support4 libkdeclarative5 libkdecorations2-5 libkdecorations2private5
  libkdecorations4abi2 libkdeui5 libkdewebkit5 libkdnssd4 libkemoticons4 libkexiv2-11 libkf5activities5 libkf5activitiesexperimentalstats1 libkf5archive5 libkf5attica5
  libkf5auth5 libkf5baloo1 libkf5balooxapian1 libkf5bookmarks5 libkf5codecs5 libkf5completion5 libkf5config-bin libkf5config-bin-dev libkf5config-dev libkf5configcore5
  libkf5configgui5 libkf5configwidgets5 libkf5coreaddons-bin-dev libkf5coreaddons-dev libkf5coreaddons5 libkf5crash5 libkf5dbusaddons-bin libkf5dbusaddons-dev
  libkf5dbusaddons5 libkf5declarative5 libkf5dnssd5 libkf5emoticons-bin libkf5emoticons5 libkf5filemetadata3 libkf5globalaccel-bin libkf5globalaccel5
  libkf5globalaccelprivate5 libkf5guiaddons5 libkf5i18n-dev libkf5i18n5 libkf5iconthemes-bin libkf5iconthemes5 libkf5idletime5 libkf5itemmodels5 libkf5itemviews5
  libkf5jobwidgets5 libkf5jsembed5 libkf5kcmutils5 libkf5kdegames6 libkf5kdelibs4support5 libkf5kdelibs4support5-bin libkf5khtml-bin libkf5khtml5 libkf5kiocore5
  libkf5kiofilewidgets5 libkf5kiontlm5 libkf5kiowidgets5 libkf5krosscore5 libkf5krossui5 libkf5networkmanagerqt6 libkf5newstuff5 libkf5notifications5 libkf5notifyconfig5
  libkf5package-dev libkf5package5 libkf5parts5 libkf5people5 libkf5peoplebackend5 libkf5peoplewidgets5 libkf5plasma5 libkf5plasmaquick5 libkf5prison1 libkf5pty5
  libkf5quickaddons5 libkf5runner5 libkf5screen6 libkf5service-bin libkf5service-dev libkf5service5 libkf5solid-bin libkf5solid5 libkf5sonnetcore5 libkf5sonnetui5
  libkf5style5 libkf5su-bin libkf5su5 libkf5sysguard-bin libkf5texteditor5 libkf5textwidgets5 libkf5threadweaver5 libkf5unitconversion5 libkf5wallet-bin libkf5wallet5
  libkf5waylandclient5 libkf5waylandserver5 libkf5webkit5 libkf5widgetsaddons5 libkf5windowsystem5 libkf5xmlgui-bin libkf5xmlgui5 libkf5xmlrpcclient5 libkfile4
  libkfontinst5 libkfontinstui5 libkholidays4 libkhtml5 libkidletime4 libkimproxy4 libkio5 libkipi11 libkldap4 libkmediaplayer4 libknewstuff2-4 libknewstuff3-4
  libknotifyconfig4 libkonq-common libkonq5abi1 libkonqsidebarplugin4a libkparts4 libkpimidentities4 libkpimtextedit4 libkpimutils4 libkprintutils4 libkresources4
  libkrosscore4 libkrossui4 libkscreensaver5 libksgrd4 libksgrd7 libksignalplotter7 libktexteditor4 libkutils4 libkwalletbackend5-5 libkwin4-effect-builtins1
  libkwineffects1abi5 libkwineffects6 libkwinglutils6 libkwinxrenderutils6 libkworkspace4abi2 libkworkspace5-5 libkxmlrpcclient4 liblastfm1 libmailtransport4
  libmicroblog4 libmyth-0.27-0 libnepomuk4 libnepomukcore4 libnepomukquery4a libnepomukutils4 liboxygenstyle5-5 liboxygenstyleconfig5-5 libpangomm-1.4-1 libphonon-dev
  libphonon4qt5-4 libplasma-geolocation-interface5 libplasma3 libplasmaclock4abi4 libplasmagenericshell4 libpolkit-qt5-1-1 libpowerdevilcore2 libpowerdevilui5
  libprocesscore7 libprocessui4a libprocessui7 libqt4-declarative libqt4-dev libqt4-dev-bin libqt4-help libqt4-qt3support libqt4-xmlpatterns libqt5clucene5
  libqt5concurrent5 libqt5core5a libqt5dbus5 libqt5designer5 libqt5designercomponents5 libqt5gui5 libqt5help5 libqt5multimedia5 libqt5multimediaquick-p5 libqt5network5
  libqt5opengl5 libqt5printsupport5 libqt5qml5 libqt5quick5 libqt5quickwidgets5 libqt5script5 libqt5scripttools5 libqt5sensors5 libqt5sensors5-dev libqt5sql5
  libqt5sql5-sqlite libqt5svg5 libqt5test5 libqt5webkit5 libqt5widgets5 libqt5x11extras5 libqt5xml5 libqtassistantclient4 libqtscript4-network libqtwebkit4
  libsigc++-2.0-0c2a libsoprano-dev libsoprano4 libtaskmanager4abi4 libtaskmanager5 libweather-ion6 libweather-ion7 linux-headers-4.1.4-towo.1-siduction-amd64
  linux-headers-siduction-amd64 milou mplayerthumbs mythlogserver mythtv mythtv-backend mythtv-frontend mythtv-transcode mythweather paman paprefs partitionmanager
  pavucontrol phonon4qt5-backend-vlc plasma-containments-addons plasma-dataengines-addons plasma-desktop plasma-framework plasma-framework-dev plasma-runners-addons
  plasma-scriptengine-javascript plasma-wallpapers-addons plasma-widget-folderview plasma-widget-lancelot plasma-widgets-addons plasma-workspace polkit-kde-1
  polkit-kde-agent-1 powerdevil pyqt4-dev-tools pyqt5-dev-tools python-qt4 python3-pyqt5 qdbus-qt5 qml-module-org-kde-draganddrop qml-module-org-kde-extensionplugin
  qml-module-org-kde-kcoreaddons qml-module-org-kde-kio qml-module-org-kde-kquickcontrols qml-module-org-kde-kquickcontrolsaddons qml-module-org-kde-kwindowsystem
  qml-module-org-kde-solid qml-module-qtgraphicaleffects qml-module-qtmultimedia qml-module-qtquick-controls qml-module-qtquick-controls-styles-breeze
  qml-module-qtquick-dialogs qml-module-qtquick-layouts qml-module-qtquick-privatewidgets qml-module-qtquick-window2 qml-module-qtquick2 qml-module-qtwebkit qt4-designer
  qt4-dev-tools qtbase5-dev qtbase5-dev-tools qtcurve qtdeclarative5-kf5declarative qtdeclarative5-kf5solid qtscript5-dev qttools5-dev-tools sddm
  siduction-art-kde-whiteroom siduction-art-ksplash-whiteroom smplayer smplayer-themes sweeper systemsettings virtualbox-qt yakuake
The following packages have been kept back:
  amarok-utils apt apt-utils build-essential cdrdao cmake cpp cpp-5 cups-filters cups-filters-core-drivers encfs g++ g++-multilib gcc gcc-5-base gcc-5-base:i386
  gcc-multilib gddrescue gdisk gettext-base glib-networking glib-networking-services gstreamer0.10-plugins-good gstreamer0.10-plugins-ugly hardinfo lib32atomic1
  lib32cilkrts5 lib32gcc1 lib32gomp1 lib32itm1 lib32quadmath0 lib32stdc++6 lib32ubsan0 libapt-pkg-perl libasan2 libatomic1 libcc1-0 libchromaprint0 libcilkrts5
  libgcc-5-dev libgcc1 libgcc1:i386 libgfortran3 libgomp1 libhunspell-1.3-0 libitm1 libjavascriptcoregtk-4.0-18 liblsan0 libmpx0 libpsl0 libqca2 libqt4-dbus
  libqt4-designer libqt4-network libqt4-opengl libqt4-script libqt4-scripttools libqt4-sql libqt4-sql-mysql libqt4-sql-sqlite libqt4-svg libqt4-test libqt4-xml
  libqt5core5a:i386 libqtcore4 libqtdbus4 libqtgui4 libquadmath0 libstdc++6 libstdc++6:i386 libtag-extras1 libtagc0 libtsan0 libubsan0 libwebkit2gtk-4.0-37 libx32atomic1
  libx32cilkrts5 libx32gcc1 libx32gomp1 libx32itm1 libx32quadmath0 libx32stdc++6 libx32ubsan0 python-apt qdbus qt4-linguist-tools uno-libs3 ure vlc vlc-nox
  vlc-plugin-notify
The following packages will be upgraded:
  apache2 apache2-bin apache2-data apache2-utils aptitude-common binutils cube2 cups-browsed devscripts dmeventd dmsetup dpkg dpkg-dev dvd+rw-tools fancontrol fish
  fish-common fonts-opensymbol gettext ghostscript ghostscript-x gperf growisofs gstreamer0.10-gconf gstreamer0.10-pulseaudio iso-codes kdelibs5-data libarchive-zip-perl
  libconfig-inifiles-perl libcrystalhd3 libcupsfilters1 libdevmapper-event1.02.1 libdevmapper1.02.1 libdpkg-perl libelf1 libelf1:i386 libflac8 libfontembed1 libgeoip1
  libgs9 libgs9-common libidn11 libinput10 libjbig2dec0 libkdecore5 libkdesu5 libkjsapi4 libkjsembed4 libkntlm4 libkpty4 libkunitconversion4 libloudmouth1-0
  liblvm2cmd2.02 libnss-myhostname libpciaccess-dev libpciaccess0 libpciaccess0:i386 libpcre16-3 libpcre16-3:i386 libpcre3 libpcre3:i386 libpcsclite1 libphonon4
  libpolkit-qt-1-1 libpulse-mainloop-glib0 libpulse0 libpulsedsp libqt5dbus5:i386 libqt5gui5:i386 libqt5network5:i386 libqt5qml5:i386 libqt5quick5:i386
  libreoffice-style-galaxy librrd4 librsvg2-2 librsvg2-common libseccomp2 libsecret-1-0 libsecret-common libsensors4 libsolid4 libsqlite3-0 libsvn-perl libsvn1
  libthreadweaver4 libudev1 libudev1:i386 libusb-0.1-4 libvlc5 libvlccore8 libxaw7 libxaw7-dev lintian linux-libc-dev lm-sensors mime-support phonon pulseaudio
  pulseaudio-module-bluetooth pulseaudio-module-gconf pulseaudio-module-x11 pulseaudio-module-zeroconf pulseaudio-utils python-apt-common python-lxml
  python-pkg-resources python-reportbug python3-pkg-resources qml-module-qtgraphicaleffects:i386 qml-module-qtquick2:i386 qt4-qmake qt5-qmake qtcore4-l10n reportbug
  sensord signing-party simple-scan soprano-daemon squashfs-tools subversion subversion-tools systemd-sysv udev usbutils vlc-data vlc-plugin-pulse
126 upgraded, 0 newly installed, 395 to remove and 91 not upgraded.
Need to get 64.8 MB of archives.
After this operation, 873 MB disk space will be freed.
Title: Re: [URGENT] GCC 5 fallout incoming
Post by: dibl on 2015/08/10, 15:49:42
The transition tracker is only showing 10% this morning.  Assuming a start on 1 AUG, that's one percent per day of progress.  A very rough metric, but it gives the idea of the magnitude -- it could be 100 days to complete.
Title: Re: [URGENT] GCC 5 fallout incoming
Post by: melmarker on 2015/08/10, 17:13:14
@dibl - why so optimistic? 8)
Title: Re: [URGENT] GCC 5 fallout incoming
Post by: dibl on 2015/08/10, 17:22:02
@dibl - why so optimistic? 8)


It doesn't matter to me -- my siduction systems were last updated on 30 JUL, and they are running perfectly today and doing everything that I need done.  Iceweasel and chromium still browse nicely, LibreOffice still calculates, Plasma 5 still acts like a beta+ version of a desktop, latest conky still crashes every so often.  All running as expected for a sid system, and if it takes until Columbus Day to finish the transition, I will not be bothered in the slightest.   8)
Title: Re: [URGENT] GCC 5 fallout incoming
Post by: domicius on 2015/08/10, 21:12:28
Well, I'm also optimistically monitoring the transition tracker :) Mostly because I switched to Plasma 5 and while it's usable, it's got a long list of "regressions" for my personal use case. And the sooner this major transition is over, the sooner, I hope, Plasma 5 starts getting better. :)

And when we think about it, most probably each and every user has a different set of packages installed and those they rely on more or less daily for their work. Because of that, I pretty much ignore any premature "updated, everything seems ok", because I know "everything" is never everything and "everything" for one users is never "everything" for other users. Like me. :)
Title: Re: [URGENT] GCC 5 fallout incoming
Post by: ralul on 2015/08/10, 22:03:31
Do we have lost all of Debian sid for the next half year?
While my estimate holds true a week later: What about Debian testing? If you need to intall a newer kind of Debian now ...
Title: Re: [URGENT] GCC 5 fallout incoming
Post by: melmarker on 2015/08/10, 23:02:50
ralul, calm down - 10% of the transition are done :D - there will be a few breaks, but there is an easy solution: Don't touch a running system or have a good and tested rollback or recovery strategy. Maybe this is the right time to find a new approach to different things - i for my self removed multiarch from my system, the last program that need multiarch was teamviewer. and that one could run in a VM (Windows or Linux - i didn't care, same for skype - but wait, well, i have a Microsoft Phone for skype 8) )
Title: Re: [URGENT] GCC 5 fallout incoming
Post by: michaa7 on 2015/08/10, 23:09:57
My just *simulated* d-u would remove all kernel headers including the respective meta package and the headers of the current kernel  linux-headers-4.1.4-towo.1-siduction-amd64 linux-headers-siduction-amd64.

As now the header package of our kernel  is hit by the transition we should all be very carefull with any kind of upgrades, i.e. wait the next 100 days.
Title: Re: [URGENT] GCC 5 fallout incoming
Post by: madal on 2015/08/11, 07:19:11
Arriving at this post TODAY! trying to figure out why KDE is so messed up..........

Anyone interested in knowing what's going on for someone who was doing religious d-u's out of ignorance?

Mad Al
Title: Re: [URGENT] GCC 5 fallout incoming
Post by: devil on 2015/08/11, 08:06:00
Welcome to siduction and ozur forums. Please enlighten us.


greetz
devil
Title: Re: [URGENT] GCC 5 fallout incoming
Post by: cas on 2015/08/11, 09:46:23
I didn't count, but  this page (https://release.debian.org/transitions/html/libstdc++6.html) looks as even less than 10% was achieved.
It is clear that this transition can not happen within hours or a few days.

Nevertheless my question is, why does this take so long? Are these guys on vacation? Did nobody tell them? Is there (much) more to it, than just a new compilation?

Greetings, C
   
 
Title: Re: [URGENT] GCC 5 fallout incoming
Post by: devil on 2015/08/11, 13:48:21
It is a reansition that triggers many other transitions. Packages need to also be uploaded in a certain order to not wreak more havoc than is already the case. Yes, this is a complicated process. And some people are for sure on vacation or otherwise not available.


greetz
devil
Title: Re: [URGENT] GCC 5 fallout incoming
Post by: clubex on 2015/08/11, 14:04:30
What's a "reansition"? I can't find it in any dictionary I have. Nor can I find a definition of it on the web.
Title: Re: [URGENT] GCC 5 fallout incoming
Post by: madal on 2015/08/11, 14:14:37
WOW! A response from the devil himself! I am honored. I've been a fan since the Sidux days.
(If I come off as being insincere, I assure you, I am not).


Anyway. For about a week now, my d-u's have been held up by only 2 packages: kwin-data and kwin-x11. Unmeetable dependencies.
Dolphin is gone and has unmeetable dependencies.
Konqueror is broken. I can only view files in Konq using filelight or FSview. Not optimal, but functional.
Taskbar - pager and task manager are gone, but launcher still works.
I cannot resize open windows.
The menu bar on open programs is gone.


Basically functional, but royally screwed up.


Mad Al
Title: Re: [URGENT] GCC 5 fallout incoming
Post by: madal on 2015/08/11, 14:16:02
@clubex


I believe he meant "transition." Typing too fast..


Mad Al
Title: Re: [URGENT] GCC 5 fallout incoming
Post by: ralul on 2015/08/11, 14:52:40
ralul, calm down - 10% of the transition are done :D - there will be a few breaks, but there is an easy solution: Don't touch a running system or have a good and tested rollback or recovery strategy.
Yes, don't touch your Debian yet if your working environment works ... My working horse at the moment is Gentoo using an older gcc-4.9 toolchain. Thus I can experiment with my Debian Sid partition: I ever wanted to give Gnome-3.16 a second try after years.

I purged all of Kde, sddm, vlc, kaffeine, xfce. I disabled siduction kdenext repos and only kept the Debian Sid unstable package list. Gnome installed and runs well (I don't know if Gnome had to transit at all, has it C++ code?). All of my remaining Debian Sid packages went through a full dist-upgrade including libreoffice-5 (this one pulls in a newer boost-dateime). Afterwards I was able to reinstall
- sddm, which pulled a lot of kde and plasma in again
- vlc and kaffeine,
where I had to purge some of multimedia libs in case there was a newer one with an ending name 'v5'

Debian Sid is usable riding Gnome-3.16 as Desktop.
Title: Re: [URGENT] GCC 5 fallout incoming
Post by: cas on 2015/08/11, 14:54:20
OT:
I hoped that google would enlighten me, what the strange "ozur forums" were. It happend that I was enligthended by myself.  :P
Title: Re: [URGENT] GCC 5 fallout incoming
Post by: ralul on 2015/08/11, 17:36:02
I purged all of Kde, sddm, vlc, kaffeine, xfce. I disabled siduction kdenext repos and only kept the Debian Sid unstable package list.
I can re-install pretty much of Kde but NOT Dolphin. It insists on an old tagging lib which is incompatible the one gstreamer-1.45 uses.
Title: Re: [URGENT] GCC 5 fallout incoming
Post by: ghstryder on 2015/08/13, 00:24:45
My list to be removed is down to 45, the lowest it has been in some time. Someone has been burning the midnight oil.
Title: Re: [URGENT] GCC 5 fallout incoming
Post by: tux on 2015/08/13, 02:00:46
Code: [Select]
248 upgraded, 46 newly installed, 145 to remove and 5 not upgraded.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: Spike_DE on 2015/08/14, 13:14:30
yep, it's getting better...

Quote
301 aktualisiert, 22 neu installiert, 35 zu entfernen und 0 nicht aktualisiert.

Code: [Select]
Die folgenden Pakete werden ENTFERNT:
  aptitude dolphin juk k3b k3b-i18n kde-baseapps kde-plasma-desktop kde-standard kdepim kdepim-strigi-plugins krename ktorrent libasprintf0c2 libbaloowidgets4 libcwidget3 libebml4 libglibmm-2.4-1c2a libk3b6 libk3b6-extracodecs
  libkfilemetadata4 libmatroska6 libopenconnect2 libproxy1 libqpdf13 librlog5 libsigc++-2.0-0c2a libstreamanalyzer0 libstreams0 libstrigihtmlgui0 libtag1-vanilla libtag1c2a libtagc0 moc nepomuk-core-runtime strigi-client
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: vilde on 2015/08/14, 13:56:10
I have a fully dist-upgraded system, the only thing i know  is broken is audacious,  I never use it. My system is a 64 bit xfce, indian summer, multiarch. Google Earth works and Libre Office seems to work, I rarely use it. My Iceweasel is from experimental. If there is something someone want's me to try if it's working I can do so.
Quote
inxi -v3
System:    Host: T420 Kernel: 4.1.5-towo.1-siduction-amd64 x86_64 (64 bit gcc: 5.2.1)
           Desktop: Xfce 4.12.2 (Gtk 2.24.25)
           Distro: siduction 14.1.0 Indian Summer - xfce - (201411230427)
Machine:   System: LENOVO product: 25223FG v: ThinkPad T410
           Mobo: LENOVO model: 25223FG
           Bios: LENOVO v: 6IET85WW (1.45 ) date: 02/14/2013
CPU:       Dual core Intel Core i7 M 620 (-HT-MCP-) cache: 4096 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 10645
           clock speeds: max: 2667 MHz 1: 1199 MHz 2: 1199 MHz 3: 2667 MHz
           4: 1599 MHz
Graphics:  Card: NVIDIA GT218M [NVS 3100M] bus-ID: 01:00.0
           Display Server: X.Org 1.17.2 drivers: nouveau (unloaded: fbdev,vesa)
           Resolution: 1440x900@60.06hz
           GLX Renderer: Gallium 0.4 on NVA8
           GLX Version: 3.0 Mesa 10.6.3 Direct Rendering: Yes
Network:   Card-1: Intel 82577LM Gigabit Network Connection
           driver: e1000e v: 2.3.2-k port: 1820 bus-ID: 00:19.0
           IF: eth0 state: up speed: 100 Mbps duplex: full
           mac: 00:26:2d:f3:8e:a0
           Card-2: Intel Centrino Ultimate-N 6300
           driver: iwlwifi bus-ID: 03:00.0
           IF: wlan0 state: up mac: 00:24:d7:06:72:fc
Drives:    HDD Total Size: 240.1GB (71.5% used) ID-1: model: Crucial_CT240M50
Info:      Processes: 210 Uptime: 4 min Memory: 644.7/3820.0MB
           Init: systemd runlevel: 5 Gcc sys: 5.2.1
           Client: Shell (bash 4.3.391) inxi: 2.2.26
Quote
apt-cache policy iceweasel
iceweasel:
  Installerad: 40.0-1
  Kandidat:    40.0-1
  Versionstabell:
 *** 40.0-1 0
          1 http://ftp.debian.org/debian/ (http://ftp.debian.org/debian/) experimental/main amd64 Packages
        100 /var/lib/dpkg/status
     38.2.0esr-1 0
        500 http://http.debian.net/debian/ (http://http.debian.net/debian/) unstable/main amd64 Packages

Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: Santa on 2015/08/14, 19:06:11

Quote from: piper
I should try without kdenext



No, you shouldn't. kdenext is not something optional which you should enable or disable depending on your mood. That is a recipe to break your system.


Also you should not disable it in a trial-error fashion to see if problems are "magically" solved. That is also a recipe to break your system.


Regarding KDE, it's not safe to dist-upgrade yet.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: holgerw on 2015/08/15, 09:00:34
Hello,

please also look here:
http://forum.siduction.org/index.php?topic=5728.msg46914#msg46914 (http://forum.siduction.org/index.php?topic=5728.msg46914#msg46914)

At this time (Saturday morning, 15.07.2015) adding kde flavour is not possibe, also with enabled kdenext repo.

Kind regards,
  Holger
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: NochEinNeuer on 2015/08/15, 11:39:09
Derzeit  sieht es bei mir so aus:
Code: [Select]
223 aktualisiert, 31 neu installiert, 21 zu entfernen wenn ich ein apt-get update und apt-get dist-upgrade machen würde. Bisher ging ich immer auf n beim dist-upgrade.
Ich vermute das ist weiterhin besser so?
Zum ENTFERNEN werden folgende aufgeführt:
Code: [Select]
Die folgenden Pakete werden ENTFERNT:
  libasprintf0c2 libbinio1ldbl libboost-date-time1.55.0 libcmis-0.5-5
  libcwidget3 libebml4 libept1.4.12 libglibmm-2.4-1c2a libgltf-0.0-0
  libmatroska6 liborcus-0.10-0 libprotobuf9 libproxy1 libqpdf13 librlog5
  libsidplay1 libsigc++-2.0-0c2a libtag1-vanilla libtag1c2a libxapian22
  printer-driver-brlaser
Allerdings weis ich auch nicht ob von diesen Paketen nicht auch wirklich welche entfallen sind und daher nicht mehr benötigt würden....


Allerdings gehe ich mal davon aus, das weiterhin abwarten und Teetrinken angesagt ist?
Viele Grüße
NochEinNeuer

Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: vilde on 2015/08/15, 12:25:48
I did a post some day ago about being fully upgraded, after that I did a few more d-u without visible problems, no packages removed.

To avoid misunderstanding I want to point out that I don't say it's safe to d-u xfce, I do this because I think it's fun an at my own risk.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: bluelupo on 2015/08/15, 12:32:34
[...]
Allerdings gehe ich mal davon aus, das weiterhin abwarten und Teetrinken angesagt ist?
Viele Grüße
NochEinNeuer

....das wird die nächsten Wochen so weiter gehen. Also Füße stillhalten ;-)
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: musca on 2015/08/15, 16:38:47
Hello NochEinNeuer,

I guess you don't use the KDE-Desktop?
Your dist-upgrade looks quite well. No applications are removed, only some libs get replaced by new packages.
We need to check the list of newly installed packages from the same output (just a few lines more text).

Removing "printer-driver-brlaser" might be a concern for printing.

On the cinnamon-desktop (not KDE!)  my d-u from five days ago looked like this
http://forum.siduction.org/index.php?topic=5719.msg46837#msg46837

greetings
musca

P.S.: you really should pick a more useful nickname.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: NochEinNeuer on 2015/08/15, 18:19:10
Ich verwende xfce.
Im einzelnen schauts so aus:
Code: [Select]
Die folgenden Pakete werden ENTFERNT:
  libasprintf0c2 libbinio1ldbl libboost-date-time1.55.0 libcmis-0.5-5
  libcwidget3 libebml4 libept1.4.12 libglibmm-2.4-1c2a libgltf-0.0-0
  libmatroska6 liborcus-0.10-0 libprotobuf9 libproxy1 libqpdf13 librlog5
  libsidplay1 libsigc++-2.0-0c2a libtag1-vanilla libtag1c2a libxapian22
  printer-driver-brlaser
Die folgenden NEUEN Pakete werden installiert:
  g++-5 libapt-inst1.7 libapt-pkg4.16 libasprintf0v5 libbinio1v5
  libboost-date-time1.58.0 libboost-iostreams1.58.0
  libboost-serialization1.58.0 libboost-system1.58.0 libboost-thread1.58.0
  libcmis-0.5-5v5 libcwidget3v5 libebml4v5 libept1.4.16 libglibmm-2.4-1v5
  libgltf-0.0-0v5 libicu55 libmatroska6v5 liborcus-0.10-0v5 libprotobuf9v5
  libproxy1v5 libqpdf13v5 librlog5v5 libsidplay1v5 libsigc++-2.0-0v5
  libstdc++-5-dev libtag1v5 libtag1v5-vanilla libxapian22v5
  linux-headers-4.1.5-towo.1-siduction-amd64
  linux-image-4.1.5-towo.1-siduction-amd64
Die folgenden Pakete sind zurückgehalten worden:
  conky-all
Die folgenden Pakete werden aktualisiert (Upgrade):
  apt apt-utils aptitude aptitude-common audacious-plugins binutils
  build-essential cdrdao cpp cpp-5 cups-browsed cups-filters
  cups-filters-core-drivers db5.3-util debhelper dmeventd dmsetup dpkg
  dpkg-dev dvd+rw-tools encfs evolution-data-server-common exim4-base
  exim4-config exim4-daemon-light fonts-opensymbol g++ gcc gcc-5 gcc-5-base
  gddrescue gdisk gettext gettext-base ghostscript ghostscript-x
  gir1.2-packagekitglib-1.0 glib-networking glib-networking-services gparted
  growisofs gstreamer0.10-gconf gstreamer0.10-plugins-good
  gstreamer0.10-plugins-ugly gstreamer0.10-pulseaudio gstreamer1.0-pulseaudio
  hexchat icedove iceowl-extension iceweasel iceweasel-l10n-de iso-codes
  lib32gcc1 lib32stdc++6 libapt-pkg-perl libasan2 libatkmm-1.6-1 libatomic1
  libcairomm-1.0-1 libcc1-0 libcilkrts5 libconfig9 libcrystalhd3
  libcupsfilters1 libdb5.3 libdevmapper-event1.02.1 libdevmapper1.02.1
  libdpkg-perl libelf1 libexempi3 libflac8 libfontembed1 libgcc-5-dev libgcc1
  libgconfmm-2.6-1c2 libgeoip1 libgfortran3 libglademm-2.4-1c2a
  libgnutls-deb0-28 libgnutls-openssl27 libgomp1 libgs9 libgs9-common
  libgtkmm-2.4-1c2a libgtkmm-3.0-1 libhogweed4 libhunspell-1.3-0 libidn11
  libinput10 libitm1 libjavascriptcoregtk-4.0-18 libjbig2dec0 libloudmouth1-0
  liblsan0 liblvm2app2.2 liblvm2cmd2.02 libmpx0 libnettle6 libnss-myhostname
  libpackagekit-glib2-18 libpam-systemd libpangomm-1.4-1 libpci3 libpciaccess0
  libpcre16-3 libpcre3 libpcsclite1 libphonenumber6 libproxy-tools libpsl0
  libpulse-mainloop-glib0 libpulse0 libpulsedsp libqt4-dbus libqt4-network
  libqt4-opengl libqt4-script libqt4-svg libqt4-xml libqt4-xmlpatterns
  libqt5core5a libqt5dbus5 libqt5gui5 libqt5network5 libqt5opengl5
  libqt5printsupport5 libqt5qml5 libqt5quick5 libqt5script5 libqt5sql5
  libqt5svg5 libqt5webkit5 libqt5widgets5 libqt5x11extras5 libqt5xml5
  libqtcore4 libqtdbus4 libqtgui4 libqtwebkit4 libquadmath0 libreoffice
  libreoffice-avmedia-backend-gstreamer libreoffice-base libreoffice-base-core
  libreoffice-base-drivers libreoffice-calc libreoffice-common
  libreoffice-core libreoffice-draw libreoffice-impress
  libreoffice-java-common libreoffice-l10n-de libreoffice-math
  libreoffice-pdfimport libreoffice-report-builder-bin
  libreoffice-style-galaxy libreoffice-writer librsvg2-2 librsvg2-common
  libseccomp2 libsecret-1-0 libsecret-common libsensors4 libsqlite3-0
  libstdc++6 libsystemd0 libtagc0 libtracker-sparql-1.0-0 libtsan0 libubsan0
  libudev1 libusb-0.1-4 libvlc5 libvlccore8 libwebkit2gtk-4.0-37 libwmf0.2-7
  libx264-146 libxaw7 linux-headers-siduction-amd64
  linux-image-siduction-amd64 linux-libc-dev lm-sensors lvm2 mime-support
  paman paprefs pavucontrol pavumeter pciutils pinentry-gnome3 pinentry-gtk2
  pulseaudio pulseaudio-module-bluetooth pulseaudio-module-gconf
  pulseaudio-module-x11 pulseaudio-module-zeroconf pulseaudio-utils python-apt
  python-apt-common python-numpy python-pkg-resources python-reportbug
  python3-pkg-resources python3-uno qdbus qtcore4-l10n reportbug signing-party
  squashfs-tools synaptic systemd systemd-sysv thunar-media-tags-plugin tzdata
  udev uno-libs3 ure usbutils vlc vlc-nox xfsprogs xserver-common
  xserver-xorg-core
223 aktualisiert, 31 neu installiert, 21 zu entfernen und 1 nicht aktualisiert.



Ausserdem habe ich seit kurzem dies hier:
Code: [Select]
Es wurden 606 kB in 44 s geholt (13,7 kB/s).                                   
W: Fehlschlag beim Holen von http://http.debian.net/debian/dists/unstable/main/binary-amd64/PackagesIndex  Hash-Summe stimmt nicht überein

W: Fehlschlag beim Holen von http://http.debian.net/debian/dists/unstable/main/i18n/Translation-enIndex  Hash-Summe stimmt nicht überein

E: Einige Indexdateien konnten nicht heruntergeladen werden. Sie wurden ignoriert oder alte an ihrer Stelle benutzt.
jf@siductionbox:~$ sudo apt-get dist-upgrade
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: seasons on 2015/08/16, 05:40:12
Removing "printer-driver-brlaser" might be a concern for printing.

From what I gather, one can rebuild the package using gcc5.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793223
https://wiki.debian.org/GCC5#libstdc.2B-.2B-_c.2B-.2B-11_incompatibilities_.284.9_and_5.29
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: michaa7 on 2015/08/16, 10:20:08
After observing again the "progress"at this page (https://release.debian.org/transitions/html/libstdc++6.html) I think we'll have quite a very calm year.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: Maik on 2015/08/16, 20:23:19
Quote
....das wird die nächsten Wochen so weiter gehen. Also Füße stillhalten ;-)
Und das bei Sid,  Wochenlang nur Halbe Sachen ^^
Den Nachteil von Bequemlichkeit und Ignoranz sieht man jetzt  :P
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: melmarker on 2015/08/16, 20:36:00
I would like to see the current situation as the ultimate chance to dive deep in the abyss of apt :D
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: KrunchTime on 2015/08/17, 10:51:31
I successfully performed a dist-upgrade on my laptop a little over an hour ago.  Some packages were removed, but all but one were replaced with new ones.  Note:  I do not run KDE.  I run openbox.

I then proceeded to finish installing my favorite apps.  I was able to install everything but guayadeque.  The one package removed, that wasn't replaced, is a dependency for guayadeque.  Overall, I'm a happy camper.  Woo hoo!


(http://s26.postimg.org/deqyoiyh1/snoopy_dancing_by_jessie4508.jpg) (http://postimg.org/image/deqyoiyh1/)
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: zephyr on 2015/08/18, 10:07:48
Haven't seen this posted yet on Siduction, a link for sid dist-upgrade. A lot of useful info.


https://release.debian.org/transitions/html/libstdc++6.html (https://release.debian.org/transitions/html/libstdc++6.html)
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: Jörg on 2015/08/18, 13:07:10
@zephyr
Accidentally you must have overlooked the post of "cas" in this very thread:

« Reply #53 on: 2015/08/11, 09:46:23 »

Greetings,
Jörg
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: zephyr on 2015/08/18, 13:49:24
@Jorg: Yes I certainly did "this page" by cas reply #53. I missed it a few times. So little info out there and glad someone had already posted. Looks like it is going to be a while for us all. - Thanks-zephyr
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: CCarpenter on 2015/08/18, 14:42:03
Its getting better and better - when i should give it a try?

Code: [Select]
  Die folgenden Pakete werden ENTFERNT:
  baloo baloo-utils baloo4 dolphin eiskaltdcpp-qt filezilla fp-units-gnome1-2.6.4 fp-units-gtk-2.6.4 gtk2-engines-qtcurve kde-baseapps kde-plasma-desktop kdepim
  kdepim-strigi-plugins kodi kodi-bin kodi-data ktorrent libasprintf0c2 libbaloowidgets4 libboost-date-time1.54.0 libboost-date-time1.55.0 libcmis-0.3-3 libcmis-0.4-4 libcmis-0.5-5
  libebml4 libeiskaltdcpp2.2 libflac++6 libglibmm-2.4-1c2a libgltf-0.0-0 libjsoncpp0 libkfilemetadata4 liblucene++0 libmatroska6 libmovit2 libopenconnect3 liborcus-0.10-0
  libpcrecpp0 libprotobuf-lite9 libproxy1 libqpdf13 libsigc++-2.0-0c2a libsigc++-2.0-0c2a:i386 libstreamanalyzer0 libstreams0 libstrigihtmlgui0 libtag1-dev libtag1-vanilla
  libtag1c2a libtagc0 libvamp-hostsdk3 libvamp-sdk2 mixxx moc nepomuk-core-runtime poedit sqlitebrowser strigi-client xbmc xbmc-bin xbmc-data
Die folgenden NEUEN Pakete werden installiert:
  distro-info-data g++-5 libantlr3-runtime-java libapt-inst1.7 libapt-pkg4.16 libasprintf0v5 libatk1.0-dev libbasicusageenvironment1 libboost-chrono1.58.0 libboost-date-time1.58.0
  libboost-filesystem1.58.0 libboost-iostreams1.58.0 libboost-random1.58.0 libboost-regex1.58.0 libboost-system1.58.0 libboost-thread1.58.0 libcairo2-dev libcmis-0.5-5v5
  libcpprest2.6 libdrm-amdgpu1 libebml4v5 libexiv2-14 libflac++6v5 libgdk-pixbuf2.0-dev libglib2.0-dev libglibmm-2.4-1v5 libgltf-0.0-0v5 libgraphicsmagick++11 libgroupsock7
  libgtk2.0-dev libicu55 libjsoncpp0v5 liblivemedia49 liblua5.3-0 liblua5.3-dev libmatroska6v5 libmovit2v5 libnpth0 liborcus-0.10-0v5 libpango1.0-dev libpcrecpp0v5
  libprotobuf-lite9v5 libproxy1v5 libqbscore1 libqbsqtprofilesetup1 libqpdf13v5 libqtcurve-utils2 libsigc++-2.0-0v5 libstdc++-5-dev libstreamanalyzer0v5 libstreams0v5
  libtag1v5-vanilla libusageenvironment3 libvamp-hostsdk3v5 libvamp-sdk2v5 libx264-148 libx264-148:i386 linux-headers-4.1.6-towo.1-siduction-amd64
  linux-image-4.1.6-towo.1-siduction-amd64 lua5.3 python-idna python-ipaddress ruby-power-assert ruby-test-unit
Die folgenden Pakete sind zurückgehalten worden:
  dvdstyler libwxsvg3 synaptic
Die folgenden Pakete werden aktualisiert (Upgrade):
  antlr3 apt apt-transport-https apt-utils ardour3 audacity-data automake autopoint base-files bash bind9-host binutils bsdutils cdrdao chromium chromium-l10n cmake console-setup
  console-setup-linux cpp cpp-5 cups-filters cups-filters-core-drivers curl debhelper debootstrap devscripts dh-exec dh-golang dh-lisp dh-lua dh-ocaml dh-python diffstat dirmngr
  distro-defaults dmeventd dmsetup dnsutils dosbox dpkg dpkg-dev dvd+rw-tools dvdstyler-data dvgrab erlang-asn1 erlang-base erlang-crypto erlang-dev erlang-dialyzer erlang-inets
  erlang-mnesia erlang-public-key erlang-runtime-tools erlang-ssl erlang-syntax-tools erlang-tools erlang-webtool fancontrol ffmpeg filezilla-common firmware-linux-free
  flashplayer-mozilla fluxbox fonts-droid fonts-opensymbol fonts-roboto fp-compiler-2.6.4 fp-ide-2.6.4 fp-units-base-2.6.4 fp-units-db-2.6.4 fp-units-fcl-2.6.4 fp-units-fv-2.6.4
  fp-units-gfx-2.6.4 fp-units-gtk2-2.6.4 fp-units-math-2.6.4 fp-units-misc-2.6.4 fp-units-net-2.6.4 fp-units-rtl-2.6.4 frei0r-plugins g++ gcc gcc-5 gcc-5-base gcc-5-base:i386
  gddrescue gdisk gettext gettext-base git git-man glib-networking glib-networking-services gnupg-agent gnupg2 gparted gpgsm growisofs gsmartcontrol gstreamer0.10-gconf
  gstreamer0.10-plugins-good gstreamer0.10-pulseaudio gstreamer1.0-plugins-good gstreamer1.0-pulseaudio handbrake handbrake-cli handbrake-gtk hardinfo html2text icedove
  icedove-l10n-de iceweasel iceweasel-l10n-de iceweasel-l10n-en-gb iceweasel-l10n-it iceweasel-l10n-pl iceweasel-l10n-pt-br iceweasel-l10n-ro icu-devtools imagemagick
  imagemagick-6.q16 imagemagick-common inkscape iproute iproute2 iso-codes jade k3b kdelibs-bin kdelibs5-data kdelibs5-plugins kdoctools keyboard-configuration kid3 kid3-core
  kodi-skin-confluence lgc-pg lib32gcc1 lib32stdc++6 libapr1 libapr1-dev libapt-pkg-perl libarchive-zip-perl libasan2 libasprintf-dev libatinject-jsr330-api-java libatkmm-1.6-1
  libatomic1 libattica0.4 libav-tools libavcodec-dev libavcodec56 libavcodec56:i386 libavdevice56 libavfilter5 libavformat-dev libavformat56 libavresample2 libavresample2:i386
  libavutil-dev libavutil54 libavutil54:i386 libbind9-90 libblkid1 libbluedevil2 libcairomm-1.0-1 libcarp-clan-perl libcc1-0 libcec3.0 libchromaprint-tools libchromaprint0
  libcilkrts5 libclass-c3-perl libcld2-0 libcolord2 libcrystalhd3 libcrystalhd3:i386 libcupsfilters-dev libcupsfilters1 libcurl3 libcurl3-gnutls libdb5.3 libdb5.3:i386 libdb5.3++
  libdevmapper-event1.02.1 libdevmapper1.02.1 libdjvulibre-text libdjvulibre21 libdlrestrictions1 libdns-export100 libdns100 libdpkg-perl libdrm-dev libdrm-intel1
  libdrm-intel1:i386 libdrm-nouveau2 libdrm-nouveau2:i386 libdrm-radeon1 libdrm-radeon1:i386 libdrm2 libdrm2:i386 libegl1-mesa libegl1-mesa:i386 libegl1-mesa-dev
  libegl1-mesa-drivers libelf1 libelf1:i386 libfdisk1 libfdt1 libffms2-4 libflac-dev libflac8 libflac8:i386 libfontembed1 libfontenc1 libfribidi0 libfs6 libftdi1 libgadu3 libgbm1
  libgbm1:i386 libgcc-5-dev libgcc1 libgcc1:i386 libgconfmm-2.6-1c2 libgeoip1 libgettextpo-dev libgettextpo0 libgfortran3 libgl1-mesa-dev libgl1-mesa-dri libgl1-mesa-dri:i386
  libgl1-mesa-glx libgl1-mesa-glx:i386 libglademm-2.4-1c2a libglapi-mesa libglapi-mesa:i386 libgles2-mesa libgme0 libgnomecanvasmm-2.6-1c2a libgnomevfs2-0 libgnomevfs2-common
  libgnutls-deb0-28 libgnutls-deb0-28:i386 libgnutls-openssl27 libgomp1 libgraphicsmagick3 libgtkmm-2.4-1c2a libgtkmm-3.0-1 libharfbuzz-dev libharfbuzz-gobject0 libharfbuzz-icu0
  libharfbuzz0b libharfbuzz0b:i386 libhogweed4 libhogweed4:i386 libhunspell-1.3-0 libicu-dev libidn11 libidn11:i386 libijs-0.35 libinput10 libintl-perl libio-stty-perl
  libirs-export91 libisc-export95 libisc95 libisccc90 libisccfg-export90 libisccfg90 libitm1 libjavascriptcoregtk-4.0-18 libjbig2dec0 libjide-oss-java libjpeg-dev
  libjpeg-turbo-progs libjpeg62-turbo libjpeg62-turbo:i386 libjpeg62-turbo-dev libjsr305-java libk3b6 libk3b6-extracodecs libkcmutils4 libkde3support4 libkdeclarative5 libkdecore5
  libkdesu5 libkdeui5 libkdewebkit5 libkdnssd4 libkemoticons4 libkf5config-bin libkf5config-data libkf5configcore5 libkf5configgui5 libkf5coreaddons-bin-dev libkf5coreaddons-data
  libkf5coreaddons5 libkf5dnssd-data libkf5dnssd5 libkf5guiaddons5 libkf5i18n-data libkf5i18n5 libkf5idletime5 libkf5itemviews-data libkf5itemviews5 libkf5modemmanagerqt6
  libkf5networkmanagerqt6 libkf5plotting5 libkf5threadweaver5 libkf5windowsystem-data libkf5windowsystem5 libkfile4 libkhtml5 libkidletime4 libkimproxy4 libkio5 libkjsapi4
  libkjsembed4 libkmediaplayer4 libknewstuff2-4 libknewstuff3-4 libknotifyconfig4 libkntlm4 libkparts4 libkprintutils4 libkpty4 libkrosscore4 libkrossui4 libktexteditor4
  libkunitconversion4 libkutils4 libllvm3.4 libllvm3.4:i386 liblsan0 liblsmash2 liblua5.1-0 liblua5.1-0-dev liblua5.2-0 liblua5.2-dev liblvm2app2.2 liblvm2cmd2.02 liblwres90
  liblz4-1 libmagickcore-6.q16-2 libmagickwand-6.q16-2 libmixin-linewise-perl libmlt++3 libmlt-data libmlt6 libmm-glib0 libmono-2.0-1 libmono-2.0-dev libmono-accessibility4.0-cil
  libmono-c5-1.1-cil libmono-cairo4.0-cil libmono-cecil-private-cil libmono-cil-dev libmono-codecontracts4.0-cil libmono-compilerservices-symbolwriter4.0-cil libmono-corlib2.0-cil
  libmono-corlib4.0-cil libmono-corlib4.5-cil libmono-cscompmgd0.0-cil libmono-csharp4.0c-cil libmono-custommarshalers4.0-cil libmono-data-tds4.0-cil libmono-db2-1.0-cil
  libmono-debugger-soft4.0a-cil libmono-http4.0-cil libmono-i18n-cjk4.0-cil libmono-i18n-mideast4.0-cil libmono-i18n-other4.0-cil libmono-i18n-rare4.0-cil libmono-i18n-west4.0-cil
  libmono-i18n4.0-all libmono-i18n4.0-cil libmono-ldap4.0-cil libmono-management4.0-cil libmono-messaging-rabbitmq4.0-cil libmono-messaging4.0-cil
  libmono-microsoft-build-engine4.0-cil libmono-microsoft-build-framework4.0-cil libmono-microsoft-build-tasks-v4.0-4.0-cil libmono-microsoft-build-utilities-v4.0-4.0-cil
  libmono-microsoft-build4.0-cil libmono-microsoft-csharp4.0-cil libmono-microsoft-visualc10.0-cil libmono-microsoft-web-infrastructure1.0-cil libmono-oracle4.0-cil
  libmono-parallel4.0-cil libmono-peapi4.0a-cil libmono-posix4.0-cil libmono-profiler libmono-rabbitmq4.0-cil libmono-relaxng4.0-cil libmono-security4.0-cil
  libmono-sharpzip4.84-cil libmono-simd4.0-cil libmono-sqlite4.0-cil libmono-system-componentmodel-composition4.0-cil libmono-system-componentmodel-dataannotations4.0-cil
  libmono-system-configuration-install4.0-cil libmono-system-configuration4.0-cil libmono-system-core4.0-cil libmono-system-data-datasetextensions4.0-cil
  libmono-system-data-entity4.0-cil libmono-system-data-linq4.0-cil libmono-system-data-services-client4.0-cil libmono-system-data-services4.0-cil libmono-system-data4.0-cil
  libmono-system-design4.0-cil libmono-system-drawing-design4.0-cil libmono-system-drawing4.0-cil libmono-system-dynamic4.0-cil libmono-system-enterpriseservices4.0-cil
  libmono-system-identitymodel-selectors4.0-cil libmono-system-identitymodel4.0-cil libmono-system-io-compression-filesystem4.0-cil libmono-system-io-compression4.0-cil
  libmono-system-json-microsoft4.0-cil libmono-system-json4.0-cil libmono-system-ldap-protocols4.0-cil libmono-system-ldap4.0-cil libmono-system-management4.0-cil
  libmono-system-messaging4.0-cil libmono-system-net-http-formatting4.0-cil libmono-system-net-http-webrequest4.0-cil libmono-system-net-http4.0-cil libmono-system-net4.0-cil
  libmono-system-numerics4.0-cil libmono-system-reactive-core2.2-cil libmono-system-reactive-debugger2.2-cil libmono-system-reactive-experimental2.2-cil
  libmono-system-reactive-interfaces2.2-cil libmono-system-reactive-linq2.2-cil libmono-system-reactive-observable-aliases0.0-cil libmono-system-reactive-platformservices2.2-cil
  libmono-system-reactive-providers2.2-cil libmono-system-reactive-runtime-remoting2.2-cil libmono-system-reactive-windows-forms2.2-cil
  libmono-system-reactive-windows-threading2.2-cil libmono-system-runtime-caching4.0-cil libmono-system-runtime-durableinstancing4.0-cil
  libmono-system-runtime-serialization-formatters-soap4.0-cil libmono-system-runtime-serialization4.0-cil libmono-system-runtime4.0-cil libmono-system-security4.0-cil
  libmono-system-servicemodel-activation4.0-cil libmono-system-servicemodel-discovery4.0-cil libmono-system-servicemodel-routing4.0-cil libmono-system-servicemodel-web4.0-cil
  libmono-system-servicemodel4.0a-cil libmono-system-serviceprocess4.0-cil libmono-system-threading-tasks-dataflow4.0-cil libmono-system-transactions4.0-cil
  libmono-system-web-abstractions4.0-cil libmono-system-web-applicationservices4.0-cil libmono-system-web-dynamicdata4.0-cil libmono-system-web-extensions-design4.0-cil
  libmono-system-web-extensions4.0-cil libmono-system-web-http-selfhost4.0-cil libmono-system-web-http-webhost4.0-cil libmono-system-web-http4.0-cil libmono-system-web-mvc3.0-cil
  libmono-system-web-razor2.0-cil libmono-system-web-routing4.0-cil libmono-system-web-services4.0-cil libmono-system-web-webpages-deployment2.0-cil
  libmono-system-web-webpages-razor2.0-cil libmono-system-web-webpages2.0-cil libmono-system-web4.0-cil libmono-system-windows-forms-datavisualization4.0a-cil
  libmono-system-windows-forms4.0-cil libmono-system-windows4.0-cil libmono-system-xaml4.0-cil libmono-system-xml-linq4.0-cil libmono-system-xml-serialization4.0-cil
  libmono-system-xml4.0-cil libmono-system2.0-cil libmono-system4.0-cil libmono-tasklets4.0-cil libmono-webbrowser4.0-cil
  libmono-xbuild-tasks4.0-cil libmonoboehm-2.0-1 libmonoboehm-2.0-dev libmonosgen-2.0-1 libmoo-perl libmount1 libmp4v2-2 
  libncursesw5:i386 libnepomuk4 libnepomukquery4a libnepomukutils4 libnet-http-perl libnettle6 libnettle6:i386 libnewt0.5
  libpam-systemd libpangomm-1.4-1 libpci-dev libpci3 libpci3:i386 libpciaccess0 libpciaccess0:i386 libpcre16-3 libpcre3 l
  libphonon-dev libphonon4 libphonon4qt5-4 libphononexperimental4 libphysfs1 libpipeline1 libplasma3 libplatform1.0 libpo
  libpostproc53 libppl-c4 libppl13 libpsl0 libpulse-mainloop-glib0 libpulse0 libpulse0:i386 libpulsedsp libpulsedsp:i386 
  libqca2 libqca2-plugin-ossl libqca2-plugins libqt4-dbus libqt4-dbus:i386 libqt4-declarative libqt4-designer libqt4-dev 
  libqt4-network:i386 libqt4-opengl libqt4-opengl:i386 libqt4-opengl-dev libqt4-qt3support libqt4-script libqt4-scripttoo
  libqt4-xml libqt4-xml:i386 libqt4-xmlpatterns libqt4-xmlpatterns:i386 libqt5clucene5 libqt5concurrent5 libqt5core5a lib
  libqt5designercomponents5 libqt5gui5 libqt5help5 libqt5multimedia5 libqt5multimediaquick-p5 libqt5network5 libqt5opengl
  libqt5quickparticles5 libqt5quicktest5 libqt5quickwidgets5 libqt5script5 libqt5scripttools5 libqt5sql5 libqt5sql5-sqlit
  libqt5widgets5 libqt5x11extras5 libqt5xml5 libqtassistantclient4 libqtcore4 libqtcore4:i386 libqtdbus4 libqtdbus4:i386 
  libqtwebkit4:i386 libquadmath0 libreoffice libreoffice-avmedia-backend-gstreamer libreoffice-base libreoffice-base-core
  libreoffice-common libreoffice-core libreoffice-draw libreoffice-help-de libreoffice-impress libreoffice-java-common li
  libreoffice-report-builder-bin libreoffice-style-galaxy libreoffice-writer librrd4 librsvg2-2 librsvg2-common libruby2.
  libsensors4 libsensors4-dev libshhmsg1 libsmartcols1 libsolid4 libsoprano4 libsp1c2 libspice-server1 libsqlite3-0 libsq
  libstoken1 libstrigiqtdbusclient0 libstringtemplate4-java libsvn-java libsvn1 libswresample-dev libswresample1 libswres
  libtaoframework-openal1.1-cil libthreadweaver4 libtinfo-dev libtinfo5 libtinfo5:i386 libtsan0 libturbojpeg0 libubsan0 l
  libusb-0.1-4 libusb-0.1-4:i386 libuuid1 libuuid1:i386 libvisio-0.1-1 libvlc-dev libvlc5 libvlccore8 libwayland-egl1-mes
  libwxbase2.8-0 libwxgtk2.8-0 libx264-dev libxatracker2 libxaw7 libxaw7:i386 libxrandr-dev libxrandr2 libxrandr2:i386 li
  linux-image-siduction-amd64 linux-libc-dev live-build lm-sensors lsb-base lsb-release lua5.1 lua5.2 lvm2 lzip man-db me
  modemmanager mono-4.0-gac mono-4.0-service mono-csharp-shell mono-gac mono-jay mono-mcs mono-runtime mono-runtime-commo
  monodoc-manual mount mpv ncompress ncurses-base ncurses-bin network-manager ntp oracle-java8-installer p7zip-rar padevc
  php5-cgi php5-cli php5-common php5-dev pinentry-gtk2 playonlinux poedit-common poppler-utils pulseaudio pulseaudio-modu
  pulseaudio-module-zeroconf pulseaudio-utils putty putty-tools python-apt python-apt-common python-cryptography python-d
  python-numpy python-pil python-pkg-resources python-psutil python-pyasn1 python-qt4 python-qt4-dbus python-twisted pyth
  python-twisted-lore python-twisted-mail python-twisted-names python-twisted-news python-twisted-runner python-twisted-w
  python3-pkg-resources python3-uno python3.4 python3.4-minimal qdbus qdbus-qt5 qml-module-qtgraphicaleffects qml-module-
  qml-module-qtquick-dialogs qml-module-qtquick-layouts qml-module-qtquick-privatewidgets qml-module-qtquick-window2 qml-
  qt4-dev-tools qt4-doc qt4-doc-html qt4-linguist-tools qt4-qmake qt5-default qt5-qmake qtbase5-dev qtbase5-dev-tools qtb
  qtcreator-doc qtcurve-l10n qtdeclarative5-dev qtdeclarative5-dev-tools qtdeclarative5-doc qtenginio5-doc qtmultimedia5-
  qtwebkit5-doc qtxmlpatterns5-doc rar reiserfsprogs ruby2.1 scdaemon sensord sharutils signing-party smartmontools sopra
  subversion systemd systemd-sysv telnet texlive-base texlive-fonts-recommended texlive-generic-recommended texlive-latex
  tzdata-java udev udisks2 unace uno-libs3 unrar unzip ure usbutils util-linux uuid-dev v4l2loopback-source v4l2loopback-
  whiptail whois x264 xfsprogs xserver-common xserver-xorg-core xvfb zip
879 aktualisiert, 64 neu installiert, 60 zu entfernen und 3 nicht aktualisiert.
Es müssen noch 1.080 MB von 1.084 MB an Archiven heruntergeladen werden.
Nach dieser Operation werden 291 MB Plattenplatz zusätzlich benutzt.
 
 
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: melmarker on 2015/08/18, 14:48:22
if no bad things happend, it may be safe to do a full upgrade in 2 or 3 month
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: CCarpenter on 2015/08/18, 15:01:10
Thanks Alfgaida
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: kokurya on 2015/08/18, 16:15:40
We are using SID. Who wants safe ;)
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: melmarker on 2015/08/18, 17:23:17
Those who are working with their systems 8)
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: ghstryder on 2015/08/18, 18:31:03
I view this as (and I include myself in this group) "if you have to ask you need to wait".
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: melmarker on 2015/08/19, 01:28:49
a few losses will be in every transition - but one may change the losses into wins - for me that means that i dropped multi-arch, use the new beta beyond compare (amd64) instead of i386, lost teamviewer which can run in a Windows VM and be done with it - ymmv. The problem with the transition is, that not only some programs and libraries will be recompiled - some projects and maintainers use the transition to get current code into debian, which make sense. But new programs and libraries can introduce a lot of new bugs ...
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: cas on 2015/08/20, 04:30:05
@zephyr
Accidentally you must have overlooked the post of "cas" in this very thread:

« Reply #53 on: 2015/08/11, 09:46:23 »

credit is due to "dibl" reply #14
http://forum.siduction.org/index.php?topic=5719.msg46713#msg46713
 8)
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: vilde on 2015/08/21, 19:59:00
Today’s d-u brought in a working audacious
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: melmarker on 2015/08/21, 20:09:59
@vilde: right, I was too busy to upload it earlier - but for now it is only amd64, i must fix the some symbols for gcc5 today evening
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: vilde on 2015/08/21, 20:31:27
@vilde: right, I was too busy to upload it earlier - but for now it is only amd64, i must fix the some symbols for gcc5 today evening

Thank you melmarker
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: melmarker on 2015/08/21, 21:02:32
@vilde: nothing to thank for  - audacious is my third important program after qterminal and inkscape 8)
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: reddark on 2015/08/21, 23:48:15
@vilde: right, I was too busy to upload it earlier - but for now it is only amd64, i must fix the some symbols for gcc5 today evening
menno, die googleübersetzung dazu:
Recht, ich war zu beschäftigt, um es zu früheren Antriebskraft - aber jetzt ist es nur amd64, ich muss die einige Symbole für gcc5 heute Abend fix

Ehrlich, als nicht englischsprachiger ist es manchmal echt schwer euch zu folgen ... war aptosid nicht auch komplett auf englisch (oh böser wink ) ;)


Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: musca on 2015/08/22, 09:37:51
Hallo reddark,

da hat google translator sich wohl an Melmarkers deutschem Akzent verschluckt:
melmarker hat nur bestätigt, dass er audacious (zunächst nur für die amd64-Architektur) hochgeladen hat und noch weiter daran arbeitet.

Grüße
musca
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: melmarker on 2015/08/22, 10:46:22
also ich find die Übersetzung eingängig, gehaltvoll und gut verständlich :)
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: reddark on 2015/08/22, 23:25:15
*grins*

und nu zurück zum Thema ... ;)
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: drb on 2015/08/24, 10:52:45
After three weeks at 47-48 to remove a sudden jump up to 250 to remove today!
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: dibl on 2015/08/24, 13:44:37
Today the transition is showing 21% complete -- still making about 1% per day since 1 AUG.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: melmarker on 2015/08/24, 17:19:00
@dibl - once the most libraries are done (and working) things will speed up.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: vilde on 2015/08/30, 00:44:18
Until for two days ago I have manage to d-u every or every second day without loosing any packages that where not changed to new versions ( I know that it's not safe anyway, as this thread says) but since the last two days there is one package that is going away and no new one is coming, it's libavfilter5. Sometimes there are packages that are not needed anymore, is that the case for libavfilter5? If not, I will wait.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: melmarker on 2015/08/30, 01:46:19
libavfilter hopefully never come back - it is now libavfilter-ffmpeg5
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: seasons on 2015/08/30, 07:47:00
^What he said, or more generally:
https://lists.debian.org/debian-devel-announce/2015/07/msg00001.html
https://release.debian.org/transitions/html/ffmpeg-libav.html
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: vilde on 2015/08/30, 09:30:25
libavfilter hopefully never come back - it is now libavfilter-ffmpeg5
^What he said, or more generally:
https://lists.debian.org/debian-devel-announce/2015/07/msg00001.html (https://lists.debian.org/debian-devel-announce/2015/07/msg00001.html)
https://release.debian.org/transitions/html/ffmpeg-libav.html (https://release.debian.org/transitions/html/ffmpeg-libav.html)
Ok, thanks, I thought it could be something like that, I now I had libavfilter-ffmpeg5, that's why I asked :)
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: vilde on 2015/09/01, 16:33:13
today, gparted will be removed, I wait a while.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: ralul on 2015/09/01, 23:22:22
gparted has included much c++ related gui things. Try gdisk which extends the old bios related fdisk.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: vilde on 2015/09/02, 23:01:04
gparted has included much c++ related gui things. Try gdisk which extends the old bios related fdisk.
Do you say that I shall let gparted go?

For now, I will wait and see if gparted will be fixed.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: melmarker on 2015/09/02, 23:07:35
gparted should be fine again
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: ralul on 2015/09/03, 00:50:14
Debian sid get pullable again: I just could install kaffeine again and running it
 in my new Gnome-3.16 environment. (first Gnome-3 bug free for me)

I had purged all of Kde in the last weeks to get free of conflicts.
Now dolphin also seems to be installable also. Though I must say
I had to purge a lot of libs which have replacements containing 'v5'
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: holgerw on 2015/09/03, 07:28:49
Debian sid get pullable again: I just could install kaffeine again and running it
 in my new Gnome-3.16 environment. (first Gnome-3 bug free for me)

I had purged all of Kde in the last weeks to get free of conflicts.
Now dolphin also seems to be installable also. Though I must say
I had to purge a lot of libs which have replacements containing 'v5'

Hi Ralph,

yesterday evening I try a D-U after replace snapshot-repo with normal debian unstable repo. But a lot of KF5 stuff should be removed, also dolphin. And some stuff, from which dolphin depends, was not installable because of broken dependencies, with enabled kdenext ca. 40 packages should be removed, without kdenext over 60 packages.

Or should I remove KDE completely and try a reinstallation?

Kind regards,
  Holger
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: vilde on 2015/09/03, 09:37:39
gparted should be fine again
Yes, now it's only testdisk that will be removed, I let that go, it's not the first time testdisk is gone away. d-u went well and gparted upgraded.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: der_bud on 2015/09/03, 10:37:17
... I had purged all of Kde in the last weeks to get free of conflicts. Now dolphin also seems to be installable also. ...

... a lot of KF5 stuff should be removed, also dolphin. And some stuff, from which dolphin depends, was not installable because of broken dependencies, with enabled kdenext ca. 40 packages should be removed, without kdenext over 60 packages ...

Please regard and be warned that it depends on your personal package collection, architecture (i386/amd64) and sources (+/- kdenext) if you get a working KDE system or not. On several irc channels some people report success, some breakage, and it changes every six hours with new mirror syncs. I tried updating kdenext in a VM yesterday and still confirm holgerw's observation of several broken dependencies. So no general 'all-clear' from my side...
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: ralul on 2015/09/04, 01:25:46
Just claiming: I do have a fresh installed kaffeine in a Gnome environment.
Not more ....
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: drb on 2015/09/04, 10:00:45
[SOLVED]
I've now exceeded my konsole scrollback buffer so I can't see the whole list of what would be removed. Is there another way of viewing packages to be in stalled / removed or a way of increasing the text buffer size? (Currently 70 to remove).

PS [EDIT] solved by editing scrolling tab in profile edit
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: paxmark2 on 2015/09/04, 14:02:52
drb  for me when I run "apt-get -s upgrade | less" works but of course that might not be inter-reactive and is not permanent. 


Sitting on 345 to upgrade, I can wait. 
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: harley-peter on 2015/09/04, 18:59:22
Hello,

I made a du today on my system with Xfce desktop at my old Toshiba notebook without problems. I tested the major programs (iceweasel, icedove, libreoffice, gimp, gthumb, xsane, networkmanager, gparted ...) and all work fine.

Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: dibl on 2015/09/05, 15:41:34

I have an old Dell laptop that I sometimes use for experiments. It has not been updated for months. Today I got curious about the state of sid and KDE/Plasma 5, so here is what I did (if I am remembering everything):


Code: [Select]
apt-get update
apt-get dist-upgrade
apt-get -f install
apt-get -f install
apt-get -f install
apt-get install libreoffice
apt-get install dolphin
apt-get install plasma-desktop
apt-get install kde-standard
apt-get install kwin-x11
apt-get clean
apt-get dist-upgrade
apt-get -f install
systemctl reboot


There were many scary removals and errors along the way, but apt-get -f install always got past the error.


I was amazed that it came up perfectly to a Plasma 5 desktop.  My early investigation indicates that it is working as expected.  Still no "kdesu" but "gksu" works anyway.


Here is the system:


Code: [Select]
System:    Host: e6500 Kernel: 4.1.6-towo.1-siduction-amd64 x86_64 (64 bit gcc: 5.2.1)
           Desktop: KDE Plasma 5 (Qt 5.4.2) Distro: siduction 13.2.1 December - kde - (201401272125)
Machine:   System: Dell product: Latitude E6500 serial: 7XFD1J1
           Mobo: Dell model: 0PP476 serial: .7XFD1J1.CN129619122714. Bios: Dell v: A14 date: 07/31/2009
CPU:       Dual core Intel Core2 Duo P8600 (-MCP-) cache: 3072 KB
           flags: (lm nx sse sse2 sse3 sse4_1 ssse3 vmx) bmips: 9581
           clock speeds: max: 2401 MHz 1: 1600 MHz 2: 1600 MHz
Graphics:  Card: NVIDIA G98M [Quadro NVS 160M] bus-ID: 01:00.0
           Display Server: X.org 1.17.2 drivers: nouveau (unloaded: fbdev,vesa)
           tty size: 121x60 Advanced Data: N/A for root
Network:   Card-1: Intel 82567LM Gigabit Network Connection driver: e1000e v: 2.3.2-k port: efe0 bus-ID: 00:19.0
           IF: eth0 state: down mac: 00:21:70:d4:d3:04
           Card-2: Broadcom BCM4312 802.11b/g LP-PHY driver: b43-pci-bridge bus-ID: 0c:00.0
           IF: wlan0 state: up mac: xxxxxxxxxxxxxxx
Drives:    HDD Total Size: 120.0GB (40.0% used) ID-1: model: OCZ_VERTEX
Info:      Processes: 193 Uptime: 15 min Memory: 1356.3/3946.5MB Init: systemd runlevel: 5 Gcc sys: 5.2.1
           Client: Shell (bash 4.3.421) inxi: 2.2.26


FYI.  Don't try it if you can't stand a risk.  I'm still wondering whether to try it on my desktop system.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: CCarpenter on 2015/09/05, 16:30:55
Do you have multiarch installed?
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: dibl on 2015/09/05, 16:42:32
Yes.


Code: [Select]
root@e650031m:/# dpkg --print-foreign-architectures
i386


Working further with it, I am seeing occasional flakiness in the GUI display.  Not sure whether it is about nouveau or kwin-x11 -- I guess I will have to do the experiment on another hardware platform to sort that out.


Also, the d-u was done with the dmo repo disabled.

Edit:  I have no idea where the "31m" came from, on root's address.  The hostname still reports it as "e6500", and a user prompt is "@e6500".  Looks like an error in root's bashrc.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: vayu on 2015/09/05, 20:53:51
 
Code: [Select]
1111 upgraded, 102 newly installed, 117 to remove and 9 not upgraded.
Need to get 1,307 MB of archives.
After this operation, 48.5 MB of additional disk space will be used.
Do you want to continue? [Y/n] n
 


My system is still a ways off from being able to du.  Is it safe to manually upgrade packages that are reported as upgradable, for example claws mail or google chrome?  What about kernel upgrade?
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: vilde on 2015/09/05, 21:12:52
I don't think there will be a point where no packages are to be removed, a lot of packages will be removed and replaced with new ones.

Maybe somebody who knows better can tell me the difference between when apt remove packages and replace them with new vs just upgrade a package?
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: bullgard4 on 2015/09/05, 22:06:19
Until for two days ago I have manage to d-u every or every second day without loosing any packages that where not changed to new versions ( I know that it's not safe anyway, as this thread says)
[siduction december Xfce amd64 X201] '# apt-get -s dist-upgrade' outputs:
"525 aktualisiert, 62 neu installiert, 45 zu entfernen und 0 nicht aktualisiert.
Die folgenden Pakete werden ENTFERNT:"
It lists 44 libraries plus only one program »xnoise«. I can dispense with xnoise for a while.
Can I dare to dist-upgrade?
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: melmarker on 2015/09/05, 22:25:27
ja, kannste - und xnoise wird auch nicht wiederkommen, es schwimmt mit dem Bauch nach oben
---
yes, you can - and xnoise will don't come back, it's dead as can be.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: dibl on 2015/09/05, 22:48:04

Quote
author=dibl link=topic=5719.msg47205#msg47205 date=1441464152]


I guess I will have to do the experiment on another hardware platform to sort that out.

OK, a second d-u experience to report, on my main desktop rig.  This one was longer and considerably more difficult, but in the end it is fully upgraded and running a Plasma 5 desktop with no apparent problems.  Here are the highlights:

- at a point very early in the process the configuration of an updated new udev package hung with a "connection timed out" error.  I lost a lot of time trying different apt and dpkg commands to make it proceed before I discovered that systemctl could not tell me anything about my system, nor could it shut my system down.  So there was a major systemd malfunction and there was no way to proceed except to press the reset button, boot a live USB stick and run gparted to check my filesystems, and try a reboot.  It came up all the way to a Plasma 5 desktop which was fairly amazing.  I went back to tty1 and continued the d-u.

- later in the d-u after the big removals, kde-standard, dolphin, and plasma-desktop refused to install or update.  It took a lot dependency chasing and comparisons to my updated Dell laptop to figure out that phonon4qt5 was at the heart of the problem.  I installed phonon4qt5-backend-gstreamer and then the others installed including libreoffice.  phonon4qt5-backend-vlc appears to be uninstallable at this moment.  Also don't forget to install systemsettings -- it disappeared during the process and had to be reinstalled.

- the final reboot brought me to a clean default Plasma 5 breeze desktop.  At first I thought was a different behavior than I had on the laptop, but then I realized I had never customized the desktop on the laptop.  Probably it overwrote the old desktop and I did not notice a difference.  But my big rig was highly customized with a slideshow that used webcam images and a desktop cube and login music, so all that has to be redone.

Here are the system specs for this one:

Code: [Select]
System:    Host: Hibiscus Kernel: 4.1.6-towo.1-siduction-amd64 x86_64 (64 bit gcc: 5.2.1)
           Desktop: KDE Plasma 5 (Qt 5.4.2)
           Distro: siduction 14.1.0 Indian Summer - kde - (201411230337)
Machine:   System: ASUS product: All Series
           Mobo: ASUSTeK model: Z87-WS v: Rev 1.xx
           Bios: American Megatrends v: 2004 date: 06/05/2014
CPU:       Quad core Intel Core i7-4770 (-HT-MCP-) cache: 8192 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 28022
           clock speeds: max: 3900 MHz 1: 3360 MHz 2: 3399 MHz 3: 3362 MHz 4: 3601 MHz
           5: 3402 MHz 6: 3401 MHz 7: 3400 MHz 8: 3476 MHz
Graphics:  Card: NVIDIA GM107 [GeForce GTX 750 Ti] bus-ID: 05:00.0
           Display Server: X.Org 1.17.2 driver: nvidia Resolution: 1920x1200@59.88hz
           GLX Renderer: GeForce GTX 750 Ti/PCIe/SSE2
           GLX Version: 4.5.0 NVIDIA 346.82 Direct Rendering: Yes
Network:   Card-1: Intel I210 Gigabit Network Connection
           driver: igb v: 5.2.15-k port: d000 bus-ID: 07:00.0
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: xxxxxxxxxxxxx
           Card-2: Intel I210 Gigabit Network Connection
           driver: igb v: 5.2.15-k port: a000 bus-ID: 0a:00.0
           IF: eth1 state: down mac: xxxxxxxxxxxxxxxxxx
Drives:    HDD Total Size: 3120.7GB (25.4% used) ID-1: model: OCZ
           ID-2: model: OCZ ID-3: model: WDC_WD1001FALS
           ID-4: model: WDC_WD1000DHTZ ID-5: model: WDC_WD1000DHTZ
Info:      Processes: 267 Uptime: 1:02 Memory: 2257.6/7927.6MB
           Init: systemd runlevel: 5 Gcc sys: 5.2.1
           Client: Shell (bash 4.3.421) inxi: 2.2.28


Note that the libstdc++6 transition is only showing 30% complete, so further breakages are likely.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: bullgard4 on 2015/09/06, 00:31:26
yes, you can - and xnoise will don't come back, it's dead as can be.
The dist-ugrade went smoothly. So far everything I tested works all right after the dist-upgrade.
Thank you.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: ralul on 2015/09/06, 11:37:15
Debian introduced an extra name ending for packages, which already have transitioned but old libs have to stay:
Code: [Select]
apt-cache search 'v5'|sed -n -e's/v5 - .*//p'|while read a;do [ -f "/var/lib/dpkg/info/${a}.md5sums" ]&&echo "avail_v5 $a ${a}v5";done

If you want to d-u probably the old libs are blocking.

aptitude is showing kde-full installable again. (But I have not tested it is runable yet)
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: vilde on 2015/09/06, 12:55:48
Today I did a full d-u on my other two daily used laptops here. About 45 packages removed, some over 60 new packages, a lot of upgrades and I was to lazy to check if all the removed packages was replaced with new ones. Everything looks fine so far, together with my main laptop we now have three xfce computers fully upgraded.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: devil on 2015/09/06, 16:05:06
I did a dist-upgrade on my workstation today by mistake. I was wanting to upgrade December KDE in VBox to see how that would go. I used the wrong konsole and, doing other things at the same time, when I realized it it was too late. So I got through the dist upgrade, installing ~ 900 packages and rfemoving ~ 90, I could finish the upgrade. Trying to install kde-standard has me running into a wall though. It all boils down to kactivities. It wants to remove kde and other things. So I cannot get plasma-desktop and plasma-workspace installed. So rebooting would leave me with a black screen.


All dependencies of kactivities are installed in the latest version, so I have no clue, where to further investigate. The upgrade in vbox, that I started afterwards went ok. Reboot ended in a black screen, installing kde-standard helped with that. There kactivities got installed fine automaticaly.


Anyone else had encounters of the strange kind with kactivities lately?


greetz
devil
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: ralul on 2015/09/06, 16:40:08
@devil, what does my one liner about 'v5' packages is showing you?
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: piper on 2015/09/06, 18:31:02
Built a Thunderstruck - xorg last night, installed today, working nicely using kde-full, will try kde-standard later

Code: [Select]
piper_test@x1:~$ inxi -FSystem:    Host: x1 Kernel: 4.1.6-towo.1-siduction-amd64 x86_64 (64 bit) Desktop: KDE Plasma 5           Distro: siduction 15.1.0 Thunderstruck - xorg - (201509051137)Machine:   Mobo: Gigabyte model: GA-970A-UD3 v: x.x Bios: Award v: F7 date: 10/22/2012CPU:       Hexa core AMD FX-6300 Six-Core (-MCP-) cache: 12288 KB            clock speeds: max: 3500 MHz 1: 1400 MHz 2: 2000 MHz 3: 1400 MHz 4: 1400 MHz 5: 1400 MHz 6: 1400 MHzGraphics:  Card: NVIDIA GF106 [GeForce GTS 450]           Display Server: X.Org 1.17.2 driver: nvidia Resolution: 1920x1200@59.95hz           GLX Renderer: GeForce GTS 450/PCIe/SSE2 GLX Version: 4.4.0 NVIDIA 340.76Audio:     Card-1 NVIDIA GF106 High Definition Audio Controller driver: snd_hda_intel           Card-2 Advanced Micro Devices [AMD/ATI] SBx00 Azalia (Intel HDA) driver: snd_hda_intel           Sound: Advanced Linux Sound Architecture v: k4.1.6-towo.1-siduction-amd64Network:   Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169           IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: 90:2b:34:a5:99:2dDrives:    HDD Total Size: 8001.6GB (24.0% used) ID-1: /dev/sdc model: ST3000DM001 size: 3000.6GB           ID-2: /dev/sda model: Hitachi_HDS72202 size: 2000.4GB ID-3: /dev/sdb model: ST3000DM001 size: 3000.6GBPartition: ID-1: / size: 50G used: 5.7G (13%) fs: ext4 dev: /dev/sda9           ID-2: swap-1 size: 4.29GB used: 0.00GB (0%) fs: swap dev: /dev/sda1RAID:      No RAID devices: /proc/mdstat, md_mod kernel module presentSensors:   System Temperatures: cpu: 27.2C mobo: N/A gpu: 48C           Fan Speeds (in rpm): cpu: N/AInfo:      Processes: 216 Uptime: 1 min Memory: 964.9/7971.5MB Client: Shell (bash) inxi: 2.2.28 
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: reddark on 2015/09/06, 18:50:39
Hab mich jetzt mutig durchgekämpft und ein D-U durchgezogen. Es wurde erst ne menge entfernt, aber ich konnte es danach wieder installieren. Bis auf wenige Programme die ich zur Zeit eher nicht brauche, läuft alles wieder.
Zur Zeit sieht es nun so bei mir mir aus:

 
Code: [Select]
Paketaktualisierung (Upgrade) wird berechnet... Fertig
Die folgenden Pakete sind zurückgehalten worden:
  kactivities libavcodec-ffmpeg56 libavfilter-ffmpeg5 libavresample-ffmpeg2 libavutil-ffmpeg54 libqapt3 libswresample-ffmpeg1
  python-xapian synaptic zeitgeist-core
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 10 nicht aktualisiert.
 

Mal sehen ob ich noch irgendwo Probleme entdecke. Aber im Moment siehts gut aus ;)
*freu*

Achja P.S:
Hab das ohne kdenext durchgezogen ...
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: dibl on 2015/09/06, 19:15:35
Anyone else had encounters of the strange kind with kactivities lately?


Code: [Select]
root@Hibiscus:/# apt-cache policy kactivities
kactivities:
  Installed: 5.12.0-siduction1
  Candidate: 5.13.0-1
  Version table:
     5.13.0-1 0
        500 http://http.debian.net/debian/ unstable/main amd64 Packages
 *** 5.12.0-siduction1 0
        500 http://packages.siduction.org/kdenext/ unstable/main amd64 Packages
        100 /var/lib/dpkg/status


So I'm not going to upgrade it yet.


A dependency of a dependency of a dependency of kde-standard is a phonon4qt5 package.  It says you need to install one of the backends and the vlc backend is not installable so you are stuck with the gstreamer backend.  Also, you need to remove kwin and replace it with kwin-x11.  I think that is all you need to do.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: piper on 2015/09/06, 20:24:19
kwin-common kwin-data kwin-x11

root@x1:/home/piper_test# apt-get install phonon-backend-vlc vlc-plugin-notify

 
Code: [Select]
Reading package lists... DoneBuilding dependency tree       Reading state information... DoneThe following extra packages will be installed:  fonts-freefont-ttf libbasicusageenvironment0 libcddb2 libchromaprint0 libdvbpsi10 libebml4v5 libfreerdp-cache1.1 libfreerdp-client1.1 libfreerdp-codec1.1  libfreerdp-common1.1.0 libfreerdp-core1.1 libfreerdp-crypto1.1 libfreerdp-gdi1.1 libfreerdp-locale1.1 libfreerdp-primitives1.1 libfreerdp-utils1.1 libgles1-mesa  libgroupsock1 libiso9660-8 libkate1 liblivemedia23 libmatroska6v5 libproxy-tools libsdl-image1.2 libusageenvironment1 libva-drm1 libvcdinfo0 libvlc5 libvlccore8  libwinpr-crt0.1 libwinpr-crypto0.1 libwinpr-dsparse0.1 libwinpr-environment0.1 libwinpr-file0.1 libwinpr-handle0.1 libwinpr-heap0.1 libwinpr-input0.1  libwinpr-interlocked0.1 libwinpr-library0.1 libwinpr-path0.1 libwinpr-pool0.1 libwinpr-registry0.1 libwinpr-rpc0.1 libwinpr-sspi0.1 libwinpr-synch0.1  libwinpr-sysinfo0.1 libwinpr-thread0.1 libwinpr-utils0.1 vlc vlc-data vlc-noxSuggested packages:  libchromaprint-tools python-acoustid freerdp-x11 videolan-doc libdvdcss2Recommended packages:  vlc-plugin-sambaThe following NEW packages will be installed:  fonts-freefont-ttf libbasicusageenvironment0 libcddb2 libchromaprint0 libdvbpsi10 libebml4v5 libfreerdp-cache1.1 libfreerdp-client1.1 libfreerdp-codec1.1  libfreerdp-common1.1.0 libfreerdp-core1.1 libfreerdp-crypto1.1 libfreerdp-gdi1.1 libfreerdp-locale1.1 libfreerdp-primitives1.1 libfreerdp-utils1.1 libgles1-mesa  libgroupsock1 libiso9660-8 libkate1 liblivemedia23 libmatroska6v5 libproxy-tools libsdl-image1.2 libusageenvironment1 libva-drm1 libvcdinfo0 libvlc5 libvlccore8  libwinpr-crt0.1 libwinpr-crypto0.1 libwinpr-dsparse0.1 libwinpr-environment0.1 libwinpr-file0.1 libwinpr-handle0.1 libwinpr-heap0.1 libwinpr-input0.1  libwinpr-interlocked0.1 libwinpr-library0.1 libwinpr-path0.1 libwinpr-pool0.1 libwinpr-registry0.1 libwinpr-rpc0.1 libwinpr-sspi0.1 libwinpr-synch0.1  libwinpr-sysinfo0.1 libwinpr-thread0.1 libwinpr-utils0.1 phonon-backend-vlc vlc vlc-data vlc-nox vlc-plugin-notify0 upgraded, 53 newly installed, 0 to remove and 0 not upgraded.Need to get 20.2 MB of archives.After this operation, 71.9 MB of additional disk space will be used.
Works well


Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: dibl on 2015/09/06, 22:03:56
Hmmmm.

Code: [Select]
root@Hibiscus:/# apt-get -s install phonon-backend-vlc
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 phonon-backend-vlc : Depends: vlc-nox but it is not going to be installed
E: Unable to correct problems, you have held broken packages.


Chasing the dependencies to ...

Code: [Select]
root@Hibiscus:/# apt-get -s install libtag1v5-vanilla
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages will be REMOVED:
  dolphin juk kde-baseapps kde-plasma-desktop kde-standard libbaloowidgets4
  libkfilemetadata4 libtag1-vanilla libtag1c2a
The following NEW packages will be installed:
  libtag1v5-vanilla
0 upgraded, 1 newly installed, 9 to remove and 28 not upgraded.
Remv kde-standard [5:89]
Remv kde-plasma-desktop [5:89]
Remv kde-baseapps [4:15.04.3-siduction1]
Remv dolphin [4:15.04.3-siduction1]
Remv juk [4:15.04.3-siduction1]
Remv libbaloowidgets4 [4:4.14.3-siduction1]
Remv libkfilemetadata4 [4:4.14.3-siduction1]
Remv libtag1c2a [1.9.1-2.1]
Remv libtag1-vanilla [1.9.1-2.1]
Inst libtag1v5-vanilla (1.9.1-2.4 Debian:unstable [amd64])
Conf libtag1v5-vanilla (1.9.1-2.4 Debian:unstable [amd64])

Obviously there's more to know about this situation.


@piper, two questions.

(1) Is it a multiarch system?
(2) Are the gstreamer plugins installed?

Here, vlc is not installable for the same reason as above. Kaffeine is sufficient for my purposes.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: devil on 2015/09/06, 22:43:09
Besides kactivities libtag1v5-vanilla is another endpoint also for me. I spent about 3 hours of chasinf dependencies today to no real avail.


greetz
devil




Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: dibl on 2015/09/06, 23:01:01
It is over 24 hours since I did the full dist-upgrade yesterday, so I checked the status of my desktop system just now.


Code: [Select]
root@Hibiscus:/# 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:
  libmsn0.3
The following NEW packages will be installed:
  libmsn0.3v5
The following packages have been kept back:
  kactivities libavfilter-ffmpeg5 python-xapian
The following packages will be upgraded:
  aptitude-common cdebootstrap grub-common grub-efi-amd64-bin grub-efi-ia32-bin grub-pc
  grub-pc-bin grub2-common guile-2.0-libs isc-dhcp-client isc-dhcp-common kopete
  kwin-common kwin-data kwin-x11 libkopete4 libkwin4-effect-builtins1 libkwineffects6
  libkwinglutils6 libkwinxrenderutils6 libprocps4 libtbb2 network-manager-openvpn procps
  python-cairo
25 upgraded, 1 newly installed, 1 to remove and 3 not upgraded.


So here, a newer version of kactivities is being held back by dpkg.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: harley-peter on 2015/09/07, 19:52:23
Habe heute mein zweites Laptop mit Xfce-Umgebung einem du unterzogen, ebenfalls ohne Probleme. Auch hier scheinen die alle Standard-Programme zu funktionieren.

Today I made a du on my second laptop with Xfce without any problems.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: NochEinNeuer on 2015/09/07, 20:25:37
Ich erhalte Fehler bei einem dist-upgrade....ich wollte zumindest mal einen großteil der Dateien downloaden und vor der installation abbrechen.
Allerdings erhalte ich bei einem apt-get dist-upgrade -d folgende Meldung und auch bei anderen Paketen kommt diese Meldung:


Code: [Select]
Holen: 10 http://http.debian.net/debian/ unstable/main ncurses-bin amd64 6.0+20150810-1 [353 kB]
Holen: 11 http://http.debian.net/debian/ unstable/main tar amd64 1.28-1 [709 kB]
Fehl http://http.debian.net/debian/ unstable/main lib32gcc1 amd64 1:5.2.1-15   
  404  Not Found
Fehl http://http.debian.net/debian/ unstable/main libitm1 amd64 5.2.1-15       
  404  Not Found
Holen: 12 http://http.debian.net/debian/ unstable/main libboost-date-time1.58.0 amd64 1.58.0+dfsg-3 [41,8 kB]



Beim apt-get update erhalte ich folgendes:
Code: [Select]
Es wurden 1.222 kB in 19 s geholt (61,7 kB/s).
W: Fehlschlag beim Holen von http://http.debian.net/debian/dists/unstable/main/binary-amd64/PackagesIndex  Hash-Summe stimmt nicht überein

W: Fehlschlag beim Holen von http://http.debian.net/debian/dists/unstable/main/i18n/Translation-enIndex  Hash-Summe stimmt nicht überein

E: Einige Indexdateien konnten nicht heruntergeladen werden. Sie wurden ignoriert oder alte an ihrer Stelle benutzt.



Wo liegt der Fehler?
danke,

Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: NochEinNeuer on 2015/09/07, 21:43:13
Den Fehler konnte ich mit Hilfe eines Forumsbeitrages aus 2014 beheben.


Ein dist-upgrade (xfce) führte ich durch. Nach einem Neustart scheint alles zu laufen.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: orinoco on 2015/09/07, 22:43:44
I did a d-u this evening and lost my window decoration (can't move, close, resize and hide window).  :(

I kwin-x11 was deleted here. Reinstalling fixed the problem. Puh!!
 
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: piper on 2015/09/08, 00:28:00
dibl, sorry for the late reply

Quote
@piper, two questions.

(1) Is it a multiarch system?
(2) Are the gstreamer plugins installed?

Here, vlc is not installable for the same reason as above. Kaffeine is sufficient for my purposes.

gstreamer-plugins default with non-multiarch  using xorg with kde-standard as the only package being built as I type this, 2 days ago I used kde-full (works well for me)

Code: [Select]
libgstreamer-plugins-base0.10-0 libgstreamer-plugins-base1.0-0 libgstreamer0.10-0 libgstreamer1.0-0



I had a nightmare doing a dist-upgrade on my main box (muilti-arch) , like devil said, a few hours, I am rolling now, and I think a build is better than fixing a dist-upgrade.

The transition is not over, so don't really expect a "official"  build any time soon.

You best know what your doing to do a du and survive

I had

Code: [Select]
963 upgraded, 89 newly installed, 83 to remove and 3 not upgraded.
Need to get 865 MB of archives.
After this operation, 198 MB of additional disk space will be used.

Using xorg, kde-standard without kde-next builds fine and installs in 3 minutes, those with ssd's possibly a lot less

 
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: dibl on 2015/09/08, 01:17:29
I've got a bit of an issue with the optical drive on my desktop rig -- device notifier is oblivious as to whether I have inserted anything.  Dolphin sees an audio CD and I can play it with xine/gxine but not kaffeine any more, and vlc is uninstallable due to the libtag1v5-vanilla issue.  Otherwise everything seems to work as expected -- at least the bits that I need.  My two laptops seem to be taking the dist-upgrades better than my desktop -- they have no apparent issues at all.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: piper on 2015/09/08, 01:58:24
VLC works fine here, but, you all know I use and build with dmo

apt-cache policy vlc

Code: [Select]
vlc:
  Installed: 1:2.2.1-dmo10
  Candidate: 1:2.2.1-dmo10
  Version table:
 *** 1:2.2.1-dmo10 0
        500 http://www.deb-multimedia.org/ sid/main amd64 Packages
        100 /var/lib/dpkg/status
     2.2.1-3 0
        500 http://httpredir.debian.org/debian/ unstable/main amd64 Packages

apt-cache policy libtag1v5-vanilla

Code: [Select]
libtag1v5-vanilla:
  Installed: 1.9.1-2.4
  Candidate: 1.9.1-2.4
  Version table:
 *** 1.9.1-2.4 0
        500 http://httpredir.debian.org/debian/ unstable/main amd64 Packages
        100 /var/lib/dpkg/status

My next build  (tonight) I will build without dmo
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: drb on 2015/09/08, 10:50:44
I'm still up to 86 to remove, including gimp, digikam and k3b. I don't understand why I'm told that  vlc (2.2.1-dmo10) is to be removed when I have vlc (2.2.1-dmo6) installed.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: davidb on 2015/09/08, 12:15:14
I couldn't resolve dependency problems until I removed kdenext from my sources list.
After apt-get dist-upgrade, a couple of apt-get -f install (and dist-upgrade again) and reinstalling dolphin, plasma-desktop, kde-standard and kwin-x11 my system runs fine.
I had to take the risk, because after a normal apt-get upgrade 2 days before kwin wasn't working anymore and I couldn't move, close and switch windows.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: holgerw on 2015/09/08, 13:46:42
Hello @piper,

so you think, with fetching a current inofficial siduction build and doing a fresh installation it is possible to get a current KF5 also with k3b, digikam and soundkonverter?

Kind regards,
  Holger
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: melmarker on 2015/09/08, 15:23:09
except of digikam this should be possible
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: piper on 2015/09/08, 15:26:53
Quote from: davidb
I couldn't resolve dependency problems until I removed kdenext from my sources list.
After apt-get dist-upgrade, a couple of apt-get -f install (and dist-upgrade again) and reinstalling dolphin, plasma-desktop, kde-standard and kwin-x11 my system runs fine.
I had to take the risk, because after a normal apt-get upgrade 2 days before kwin wasn't working anymore and I couldn't move, close and switch windows.

Yes, you have to disable kdenext, after a couple hundred (humour) apt-get -f installs this can get your system working again by installing some apps over again or the new ones.

What my du looks like today

Code: [Select]
The following packages will be upgraded:
  libassuan0 libgpg-error0 libgpg-error0:i386 libsvn-perl libsvn1 subversion subversion-tools
7 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: drb on 2015/09/08, 15:31:29
Is that with kde?  A du-dV gives 20 more packages to go without kdenext here.

Does, gimp, digikam and k3b install?
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: piper on 2015/09/08, 15:37:52
Quote from: holgerw
Hello @piper,

so you think, with fetching a current inofficial siduction build and doing a fresh installation it is possible to get a current KF5 also with k3b, digikam and soundkonverter?

Kind regards,
  Holger

Yes this should work. I just built one based on xorg base

kde-baseapps & kde-plasma-desktop

which works beautifully.

I did not build with k3b, digikam, soundkonverter

Will boot into that now and see if installable
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: devil on 2015/09/08, 16:11:13
Digikam is not installable at the moment. It depends on digikam-private-libs:
Code: [Select]
install digikam-private-libs -s
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.       
Statusinformationen werden eingelesen.... Fertig
Einige Pakete konnten nicht installiert werden. Das kann bedeuten, dass
Sie eine unmögliche Situation angefordert haben oder, wenn Sie die
Unstable-Distribution verwenden, dass einige erforderliche Pakete noch
nicht erstellt wurden oder Incoming noch nicht verlassen haben.
Die folgenden Informationen helfen Ihnen vielleicht, die Situation zu lösen:


Die folgenden Pakete haben unerfüllte Abhängigkeiten:
 digikam-private-libs : Hängt ab von: libbaloofiles4 (>= 4:4.12.80) soll aber nicht installiert werden
                        Hängt ab von: libkdcraw23 (>= 4:4.12.3) soll aber nicht installiert werden
                        Hängt ab von: libkdecore5 (>= 4:4.6.2) soll aber nicht installiert werden
                        Hängt ab von: libkdeui5 (>= 4:4.6.3) soll aber nicht installiert werden
                        Hängt ab von: libkdewebkit5 (>= 4:4.4.0) soll aber nicht installiert werden
                        Hängt ab von: libkexiv2-11 (>= 4:4.11.1) soll aber nicht installiert werden
                        Hängt ab von: libkfile4 (>= 4:4.3.4) soll aber nicht installiert werden
                        Hängt ab von: libkhtml5 (>= 4:4.3.4) soll aber nicht installiert werden
                        Hängt ab von: libkio5 (>= 4:4.7.0) soll aber nicht installiert werden
                        Hängt ab von: libknotifyconfig4 (>= 4:4.3.4) soll aber nicht installiert werden
                        Hängt ab von: libkparts4 (>= 4:4.5.85) soll aber nicht installiert werden
                        Hängt ab von: liblensfun0 (>= 0.2. soll aber nicht installiert werden
                        Hängt ab von: libmarblewidget19 (>= 4:4.13.90) soll aber nicht installiert werden
                        Hängt ab von: libopencv-contrib2.4 soll aber nicht installiert werden
                        Hängt ab von: libopencv-core2.4 soll aber nicht installiert werden
                        Hängt ab von: libopencv-imgproc2.4 soll aber nicht installiert werden
                        Hängt ab von: libopencv-objdetect2.4 soll aber nicht installiert werden
                        Hängt ab von: libpgf6 (>= 6.12.24+ds1) soll aber nicht installiert werden
                        Hängt ab von: libqjson0 (>= 0.7.1) soll aber nicht installiert werden
                        Hängt ab von: libqt4-dbus (>= 4:4.5.3) soll aber nicht installiert werden
                        Hängt ab von: libqt4-network (>= 4:4.5.3) soll aber nicht installiert werden
                        Hängt ab von: libqt4-sql (>= 4:4.5.3) soll aber nicht installiert werden
                        Hängt ab von: libqt4-xml (>= 4:4.5.3) soll aber nicht installiert werden
                        Hängt ab von: libqtcore4 (>= 4:4.8.0) soll aber nicht installiert werden
                        Hängt ab von: libqtgui4 (>= 4:4.8.0) soll aber nicht installiert werden
                        Hängt ab von: libqtwebkit4 (>= 2.1.0~2011week13) soll aber nicht installiert werden
                        Hängt ab von: libsolid4 (>= 4:4.3.4) soll aber nicht installiert werden
                        Hängt ab von: libstdc++6 (>= 4.9) soll aber nicht installiert werden
 grub-common : Hängt ab von: gettext-base



K3b and Soundconverter install just fine on a freshly installed indiansummer after a dist-upgrade.


greetz
devil
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: dibl on 2015/09/08, 19:04:54
I finally got vlc and libtag1v5-vanilla installed -- watched dolphin, plasma-desktop, and kde-standard get ripped out but then they reinstalled perfectly.


Does anyone else see an excessive use of CPU resources by kwin-x11?  Here it is a continuous 11% - 15% of CPU.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: piper on 2015/09/08, 19:51:39
htop gives me

1.6 for mem%
0.0 for cpu%
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: dibl on 2015/09/08, 19:54:07
Hmmmmm.  Reinstalled an hp printer and some other configuration stuff, rebooted, and the kwin-x11 issue is gone.  I guess I'll take it for now and watch it.  Thanks piper.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: clubex on 2015/09/09, 11:57:38
Took the plunge and did the du yesterday. Everything seems OK on my KDE system; although I haven't tested much beyond normal eveyday usage. All I lost was Gimp which couldn't be re-installed due to dependancy errors.

I don't think it's a procedure for those of a nervous disposition. I had to do several dist-upgrades including some -f installs. I also had to re-install dolphin, plasma-desktop and kde-standard. But still there were many packages not upgraded.

The problem turned out to be kwin reacting with kwin-x11 (don't know how they both got installed). Once kwin was removed the remainer of packages upgraded easily with merely kactivities and four or five other packages held back. Trying to install kactivities wants to remove many, many packages.

ps. I've got it sIightly wrong. I now remember that it was only kwin that was installed and that was causing the du not to upgrade all the packages. Once Kwin was removed and kwin-x11 installed the full upgrade completed..
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: drb on 2015/09/09, 12:25:59
I've not attempted to d-u since 31 July and, with a kde system, currently have 89 packages to remove. Would an install of kwin-x11 safely allow me to have a clearer view of what is still uninstallable with a d-u, so I will know when it's Ok to take a risk?

apt-get install kwin-x11 kwin-common kwin-data -d gives me :

Code: [Select]
  The following extra packages will be installed:
  breeze breeze-cursor-theme breeze-icon-theme kde-plasma-desktop kde-standard kde-style-breeze kde-style-breeze-qt4 kwin-style-breeze libkdecorations2-5v5 libkdecorations2private5v5
  libkf5waylandclient5 libkf5waylandserver5 libkwin4-effect-builtins1 libkwineffects6 libkwinglutils6 qml-module-qtquick-controls-styles-breeze
Suggested packages:
  orion-gtk-theme kde-l10n kwin-addons
Recommended packages:
  kde-style-qtcurve sddm
The following packages will be REMOVED:
  kwin libkdecorations2-5 libkdecorations2private5
The following NEW packages will be installed:
  kwin-common kwin-x11 libkdecorations2-5v5 libkdecorations2private5v5
The following packages will be upgraded:
  breeze breeze-cursor-theme breeze-icon-theme kde-plasma-desktop kde-standard kde-style-breeze kde-style-breeze-qt4 kwin-data kwin-style-breeze libkf5waylandclient5 libkf5waylandserver5
  libkwin4-effect-builtins1 libkwineffects6 libkwinglutils6 qml-module-qtquick-controls-styles-breeze
15 upgraded, 4 newly installed, 3 to remove and 1009 not upgraded.
Need to get 41.7 MB of archives.
After this operation, 17.0 MB of additional disk space will be used.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: devil on 2015/09/09, 13:42:57
Like Clubex said, not for the faint at heart, but nothing to fear either, if using common sense. From the facts you post, things look ok.


greetz
devil
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: drb on 2015/09/09, 14:52:06
I had to remove kwin manually first, but otherwise still OK. Still 89 packages to remove though so not a lot further forward.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: mylo on 2015/09/09, 23:40:02
Hi all,


regards from Crete, where temperature rises down to 28 C from 35+ C. Sorry for letting out the degree character, but silly Apple Keyboardtech from the 90's does not offer keyboardwise or is hidden for users.


My question as a normal user of siduction on this transition is:
Shall we wait or prepare for a full reinstsllation/setup?


All meanings/recommendations welcome.






Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: devil on 2015/09/09, 23:49:57
Just sit tight.


greetz
devil
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: mylo on 2015/09/10, 14:56:56
That is easy to do, thanks!
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: samoht on 2015/09/10, 16:40:47
@mylo


Why is Apple® keyboard tech silly and not maybe the person in charge of the keyboard?
Apple bashing does not make any sense in this forum.
Greetings
Tom
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: mylo on 2015/09/11, 09:21:45
Hi Samoth,
You are right, but i also...will change Forum for that.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: mylo on 2015/09/11, 09:22:51
Sorry samoht! Apple changed your name...
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: devil on 2015/09/11, 09:28:24
Careful with KDE upgrades today. plasma-widgets-workspace is being removed on some systems and I am sure you want to keep that.


greetz
devil
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: vilde on 2015/09/11, 17:26:18
Today some packages are gone without new ones installed:
Code: [Select]
The following packages will be REMOVED:
  coinor-libcbc3 coinor-libcoinmp1 coinor-libcoinutils3 coinor-libosi1
The following NEW packages will be installed:
  coinor-libcoinutils3v5 coinor-libosi1v5 liblz4-1
Shall they be gone or shall I wait?
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: michaa7 on 2015/09/11, 23:36:42
I did a d-u on my *experimental* system with IDGAS desktop. Nearly a GB of new packages, 54 packages removed. All went well. This system is running without problems AFAICS.

What's keeping me from updating my default system is digikam/showphoto being removed (announced by apt).
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: mylo on 2015/09/12, 00:18:36
Hi michaaa7,

that sounds good. If digikam were all (I think, that can be reinstalled some days later if required), then days come where the d-u can be riked/done/tried.
Or do we get a release signal here for all to d-u?
I have menawhile some effects on my box, I hope to get rid off with the d-u.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: michaa7 on 2015/09/12, 01:04:47
I don't have an ordinary desktop and I don't recomment a d-u for your default and only system. Read what others say like devil about KDE/plasma. Everyone goes ahead at his own risk. So if you feel it is a risk, wait.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: clubex on 2015/09/12, 11:54:11
On my KDE machine and using kdenext repository the following
Code: [Select]
plasma-dataengines-workspace and plasma-widgets-workspace
will be the only packages removed.

As plasma-dataengines-addons and plasma-widgets-addons are to be upgraded I suppose plasma-dataengines-workspace plasma-widgets-workspace will be next or very soon.

Personally I will not du until these two are upgradable.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: dibl on 2015/09/12, 13:24:50

As plasma-dataengines-addons and plasma-widgets-addons are to be upgraded I suppose plasma-dataengines-workspace plasma-widgets-workspace will be next or very soon.



There is no plasma-widgets-workspace package in sid at the moment -- the only one is in kdenext, and it has hard dependency on the versions of plasma-data-engines and libplasmaclock4abi4 that are also in kdenext.  In sid we have newer versions of plasma-dataengines-workspace and libplasmaclock4abi4 packages.


With kdenext repo disabled, I ran d-u and let plasma-widgets-workspace get removed on two KDE/KF5 systems -- a desktop and a laptop -- and I don't see any damage.  I'm not a huge widgets user, however -- maybe it causes a problem for someone.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: piper on 2015/09/12, 14:52:34
Without kde-next

0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded


Code: [Select]
plasma-dataengines-addons:
  Installed: 4:5.4.1-1
  Candidate: 4:5.4.1-1

Code: [Select]
plasma-widgets-addons:
  Installed: 4:5.4.1-1
  Candidate: 4:5.4.1-1





Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: clubex on 2015/09/12, 15:17:24
didl:
I was led to believe that plasma-wigets-workspace was essential to the plasma desktop.
To quote:
https://packages.debian.org/sid/plasma-widgets-workspace
Code: [Select]
This package contains standard Plasma widgets and containments shipped in the KDE base workspace module. They provide such basic desktop functionality as the panel, task manager, application laucher, clock and more. The default KDE Workspace is a combination of these visual components.

I wouldn't want to be without the panel, the task manager or the app launcher..
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: dibl on 2015/09/12, 17:01:01
No @clubex that is an older version even than the version in kdenext.  I can say for sure it is not essential -- I am looking at a kde-plasma-desktop with fully functional panel, kwin-X11, krunner, etc.


Code: [Select]
root@Hibiscus:/# apt-cache policy plasma-widgets-workspace 
plasma-widgets-workspace:
  Installed: (none)
  Candidate: (none)
  Version table:
     4:4.11.22-2 0
        100 /var/lib/dpkg/status                                                                                                     
root@Hibiscus:/# apt-cache policy kde-standard             
kde-standard:
  Installed: 5:90
  Candidate: 5:90
  Version table:
 *** 5:90 0
        500 http://http.debian.net/debian/ unstable/main amd64 Packages
        100 /var/lib/dpkg/status
root@Hibiscus:/# apt-cache policy kde-plasma-desktop       
kde-plasma-desktop:
  Installed: 5:90
  Candidate: 5:90
  Version table:
 *** 5:90 0
        500 http://http.debian.net/debian/ unstable/main amd64 Packages
        100 /var/lib/dpkg/status
root@Hibiscus:/# apt-cache policy kwin-x11
kwin-x11:
  Installed: 4:5.4.1-1
  Candidate: 4:5.4.1-1
  Version table:
 *** 4:5.4.1-1 0
        500 http://http.debian.net/debian/ unstable/main amd64 Packages
        100 /var/lib/dpkg/status
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: clubex on 2015/09/13, 00:18:45
Thanks dibl for pointing that out to me. I went through with the du and indeed found no problems.
 
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: piper on 2015/09/13, 00:27:30
You don't need kde-standard/kde-full either to have a fully functional kde-plasma-desktop  ;)


Desktop: KDE Plasma 5.4.1

Code: [Select]
piper@x1:~$ apt-cache policy kde-standard
kde-standard:
  Installed: (none)
  Candidate: 5:90
  Version table:
     5:90 0
        500 http://httpredir.debian.org/debian/ unstable/main amd64 Packages
piper@x1:~$ apt-cache policy kde-full
kde-full:
  Installed: (none)
  Candidate: 5:90
  Version table:
     5:90 0
        500 http://httpredir.debian.org/debian/ unstable/main amd64 Packages
piper@x1:~$
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: jaegermeister on 2015/09/14, 19:11:05
Hello, this is a today's update on my machine (not du'd since last half July), to be REMOVED items list is further shrinking:

Quote
cheese coinor-libcbc3 coinor-libcoinmp1 coinor-libcoinutils3 coinor-libosi1 digikam digikam-private-libs dvdwizard gimp gimp-gap gimp-gutenprint gimp-plugin-registry gimp-texturize gimp-ufraw gnome-video-effects gstreamer1.0-plugins-bad kde-workspace kde-workspace-bin kde-workspace-data kdebase-workspace-bin kipi-plugins klipper libatkmm-1.6-1 libav-tools libbinio1ldbl libboost-date-time1.55.0 libcairomm-1.0-1 libcheese-gtk23 libcheese7 libclucene-contribs1 libclucene-core1 libcmis-0.5-5 libcrypto++9 libcwidget3 libebml4 libept1.4.12 libffmpegthumbnailer4 libflac++6 libgconfmm-2.6-1c2 libgegl-0.2-0 libglademm-2.4-1c2a libglibmm-2.4-1c2a libgltf-0.0-0 libgnomecanvasmm-2.6-1c2a libgpgme++2 libgtkmm-2.4-1c2a libgtkmm-3.0-1 libid3-3.8.3c2a libilmbase6 libkolab0 libkolabxml1 libkyotocabinet16 libllvm3.5 libllvm3.5:i386 libmatroska6 libmsn0.3 libopenexr6 liborcus-0.10-0 libpangomm-1.4-1 libpcrecpp0 libpodofo0.9.0 libprojectm2 libprotobuf-lite9 libproxy1 libqalculate5 libqpdf13 librlog5 libsearchclient0 libsidplay1 libsidplayfp3 libsigc++-2.0-0c2a libstreamanalyzer0 libstreams0 libstrigihtmlgui0 libtag1-vanilla libtag1c2a libtinyxml2.6.2 libvamp-hostsdk3 libvamp-sdk2 libwxbase3.0-0 libwxgtk3.0-0 libxapian22 lxdvdrip miro pitivi plasma-desktopthemes-artwork plasma-widgets-workspace tribler

It's mostly about libraries. I have updated manually just some CLI utilities and nothing more. Still two things stop me from proceeeding:

1. KDE base files "kde-workspace kde-workspace-bin kde-workspace-data kdebase-workspace-bin" getting wiped away

2. digikam, which I currently use, even if it's some months that it's getting me nuts by not recognizing anymore my Canon S100 which previously did...

Any feedback on these?
THX
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: dibl on 2015/09/14, 19:38:23
Plasma-desktop 5:90 (for amd64 and i386) does not depend on kde-workspace.  After d-u the other day, kde-workspace is no longer installable on my systems, but the kde-plasma-desktop works anyway.


Digikam is not installable, however.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: piper on 2015/09/14, 19:43:12
For digikam, your going to have to wait

As for those KDE base files you list ...

Code: [Select]
piper@x1:~$ apt-cache policy kde-workspace
kde-workspace:
  Installed: (none)
  Candidate: 4:4.11.22-3
  Version table:
     4:4.11.22-3 0
        500 http://httpredir.debian.org/debian/ unstable/main amd64 Packages
piper@x1:~$ apt-cache policy kde-workspace-bin
kde-workspace-bin:
  Installed: (none)
  Candidate: 4:4.11.22-3
  Version table:
     4:4.11.22-3 0
        500 http://httpredir.debian.org/debian/ unstable/main amd64 Packages
piper@x1:~$ apt-cache policy kde-workspace-data
kde-workspace-data:
  Installed: (none)
  Candidate: 4:4.11.22-3
  Version table:
     4:4.11.22-3 0                                                                                                                           
        500 http://httpredir.debian.org/debian/ unstable/main amd64 Packages                                                                 
piper@x1:~$ apt-cache policy kdebase-workspace-bin
kdebase-workspace-bin:
  Installed: (none)
  Candidate: 4:4.11.22-3
  Version table:
     4:4.11.22-3 0
        500 http://httpredir.debian.org/debian/ unstable/main amd64 Packages
piper@x1:~$

Not needed.

If you do a apt-cache search kf5 you can get a general idea on what has changed and what you need.

I will delete your other post if you would like
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: jaegermeister on 2015/09/14, 21:15:04
For digikam, your going to have to wait

As for those KDE base files you list ...

Code: [Select]
piper@x1:~$ apt-cache policy kde-workspace
kde-workspace:
  Installed: (none)
  Candidate: 4:4.11.22-3
  Version table:
     4:4.11.22-3 0
        500 http://httpredir.debian.org/debian/ unstable/main amd64 Packages
piper@x1:~$ apt-cache policy kde-workspace-bin
kde-workspace-bin:
  Installed: (none)
  Candidate: 4:4.11.22-3
  Version table:
     4:4.11.22-3 0
        500 http://httpredir.debian.org/debian/ unstable/main amd64 Packages
piper@x1:~$ apt-cache policy kde-workspace-data
kde-workspace-data:
  Installed: (none)
  Candidate: 4:4.11.22-3
  Version table:
     4:4.11.22-3 0                                                                                                                           
        500 http://httpredir.debian.org/debian/ unstable/main amd64 Packages                                                                 
piper@x1:~$ apt-cache policy kdebase-workspace-bin
kdebase-workspace-bin:
  Installed: (none)
  Candidate: 4:4.11.22-3
  Version table:
     4:4.11.22-3 0
        500 http://httpredir.debian.org/debian/ unstable/main amd64 Packages
piper@x1:~$

Not needed.

If you do a apt-cache search kf5 you can get a general idea on what has changed and what you need.

I will delete your other post if you would like

Yes, you can delete it.
As for KDE5, that query outputs countless libkf5*, some plasma* and baloo4. I cannot yet understand how kde base/meta packages (if they're already available) would be named. Do you have a working KDE5 environment on your screen?
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: jaegermeister on 2015/09/14, 21:20:15
Plasma-desktop 5:90 (for amd64 and i386) does not depend on kde-workspace.  After d-u the other day, kde-workspace is no longer installable on my systems, but the kde-plasma-desktop works anyway.


Digikam is not installable, however.

So is "plasma-desktop" the package that drives the whole story?
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: dibl on 2015/09/14, 22:34:48
Santa and others are far more knowledgeable than me, so don't take this as the expert answer.  But it seems to me you want:


plasma-workspace
plasma-desktop
kde-plasma-desktop
kde-standard (or as piper says, it is not essential if you want only a small set of kde packages)
sddm
kde-config-sddm
kwin-x11


This should result in a workable plasma 5 desktop.  system-settings might get removed -- if so, you can reinstall it after you have the others.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: piper on 2015/09/14, 23:28:00
You can add

kde-baseapps
kde-runtime

I use kde-baseapps instead of kde-standard/full (metapackages) and add what I want as individual packages , half the packages in standard/full I don't use/want. I actually only use 6 packages from standard
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: jaegermeister on 2015/09/15, 00:30:10
Many thanks to both :)

It looks like that kde-plasma-desktop is moving more or less all the necessary dependencies, while kde-baseapps giving what is needed. Considering I have both already installed and going to be updated, it looks like my system is already KDE5-ready :) I will anyway wait more in order for other apps (like digikam and gimp) to settle.

Just one thing looks strange (debian package maintainers fault?): while kde-plasma-desktop clearly rdepends on kde-standard or kde-full, it does NOT on kde-baseapps... what the heck?
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: domicius on 2015/09/15, 18:27:54
Well, on my system, trying to update
Quote
plasma-workspace
plasma-desktop
kde-plasma-desktop
sddm
kde-config-sddm
kwin-x11
kde-baseapps-bin
kde-runtime

apt cries about needing
Quote
plasma-scriptengine-javascript
libopenexr6v5
which are not going to be installed.

Forcing those two then makes the apt complain about libopenexr6v5 conflicting with libopenexr6 and trying to remove that would result in wiping 242 packages.

Simply trying apt-get install plasma-desktop seems it would remove 42 packages, including at least libreoffice, poedit and mysql-workbench. So, no go for me.

Do any of you use libreoffice?

EDIT: forgot to say my system is kdenext enabled.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: dibl on 2015/09/15, 18:36:18
If you want to do the upgrade, you'll have to disable kdenext for now.  I don't see a problem with the packages you named:

Code: [Select]
root@Hibiscus:/# apt-cache policy plasma-scriptengine-javascript 
plasma-scriptengine-javascript:
  Installed: 4:15.08.0-2
  Candidate: 4:15.08.0-2
  Version table:
 *** 4:15.08.0-2 0
        500 http://http.debian.net/debian/ unstable/main amd64 Packages
        100 /var/lib/dpkg/status
root@Hibiscus:/# apt-cache policy libopenexr6v5
libopenexr6v5:
  Installed: 1.6.1-8.1+b2
  Candidate: 1.6.1-8.1+b2
  Version table:
 *** 1.6.1-8.1+b2 0
        500 http://http.debian.net/debian/ unstable/main amd64 Packages
        100 /var/lib/dpkg/status

Yes, there will be removals, but then they will be installable again.  Yes, I have LibreOffice 5 installed:

Code: [Select]
root@Hibiscus:/# apt-cache policy libreoffice 
libreoffice:
  Installed: 1:5.0.1-1
  Candidate: 1:5.0.1-1
  Version table:
 *** 1:5.0.1-1 0
        500 http://http.debian.net/debian/ unstable/main amd64 Packages
        100 /var/lib/dpkg/status

Again, LibreOffice 4.xx will be ripped out during the d-u, then afterward LO 5 can be installed.Notice that all packages are from Debian sid -- you can't have kdenext enabled to do this.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: piper on 2015/09/15, 23:17:27
Without kdenext

Code: [Select]
piper@x1:~$ apt-cache policy plasma-desktop
plasma-desktop:
  Installed: 4:5.4.1-1
  Candidate: 4:5.4.1-1
  Version table:
 *** 4:5.4.1-1 0
        500 http://httpredir.debian.org/debian/ unstable/main amd64 Packages
        100 /var/lib/dpkg/status
piper@x1:~$ apt-cache policy mysql-workbench
mysql-workbench:
  Installed: 6.3.4+dfsg-1+b2
  Candidate: 6.3.4+dfsg-1+b2
  Version table:
 *** 6.3.4+dfsg-1+b2 0
        500 http://httpredir.debian.org/debian/ unstable/main amd64 Packages
        100 /var/lib/dpkg/status
piper@x1:~$ apt-cache policy libreoffice
libreoffice:
  Installed: 1:5.0.1-1
  Candidate: 1:5.0.1-1
  Version table:
     1:5.0.1-1 0
        500 http://httpredir.debian.org/debian/ unstable/main amd64 Packages
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: domicius on 2015/09/17, 20:14:50
Ok, thanks guys! :) Will give it a try tomorrow probably.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: Spike_DE on 2015/09/17, 21:41:39
What do you think, when a "normal" D-U will work again?

1096 aktualisiert, 123 neu installiert, 89 zu entfernen und 7 nicht aktualisiert.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: melmarker on 2015/09/18, 01:22:24
@Spike_DE: Never without manual intervention .. :)
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: piper on 2015/09/18, 01:32:16
Quote from: Spike_DE
What do you think, when a "normal" D-U will work again?

1096 aktualisiert, 123 neu installiert, 89 zu entfernen und 7 nicht aktualisiert.

That's a tough question to answer ;)


It depends if you use kdenext or not

If you do, I cannot answer that, I don't know what Santa has cooking, it is a lot of work, and people need to be patient with kdenext. Santa has done a great job, he is one man and he *might be waiting for the transition to be over, I cannot speak for him.

You can disable kdenext and go with what debian has for now.

Yes, a lot will be removed, just use kate or something similar to copy & paste from terminal on the output of a dist-upgrade and especially what it wants to remove .

Read this thread to see how others have done it

Post any problems, hiccups, etc ... , can't promise,  but, we can probably get you up and running.

The last option is to wait it out, yes, this will take awhile, but, it is the safest. :)

Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: Santa on 2015/09/18, 01:58:41

Hello,


I have been reading many stupid things about KDE here, I was crystal clear from the beginning:
http://forum.siduction.org/index.php?topic=5719.msg46629#msg46629 (http://forum.siduction.org/index.php?topic=5719.msg46629#msg46629)
Quote
Regarding KDE packaging I have been working with a person from debian and kubuntu's people to make the dist-upgrades safe as soon as possible.
Quote

What to do to "survive gracefully":
Do NOT dist-upgrade after July 31 until you find here further instructions, we will keep you posted.



So please stop misleading users and giving bad advices like the one above (meaning http://forum.siduction.org/index.php?topic=5719.msg47413#msg47413 (http://forum.siduction.org/index.php?topic=5719.msg47413#msg47413)), It's not the first time that I see such kind of advices from forum moderators who really know nothing about KDE packaging.



You can disable kdenext and go with what debian has for now.



I was crystal clear about this too:
http://forum.siduction.org/index.php?topic=5719.msg46909#msg46909 (http://forum.siduction.org/index.php?topic=5719.msg46909#msg46909)



P.S.
If you do, I cannot answer that, I don't know what Santa has cooking, it is a lot of work, and people need to be patient with kdenext.
And, last but not least, please stop implying this is a problem specific of kdenext, it's very clear it's a general problem of debian sid.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: piper on 2015/09/18, 04:12:29
Excuse me GOD !

I have 4 WORKING sid systems WITHOUT KDENEXT

Misleading IS KDENEXT  at this moment (who knows the future)

1127 upgraded, 132 newly installed, 89 to remove and 15 not upgraded.

This is  uncalled for


July 30, 2015 that was posted (last time we heard anything from you)

Until kdenext gets it's SHIT together, WE  can and WILL do, what WE want to do to OUR systems, whether you like it or not, whether you think it's bad advise or not

You have showed us nothing up to this point

I tried being nice in the post above, but, your (this) post blew it.

my dist-upgrade

0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Thats also with dmo enabled and these are builds that work also

System:    Host: x1 Kernel: 4.2.0-towo.1-siduction-amd64 x86_64 (64 bit) Desktop: KDE Plasma 5.4.1
           Distro: siduction 15.1.0 Thunderstruck - xorg - (201509110914)

Can you build with kdenext ??     I can't

Yeah, I call that bad advice (yes, it can break in 10 minutes, it's sid)

This ain't about packaging, this is about delivery and what is working and trough the transition

You can't use your system right now

Blow off your steam somewhere else, not here !

Until you have something to show & works

DON'T CALL THIS MISLEADING

You don't need to be a packager or a rocket scientist to see this.



It's not the first time that I have  seen  such a reply from packagers who think they know everything.

In the end, my system works (debian sid)

Does yours ?






Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: sunrat on 2015/09/18, 05:08:13
Chill pill please. I appreciate Santa's hard work, dedication and advice.
Perhaps a new thread would be more appropriate, something like " Workarounds for GCC transition". I appreciate your input as well, piper.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: ayla on 2015/09/18, 06:23:23
Chill pill please. I appreciate Santa's hard work, dedication and advice.
Perhaps a new thread would be more appropriate, something like " Workarounds for GCC transition". I appreciate your input as well, piper.

+1
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: Santa on 2015/09/18, 07:04:18
Excuse me GOD !

I have 4 WORKING sid systems WITHOUT KDENEXT

Misleading IS KDENEXT  at this moment (who knows the future)

1127 upgraded, 132 newly installed, 89 to remove and 15 not upgraded.

This is  uncalled for


Stop spreading FUD. I was very clear saying that it's being worked on.

July 30, 2015 that was posted (last time we heard anything from you)


No. http://forum.siduction.org/index.php?topic=5719.msg46909#msg46909 (http://forum.siduction.org/index.php?topic=5719.msg46909#msg46909)
And it was a direct reply to you, another isssue is if you want to listen or not.

Until kdenext gets it's SHIT together, WE  can and WILL do, what WE want to do to OUR systems, whether you like it or not, whether you think it's bad advise or not

You have showed us nothing up to this point


No. As I said above I was very clear in the first post that the issue with GCC 5 was being worked on, also you can see here a fair number of commits done during all august and part of them during september:
https://gitlab.com/groups/siduction-tools (https://gitlab.com/groups/siduction-tools)
And this is not the only git repositories I have for siduction.
Another different issue is your ignorance about it.

I tried being nice in the post above, but, your (this) post blew it.


Thanks for showing the true face of some people in siduction who aren't really qualified to give advices about KDE.

my dist-upgrade

0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Thats also with dmo enabled and these are builds that work also

System:    Host: x1 Kernel: 4.2.0-towo.1-siduction-amd64 x86_64 (64 bit) Desktop: KDE Plasma 5.4.1
           Distro: siduction 15.1.0 Thunderstruck - xorg - (201509110914)

Can you build with kdenext ??     I can't
My system here works because I followed my own advice of not dist-upgrading siduction KDE systems until the GCC 5 transition is properly settled.


Yeah, I call that bad advice (yes, it can break in 10 minutes, it's sid)

This ain't about packaging, this is about delivery and what is working and trough the transition


Not sure how to reply to this. If the GCC 5 transition and how affects KDE isn't about packaging for you, I don't expect much rationality from you.

You can't use your system right now

Blow off your steam somewhere else, not here !

Until you have something to show & works

DON'T CALL THIS MISLEADING

You don't need to be a packager or a rocket scientist to see this.

Yes, I can use my system (I'm writing using it), your advice of removing kdenext is bad/misleading and the fact that I worked packaging KDE for various distributions in the latest few years is quite helpful to see it.

It's not the first time that I have  seen  such a reply from packagers who think they know everything.

In the end, my system works (debian sid)

Does yours ?


Yes, because I followed my own advice of not dist-upgrading.


P.S. Just for curiosity I tried to dist-upgrade an indiansummer installation without kdenext. I still tries to remove stuff which shoudln't be removed (as expected). Now, if you excuse me I'm going back to work.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: melmarker on 2015/09/18, 09:04:52
Santa: Some people (piper in this case) have a different view to KDE than you - that doesn't mean that your'e allowed to call them morons. Please stop that now and for ever.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: Santa on 2015/09/18, 09:45:53
Santa: Some people (piper in this case) have a different view to KDE than you - that doesn't mean that your'e allowed to call them morons. Please stop that now and for ever.


If some people - who never worked on KDE packaging - have a different view I understand that it's perfectly fine. I also understand t's also perfectly fine to point out that some advices coming from them are bad, without insulting anyone.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: piper on 2015/09/18, 11:43:59
Quote from: Santa
Quote from: melmarker on Today at 03:04:52 AM (http://forum.siduction.org/index.php?topic=5719.msg47420#msg47420)Santa: Some people (piper in this case) have a different view to KDE than you - that doesn't mean that your'e allowed to call them morons. Please stop that now and for ever.

If some people - who never worked on KDE packaging - have a different view I understand that it's perfectly fine. I also understand t's also perfectly fine to point out that some advices coming from them are bad, without insulting anyone.

The only person here giving bad advise here is you




Quote from: "Santa"
Code: [Select]
Thanks for showing the true face of some people in siduction who aren't really qualified to give advices about KDE.
You really want me to go here  ....

If you know so much about packaging and KDE, why did every distro you were involved with dump you, this is including debian itself, god-like attitude maybe ... my way or the highway attitude .. maybe,   should I go on ? ...

You really don't want me to go on ....

Your god like attitude is catching up here also

Quote from: "Santa"
Code: [Select]
Yes, I can use my system (I'm writing using it), your advice of removing kdenext is bad/misleading and the fact that """"I worked packaging KDE for various distributions in the latest few years""" is quite helpful to see it.
And what happened ? again, you don't want me to go there in public.

Quote from: "Santa"

Code: [Select]
No. http://forum.siduction.org/index.php?topic=5719.msg46909#msg46909
And it was a direct reply to you, another isssue is if you want to listen or not.


Regarding KDE, it's not safe to dist-upgrade yet.

Which is utter BULLSHIT

You are banned from everything debian pretty much and that includes irc, you have no-one to blame but yourself ..

If, you were allowed on irc, you would see that this "Regarding KDE, it's not safe to dist-upgrade yet[[/code] is pure horseshit at its purist.


Quote from: "Santa"
Code: [Select]
No. As I said above I was very clear in the first post that the issue with GCC 5 was being worked on, also you can see here a fair number of commits done during all august and part of them during september:
https://gitlab.com/groups/siduction-tools
And this is not the only git repositories I have for siduction.
Another different issue is your ignorance about it.

Well, Duke Nukem was being worked on also

Quote from: "melmarker"

Code: [Select]
Santa: Some people (piper in this case) have a different view to KDE than you - that doesn't mean that your'e allowed to call them morons. Please stop that now and for ever.
thats ok, it's just words, it gives him a hard-on with the superior attitude


Santa, when your project is finished (working) you can post it

Don't butt in on anyone who don't have the same beliefs as you, there are thousands of people that are enjoying debian sid kde (kdf) without kde-next



I build siduction stock, my own gaming, mythtv versions of siduction and quite a few android roms, I feel I know about 1% of anything, yet, I get by.

You really don't want to get in a pissing match with me, if you do, game on, lets have some fun ....
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: devil on 2015/09/18, 11:51:25
Nothing will come of that, so lets stop it here. Thanks :)


greetz
devil
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: horo on 2015/09/18, 12:01:08
Thx devil,

Maybe it's time to split this pinned thread into one "DO NOTHING UNTIL SANTA TELLS US" for the belt-and-suspender-kdenext-follower and another "HOW TO SURVIVE A DU AND HAVE FUN WITH SID" for the more adventurous hacker.

My 2ct.

Ciao, Martin

P.S. to the _whole_ siduction team: Please remember the lessons learned from kanotix and sidux!
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: Santa on 2015/09/18, 13:20:59
You really want me to go here  ....

If you know so much about packaging and KDE, why did every distro you were involved with dump you, this is including debian itself, god-like attitude maybe ... my way or the highway attitude .. maybe,   should I go on ? ...



I will reply you with other question: if debian's people were so right banning me: how it's possible they broke the Plasma 5 upgrade, even while it was perfectly avoidable?


What is catching up here is the same problem than debian and solydk have: being ruled by people who don't do the work but think they know bettter than those who do the work. By the way the very same people that expelled me from debian managed to broke kde - even while they already had the 90% of the work already done in kubuntu (that deserves like some kind of medal). Please see again the corresponding thread:
http://forum.siduction.org/index.php?topic=5644.0 (http://forum.siduction.org/index.php?topic=5644.0)


And what happened ? again, you don't want me to go there in public.


I don't have any problem in talking about my expelling of debian or solydk or my current work on siduction and kubuntu, so I see no point in threatening me about discussing it publicly (I already mentioned it briefly in this forum in other thread).


And by the way I wasn't the only one here banned by debian's people. And I think that's a shame for debian's people and not for the person banned.

Regarding KDE, it's not safe to dist-upgrade yet.

Which is utter BULLSHIT

You are banned from everything debian pretty much and that includes irc, you have no-one to blame but yourself ..

If, you were allowed on irc, you would see that this "Regarding KDE, it's not safe to dist-upgrade yet" is pure horseshit at its purist.


I don't need to be allowed on irc to know that kind of things.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: drb on 2015/09/18, 14:11:03
Thanks for your help getting through kde5. I'm looking forward to you getting us through the current mess. I'm using a fully working non-dued kde install . . . and I need gimp in particular before I risk allowing over-written libs to go.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: dibl on 2015/09/18, 14:37:53
. . . and I need gimp in particular before I risk allowing over-written libs to go.


Code: [Select]
root@Hibiscus:/# apt-cache policy gimp
gimp:
  Installed: 2.8.14-1+b1
  Candidate: 2.8.14-1+b1
  Version table:
 *** 2.8.14-1+b1 0
        500 http://httpredir.debian.org/debian/ unstable/main amd64 Packages
        100 /var/lib/dpkg/status
     2.8.10-0.siduction.1 0
        500 http://packages.siduction.org/extra/ unstable/main amd64 Packages
root@Hibiscus:/# apt-cache policy kde-plasma-desktop
kde-plasma-desktop:
  Installed: 5:90
  Candidate: 5:90
  Version table:
 *** 5:90 0
        500 http://httpredir.debian.org/debian/ unstable/main amd64 Packages
        100 /var/lib/dpkg/status
 
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: dibl on 2015/09/18, 14:46:49
This bug (https://bugs.kde.org/show_bug.cgi?id=348123) still exists, by the way.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: drb on 2015/09/18, 15:04:13
@dibl
This is what my du -dV. gimp being removed and, as of today, libreoffice would also go. Does gimp reinstall after a du?

Code: [Select]
  The following packages will be REMOVED:                                                                                                                                                       
   aptitude (0.7.1-1)                                                                                                                                                                         
   baloo-utils (4.14.3-siduction1)
   coinor-libcoinutils3 (2.9.15-3)
   coinor-libosi1 (0.106.9-1)
   digikam (4.10.0-0u1+siduction1.3)
   digikam-private-libs (4.4.0-1.1+fix4.2)
   dolphin (15.04.3-siduction1)
   gimp (2.8.14-1+b1)
   gimp-ufraw (0.20-3+b1)
   kde-baseapps (15.04.3-siduction1)
   kde-full (90)
   kde-plasma-desktop (90)
   kde-plasma-netbook (88+mod90.11)
   kde-standard (90)
   kde-workspace (5.3.2-siduction1)
   kde-workspace-bin (5.3.2-siduction1)
   kde-workspace-data (5.3.2-siduction1)
   kdebase-workspace-bin (4.11.22-3)
   kdegraphics (4.14.3+5.88+mod90.11)
   kdepim-groupware (4.14.5+really4.4.11.1+l10n-0r2.1)
   kdepim-strigi-plugins (4.14.5+really4.4.11.1+l10n-0r2.1)
   kdepim-wizards (4.14.5+really4.4.11.1+l10n-0r2.1)
   kgamma (15.04.3-siduction1)
   klipper (5.3.2-siduction1)
   kscreensaver (15.04.0-siduction0.4)
   ktorrent (4.3.1-90r0)
   libatkmm-1.6-1 (2.22.7-2.1)
   libav-tools (2.7.2-dmo2)
   libbaloowidgets4 (4.14.3-siduction1)
   libboost-date-time1.55.0 (1.55.0+dfsg-4)
   libcairomm-1.0-1 (1.10.0-1.1)
   libclucene-contribs1 (2.3.3.4-4)
   libclucene-core1 (2.3.3.4-4)
   libcmis-0.4-4 (0.4.1-7)
   libcmis-0.5-5 (0.5.0-2)
   libcwidget3 (0.5.17-2)
   libebml4 (1.3.1-dmo2)
   libflac++6 (1.3.1-2)
   libgconfmm-2.6-1c2 (2.28.0-1.1)
   libgegl-0.2-0 (0.2.0-dmo8)
   libglademm-2.4-1c2a (2.6.7-4)
   libglibmm-2.4-1c2a (2.44.0-1)
   libgpgme++2 (4.14.3-siduction1.0.3)
   libgtkmm-2.4-1c2a (2.24.4-1.1)
   libgtkmm-3.0-1 (3.16.0-1)
   libilmbase6 (1.0.1-6.1)
   libkf5baloo1 (5.9.2-siduction1)
   libkf5balooxapian1 (5.9.2-siduction1)
   libkfilemetadata4 (4.14.3-siduction1)
   libkolab0 (0.6.0-1)
   libkolabxml1 (1.1.0-3)
   libllvm3.5 (3.5.2-1)
   libmatroska6 (1.4.2-dmo2)
   libmovit2 (1.1.3-dmo1)
   libmsn0.3 (4.2-2)
   libmuparser2 (2.2.3-4)
   libopencolorio1 (1.0.9~dfsg0-3+b1)
   libopenconnect3 (6.00-2)
   libopencv-calib3d2.4 (2.4.9.1+dfsg-1.1+b2)
   libopencv-contrib2.4 (2.4.9.1+dfsg-1.1+b2)
   libopencv-core2.4 (2.4.9.1+dfsg-1.1+b2)
   libopencv-features2d2.4 (2.4.9.1+dfsg-1.1+b2)
   libopencv-flann2.4 (2.4.9.1+dfsg-1.1+b2)
   libopencv-highgui2.4 (2.4.9.1+dfsg-1.1+b2)
   libopencv-imgproc2.4 (2.4.9.1+dfsg-1.1+b2)
   libopencv-legacy2.4 (2.4.9.1+dfsg-1.1+b2)
   libopencv-ml2.4 (2.4.9.1+dfsg-1.1+b2)
   libopencv-objdetect2.4 (2.4.9.1+dfsg-1.1+b2)
   libopencv-video2.4 (2.4.9.1+dfsg-1.1+b2)
   libopenexr6 (1.6.1-8)
   libopenimageio1.4 (1.4.14~dfsg0-1)
   libopenimageio1.5 (1.5.17~dfsg0-1)
   liborigin2-1 (20110117-1+b4)
   libpangomm-1.4-1 (2.36.0-1)
   libproxy1 (0.4.11-4+b2)
   libqalculate5 (0.9.7-9)
   libqpdf13 (5.1.3-1)
   libreoffice (4.4.4-1)
   libreoffice-avmedia-backend-gstreamer (5.0.1-2)
   libreoffice-base (5.0.1-2)
   libreoffice-base-core (5.0.1-2)
   libreoffice-base-drivers (5.0.1-2)
   libreoffice-calc (4.4.4-1)
   libreoffice-core (4.4.4-1)
   libreoffice-draw (5.0.1-2)
   libreoffice-gnome (4.4.4-1)
   libreoffice-gtk (4.4.4-1)
   libreoffice-help-en-gb (4.4.4-1)
   libreoffice-impress (5.0.1-2)
   libreoffice-kde (4.4.4-1)
   libreoffice-lightproof-en (0.4.3+1.5+git20140515-2)
   libreoffice-math (4.4.4-1)
   libreoffice-report-builder-bin (5.0.1-2)
   libreoffice-writer (5.0.1-2)
   librlog5 (1.4-3)
   libsearchclient0 (0.7.8-1.2+b3)
   libsidplay1 (1.36.59-7)
   libsigc++-2.0-0c2a (2.4.1-1)
   libstreamanalyzer0 (0.7.8-1.2+b3)
   libstreams0 (0.7.8-1.2+b3)
   libstrigihtmlgui0 (0.7.8-1.2+b3)
   libtag1-vanilla (1.9.1-2.1)
   libtag1c2a (1.9.1-2.1)
   libtinyxml2.6.2 (2.6.2-2)
   libwxbase3.0-0 (3.0.2+dfsg-1)
   libwxgtk3.0-0 (3.0.2+dfsg-1)
   libyaml-cpp0.3 (0.3.0-1.1)
   mythes-en-us (3.3.0-4)
   plasma-desktopthemes-artwork (15.04.0-siduction0.4)
   plasma-widgets-workspace (4.11.13-90r2)
   python3-uno (4.4.4-1)
 
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: dibl on 2015/09/18, 17:02:43
Yes both gimp and libreoffice will be installable, at newer versions, after all the removals and after your kf5 packages are all installed.

Code: [Select]
root@Hibiscus:/# apt-cache policy libreoffice
libreoffice:
  Installed: 1:5.0.1-2
  Candidate: 1:5.0.1-2
  Version table:
 *** 1:5.0.1-2 0
        500 http://httpredir.debian.org/debian/ unstable/main amd64 Packages
        100 /var/lib/dpkg/status


But digikam is not installable so if you lose that it is gone for awhile.  I also lost hplip and some other items that I had to reinstall.  As of now the only two packages that I wish I had, which do not work with kf5, are skype and radiotray.  They both need a systemtray on the panel and kf5 does not have that capability (yet).

I had some difficulties with vlc and libtag1v5-vanilla, which required some manual work to find the dependencies and conflicts and fix them.  I have also noticed that bangarang is not working correctly -- it installs and opens, but does not play the file, so I'm not sure what that problem is.  But of course we have many music players for linux, and vlc and kaffeine are working today.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: Spike_DE on 2015/09/18, 19:49:17
Hi there,

uh, my simple question leads to a bunch of "comments". i apologize for that!

but to come back to the emotionless content of my question:

"how long do you personaly think will the gcc5-transition take?"

I'm asking that, because i don't feel very good without D-U for month.
but also: i don't want anything else than siduction on my system.
currently my system runs without problems, so i can wait. and yes, i'm using KDENEXT.

i've used siduction (and the prior sid-derivates) for years.
My understanding of sidux/aptosid/siduction was: making sid as stable, as possible.
that means for me: D-U is possible.

if this gcc5-topic means that we have to strougle for month/years, then we have a major problem, don't we?

@Spike_DE: Never without manual intervention .. :)

THAT is hopefully a joke?  :-[

thx to all of you, be kind to each other!
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: melmarker on 2015/09/18, 20:55:43
why should i make bad jokes - the reality is far better - and depending on the direction you want your system, you have to wait until the debian-qt-kde team or Santa fixes the remaining fallout. So it is a question of time and/or patience.

I'm a impatient person - so i let the most disturbing packages go some weeks ago and be done with the most of the shit. (Ok, LXQt is not that hard)
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: Santa on 2015/09/18, 22:01:05
Hi there,

uh, my simple question leads to a bunch of "comments". i apologize for that!

but to come back to the emotionless content of my question:


Thanks for getting things back on track, we were clearly going nowhere with the other line of conversation.

"how long do you personaly think will the gcc5-transition take?"

I'm asking that, because i don't feel very good without D-U for month.
but also: i don't want anything else than siduction on my system.
currently my system runs without problems, so i can wait. and yes, i'm using KDENEXT.


I agree it's not good to have this kind of situations, the only reason why it wasn't fixed earlier is that the GCC 5 transition involves so many packages that is getting too much time to gte things back on track.

i've used siduction (and the prior sid-derivates) for years.
My understanding of sidux/aptosid/siduction was: making sid as stable, as possible.
that means for me: D-U is possible.

That's what we - at least me - try to do as much as we can, but with GCC 5 it wasn't feasible to provide smooth continuous upgrades like we normally do. The good news about this transition is that is going to be, probably, an exceptional thing in the history of siduction.

if this gcc5-topic means that we have to strougle for month/years, then we have a major problem, don't we?



I don't think its going to take years to get it working again, I would rather say some days, but as allways I cannot give an exact day. Right now I'm building yet another round of packages and I don't know how many grave issues I will find. Hopefully less, because the general state of sid right now is a lot better than what it was in august.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: piper on 2015/09/19, 04:27:56

Santa, I give up, you may have  YOUR last word after this post


I apologise to the users of this forum, it's sad it had to get this far.




I don't like ANYONE telling me  what or what I can't do with my computer. It is mine, I bought the parts, I built it, I own it. I can also include USERS of siduction, unless, it will mess up your system.

I am not a moran, fucked up, but not a moran

I did not disrespect Santa in any way, shape, or form on this thread or forum in general.


What I did, was do things MY WAY, which, as you can see in this thread, he did not like

I have built many builds and did the installations to test. (4 machines, with several test partitions)  I have put many hours in this. It works, and works well, again, Santa does not like this


 This is all I  ever had to say about Santa

Quote from: "piper"


Code: [Select]
That's a tough question to answer ;)


It depends if you use kdenext or not

If you do, I cannot answer that, I don't know what Santa has cooking, it is a lot of work, and people need to be patient with kdenext. Santa has done a great job, he is one man and he *might be waiting for the transition to be over, I cannot speak for him.


This is how I get treated, or, just read this whole thread.


Quote from: "Santa"
Code: [Select]
Hello,


I have been reading many stupid things about KDE here, I was crystal clear from the beginning:
http://forum.siduction.org/index.php?topic=5719.msg46629#msg46629


So please stop misleading users and giving bad advices like the one above (meaning http://forum.siduction.org/index.php?topic=5719.msg47413#msg47413), It's not the first time that I see such kind of advices from forum moderators who really know nothing about KDE packaging.


Quote from: "melmarker"

Code: [Select]
Santa: Some people (piper in this case) have a different view to KDE than you - that doesn't mean that your'e allowed to call them morons. Please stop that now and for ever.



Quote from: "Santa"
Code: [Select]
I don't need to be allowed on irc to know that kind of things. 


Well, after your spies and whatever/whoever gave you the logs to what was said, (I know, you do ask for logs cause your not allowed there and I have witnessed you asking for logs, and i have years of logs myself)  then you know, full stop,   your full of shit then right, when you going to admit it (suck it up)  and apologise to the forum for spreading fud, yes, true fud,  that this can only work with kdenext and that we are all morans that build, install, use, kde/debian sid or in a nice tone,  USE WHAT WE WANT, WITHOUT YOU DICTATED WHAT WE DO, and if us morans choose to do things differntly than you KEEP YOUR SHIT to yourself

How many people running kde/debian sid without kdenext have a working system  ....



Nothing you do, say, or whatever else kind of manipulnation you do, will ever work with me and possibly others


"Manipulation" - is a way to covertly influence someone with indirect, deceptive, or abusive tactics. 



I enjoyed your work before, but the shit you just pulled with me and *possibly* our users, will never get me to use kde-next again, nor will I make a build with it included,  just your attitude alone is disturbing,  you remind me of microsoft and what it tried to do to linux in the early years.

  You are Steve Ballmer and I am the cancer (linux)  You are not what I call open source friendly.
 
 
  I think 100% that you can run and dist-upgrade siduction/debian without kde-next, there is no fud about it. It just works.




Thats it people, shows over, my last post in this thread period.   

TAKE IT AWAY SANTA  .......
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: jaegermeister on 2015/09/19, 10:15:57
But digikam is not installable so if you lose that it is gone for awhile.  I also lost hplip and some other items that I had to reinstall.  As of now the only two packages that I wish I had, which do not work with kf5, are skype and radiotray.  They both need a systemtray on the panel and kf5 does not have that capability (yet).


Thank for this very important information!


Not only I use gimp and digikam but also Skype and radiotray, so it would be great to know, from some of you who have already crossed the river of KDE5, when a systemtray will emerge out of this situation.
THX
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: Ercolinux on 2015/09/19, 15:26:00
Now skype-unofficial-client exists to use Skype via Web also in linux :


https://github.com/haskellcamargo/skype-unofficial-client (http://https://github.com/haskellcamargo/skype-unofficial-client)


I do  not know the real-usage, because I do not use it. But it could be can help You in these transition days while official Skype package cannot install or work
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: Santa on 2015/09/19, 18:18:01
Well, after your spies and whatever/whoever gave you the logs to what was said, (I know, you do ask for logs cause your not allowed there and I have witnessed you asking for logs, and i have years of logs myself)  then you know, full stop,   your full of shit then right, when you going to admit it (suck it up)  and apologise to the forum for spreading fud, yes, true fud,  that this can only work with kdenext and that we are all morans that build, install, use, kde/debian sid or in a nice tone,  USE WHAT WE WANT, WITHOUT YOU DICTATED WHAT WE DO, and if us morans choose to do things differntly than you KEEP YOUR SHIT to yourself

How many people running kde/debian sid without kdenext have a working system  ....



Nothing you do, say, or whatever else kind of manipulnation you do, will ever work with me and possibly others


"Manipulation" - is a way to covertly influence someone with indirect, deceptive, or abusive tactics. 



I enjoyed your work before, but the shit you just pulled with me and *possibly* our users, will never get me to use kde-next again, nor will I make a build with it included,  just your attitude alone is disturbing,  you remind me of microsoft and what it tried to do to linux in the early years.

  You are Steve Ballmer and I am the cancer (linux)  You are not what I call open source friendly.
 
 
  I think 100% that you can run and dist-upgrade siduction/debian without kde-next, there is no fud about it. It just works.




Thats it people, shows over, my last post in this thread period.   

TAKE IT AWAY SANTA  .......


Probably soon you won't have to worry about my "abusive tactics". I have been yesterday seriously considering to drop siduction both for development and for my own use. And probably I will go ahead with this decision.


So if you love the debian packages so much, congratulations, because if I finally leave, you will swallow them in all their greateness


It's not a single event what triggered this, but various things in the latest months/year.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: tux on 2015/09/19, 19:43:15
Dear Santa, you should keep kde-next up-to-date and working condition. Siduction is rolling release distro and you should keep this on your mind when you doing KDE Next packaging tasks.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: plandream on 2015/09/19, 19:47:24
So, considering I do have kdenext in my apt config, should I do a d-u? rip it off and go d-u?
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: Santa on 2015/09/19, 19:54:42
Dear Santa, you should keep kde-next up-to-date and working condition. Siduction is rolling release distro and you should keep this on your mind when you doing KDE Next packaging tasks.


And that's how it normally works. I already pointed out than the transition of GCC 5 was an exception to this because it was so big that it was impossible to keep it rolling. At the same time dist-upgrading with plain debian sid isn't still safe so we are not providing something worse than debian sid.

And no, it's not as simple as "being aware that siduction is a rolling release and that I should keep that in mind". If you think it's so easy, provide something better instead of saying how people (in this case me) should do their job.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: Santa on 2015/09/19, 19:56:32
So, considering I do have kdenext in my apt config, should I do a d-u? rip it off and go d-u?


No, as I pointed out several times, the best option is waiting a few days.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: plandream on 2015/09/19, 20:01:13
So, considering I do have kdenext in my apt config, should I do a d-u? rip it off and go d-u?


No, as I pointed out several times, the best option is waiting a few days.


Thanks, I was not entirely sure about it.I will leave it be.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: ayla on 2015/09/19, 20:03:13
So, considering I do have kdenext in my apt config, should I do a d-u? rip it off and go d-u?

I did this today, and with some dpkg --purge and force-overwrite and a lot of apt-get -f install at the end I have a running system again, as piper said above...
But on my main system I would prefer it much when Santa would  think it over again and deliver us a smooth d-u with kde-next when the progress of the gcc-transition allows it to do so.

I, for myself, can wait another few weeks/month if I do not have to run after the pieces of my config after.

And, without intention to blame anyone or take a side or whatever, I wish to say this:
I wish for siduction that people concentrate on the jobs they are doing and letting personal stories out of here.

greets
ayla
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: dibl on 2015/09/19, 20:03:57

I have been yesterday seriously considering to drop siduction both for development and for my own use. And probably I will go ahead with this decision.


Speaking only for myself, that is unfortunate.  I have enjoyed your KDE contributions.  I have been a sidux/aptosid/siduction user for 8 years or so now, and once in awhile sid users go through a special kind of Hell while major transitions happen.  Good luck with your future endeavors, whatever they may be.

Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: cas on 2015/09/20, 04:30:37
there seem to be two ways to handle the transition
1) follow santa's advice
2) not to  follow santa's advice

both seems viable. I didn't see any need to get emotional about this. Maybe another thread reserved for those  prefering not to follow santa's advice might help to reduce the confusion.

I have been yesterday seriously considering to drop siduction both for development and for my own use. And probably I will go ahead with this decision.
If you leave, which I dont hope, I'd like to say thanks for your work.

Christian
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: tmhind2 on 2015/09/20, 11:38:42
I have to agree with cas on splitting this thread for one important reason. It would cut down on all the confusion between kde-sid and kdenext for those that are just trying to get and keep kde running on their system. I don't know how many times I have had to pick-up the pieces as melmarker say's would happen trying either the sid or the kdenext updates. In end effect splitting the two kde threads would give those of us starting out here on siduction the choice on one or the other to follow and grow.


I also want to THANK BOTH santa and piper for what they have brought to siduction in the past and only hope that they will BOTH continue supporting us newbie's in the future despite their disagreements as loosing either one would be a shame!   


tom2
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: ralul on 2015/09/20, 15:17:25
It is just a misunderstanding:
there seem to be two ways to handle the transition
1) follow santa's advice
2) not to  follow santa's advice

both seems viable. I didn't see any need to get emotional about this. Maybe another thread reserved for those  prefering not to follow santa's advice might help to reduce the confusion.
Yes, the misunderstanding happened, because we - all of siduction - captured Santas thread (this one) for a general discussion how to handle the transition.
We should have had two threads from the beginning:
1. Santa explaining how to follow his kdenext, which seemingly follows Kubuntu.
This has the big advantage to have a shorter half year release cycle
2. Howto closely follow Debian sid.
Which in this special case is the faster method (perhaps days or weeks) to get through the C++ transition.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: plandream on 2015/09/20, 22:11:20
You are absolutely right. There is some confusion here and there,that's why I asked. Personally, I have no problem waiting a few extra days for such a humongous transition. My systems work without a problem anyway.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: jaegermeister on 2015/09/20, 22:14:23
Which in this special case is the faster method (perhaps days or weeks) to get through the C++ transition.


BTW, which is the current status of migration statistics upstream?


I would also like to take the occasion to say that I wouldn't like to see again what destroyed the sidux project, which was flaming attitude instead of concentrating on how to get jobs done. It would be great if you, guys, would just consider that you are working for the same goals and that technical disputes should just be within technical constraints and never get personal. That's the way siduction was born on the ashes of formerly clashing communities: by reserving a nice space where everybody could have a word without the fear of being put at unease. Thanks everybody.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: samoht on 2015/09/21, 03:03:06
@jaegermeister,

fully agree with you.
Let us hope, that both, piper and santa, remain such valuable and acknowledged members of our siduction community.

Greetings
Tom
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: DeepDayze on 2015/09/21, 03:32:51
@jaegermeister,

fully agree with you.
Let us hope, that both, piper and santa, remain such valuable and acknowledged members of our siduction community.

Greetings
Tom

Totally agree as we don't need fighting among our respected members. I feel that we should share ideas and while some ideas and suggestions might not be agreeable to everyone it's best to have a civil discussion on the merits of such ideas.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: thunderrd on 2015/09/21, 06:32:46
I am almost fearful of posting in this thread, since my system is KDE-free, but until the topic is changed it still appears to be the right place to ask.

I have not upgraded since July on this Xfce box, and this is the current state.  I don't see any major problems here that should stop me from upgrading now, but if someone else would take a quick look, I'd appreciate it:
Code: [Select]
[CHROOT]root@Q6600: /# apt-get dist-upgrade                                                                                     
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
The following packages will be REMOVED:
  libasprintf0c2 libatkmm-1.6-1 libbinio1ldbl libboost-date-time1.55.0 libcairomm-1.0-1 libcwidget3 libebml4 libept1.4.12
  libgconfmm-2.6-1c2 libglibmm-2.4-1c2a libgtkmm-2.4-1c2a libgtkmm-3.0-1 libilmbase6 libllvm3.5 libmatroska6 libopenexr6
  libpanelappletmm-2.6-1c2 libpangomm-1.4-1 libpcrecpp0 libprotobuf9 libproxy1 libqpdf13 libsidplayfp3 libsigc++-2.0-0c2a
  libtag1-vanilla libtag1c2a libtinyxml2.6.2 libxapian22
The following NEW packages will be installed:
  distro-info-data g++-5 libapt-inst1.7 libapt-pkg4.16 libasprintf0v5 libatkmm-1.6-1v5 libaudcore3 libbinio1v5
  libboost-date-time1.58.0 libboost-filesystem1.58.0 libboost-iostreams1.58.0 libboost-random1.58.0 libboost-regex1.58.0
  libboost-system1.58.0 libboost-thread1.58.0 libcairomm-1.0-1v5 libcwidget3v5 libdrm-amdgpu1 libebml4v5 libept1.4.16
  libglibmm-2.4-1v5 libgraphicsmagick++11 libgtkmm-2.4-1v5 libgtkmm-3.0-1v5 libicu55 libilmbase6v5 libjs-openlayers
  libllvm3.5v5 liblz4-1 libmatroska6v5 libnghttp2-14 libnpth0 libopenexr6v5 libpangomm-1.4-1v5 libpcrecpp0v5 libprotobuf9v5
  libproxy1v5 libqpdf13v5 libsidplayfp4 libsigc++-2.0-0v5 libstdc++-5-dev libtag1v5 libtag1v5-vanilla libtinyxml2.6.2v5
  libxapian22v5 linux-headers-4.2.0-towo.1-siduction-amd64 linux-image-4.2.0-towo.1-siduction-amd64
The following packages have been kept back:
  metacity-common
The following packages will be upgraded:
  abiword abiword-common acpi-support-base acpid apt apt-utils aptitude aptitude-common audacious-plugins
  audacious-plugins-data autoconf automake autotools-dev base-files bash bash-completion binutils bsdutils build-essential
  cdebootstrap cdrdao console-setup console-setup-linux cpp cpp-4.9 cpp-5 cups-client cups-common cups-core-drivers cups-daemon
  cups-filters-core-drivers cups-ppdc cups-server-common curl dbus dbus-x11 debhelper debtags dh-python dictionaries-common
  diffstat distro-defaults dmeventd dmsetup dosfstools dpatch dpkg dpkg-dev dvd+rw-tools evolution-data-server-common exo-utils
  fam file firmware-linux-free flac g++ g++-4.9 gcc gcc-4.9 gcc-4.9-base gcc-5 gcc-5-base gettext gettext-base gimp-help-common
  gimp-help-en gir1.2-gdkpixbuf-2.0 git git-man glib-networking glib-networking-services gnome-system-monitor gnote gnumeric
  gnumeric-common gnupg gnupg-agent gnupg2 gparted gpgv growisofs grub-common grub-pc grub-pc-bin grub2 grub2-common
  gsfonts-x11 gtk-redshift gvfs gvfs-bin gvfs-common gvfs-daemons gvfs-libs hostname html2text hwinfo iceweasel imagemagick
  imagemagick-6.q16 imagemagick-common initramfs-tools inkscape intltool-debian inxi iproute iproute2 isc-dhcp-client
  isc-dhcp-common iso-codes kexec-tools keyboard-configuration klibc-utils libabiword-3.0 libaiksaurus-1.2-0c2a
  libaiksaurusgtk-1.2-0c2a libapparmor1 libapr1 libapt-pkg-perl libasan1 libasan2 libasprintf-dev libassuan0 libatk-bridge2.0-0
  libatomic1 libaudit-common libaudit1 libauparse0 libavcodec-ffmpeg56 libavformat-ffmpeg56 libavresample-ffmpeg2
  libavutil-ffmpeg54 libblkid1 libburn4 libc-bin libc-dev-bin libc6 libc6-dev libcamel-1.2-52 libcap2 libcap2-bin libcc1-0
  libccid libcdr-0.1-1 libchamplain-0.12-0 libchamplain-gtk-0.12-0 libcilkrts5 libclutter-1.0-0 libclutter-gtk-1.0-0
  libcogl-pango20 libcogl-path20 libcogl20 libcolord2 libconfig-inifiles-perl libcrystalhd3 libcups2 libcupscgi1
  libcupsfilters1 libcupsimage2 libcupsmime1 libcupsppdc1 libcurl3 libcurl3-gnutls libdb5.3 libdbus-1-3 libdbus-1-dev
  libdevmapper-event1.02.1 libdevmapper1.02.1 libdjvulibre-text libdjvulibre21 libdns-export100 libdpkg-perl libdrm-dev
  libdrm-intel1 libdrm-nouveau2 libdrm-radeon1 libdrm2 libdvdnav4 libdvdread4 libebackend-1.2-10 libebook-1.2-16
  libebook-contacts-1.2-1 libecal-1.2-18 libedata-book-1.2-25 libedataserver-1.2-20 libegl1-mesa libegl1-mesa-dev
  libegl1-mesa-drivers libegl1-nvidia-legacy-340xx libelf1 libepoxy0 liberror-perl libevdev2 libexempi3 libexo-1-0
  libexo-common libexo-helpers libfam0 libfdisk1 libflac8 libfluidsynth1 libfontembed1 libfreerdp-cache1.1 libfreerdp-client1.1
  libfreerdp-codec1.1 libfreerdp-common1.1.0 libfreerdp-core1.1 libfreerdp-crypto1.1 libfreerdp-gdi1.1 libfreerdp-locale1.1
  libfreerdp-primitives1.1 libfreerdp-rail1.1 libfreerdp-utils1.1 libfreetype6 libfreetype6-dev libfribidi0 libftdi1 libgbm1
  libgcc-4.9-dev libgcc-5-dev libgcc1 libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-common libgegl-0.2-0 libgeoip1 libgettextpo-dev
  libgettextpo0 libgfortran3 libgl1-mesa-dev libgl1-mesa-dri libgl1-mesa-glx libgl1-nvidia-legacy-340xx-glx libglapi-mesa
  libgles1-mesa libgles2-mesa libglu1-mesa libgme0 libgnutls-deb0-28 libgnutls-openssl27 libgoffice-0.10-10
  libgoffice-0.10-10-common libgomp1 libgpg-error0 libgpgme11 libgraphicsmagick3 libgraphite2-3 libgs9 libgs9-common
  libgsf-1-114 libgsf-1-common libgtk2-perl libgxps2 libharfbuzz-dev libharfbuzz-gobject0 libharfbuzz-icu0 libharfbuzz0b
  libhd21 libhogweed4 libhunspell-1.3-0 libical1a libidn11 libijs-0.35 libinput10 libio-socket-ssl-perl libio-stty-perl
  libirs-export91 libisc-export95 libisccfg-export90 libisoburn1 libisofs6 libitm1 libjavascriptcoregtk-4.0-18 libjbig2dec0
  libjpeg62-turbo libkate1 libkeyutils1 libklibc libkpathsea6 libldap-2.4-2 libldb1 liblightdm-gobject-1-0 libllvm3.4
  libloudmouth1-0 liblsan0 liblua5.1-0 liblua5.2-0 liblvm2app2.2 liblvm2cmd2.02 libmagic1 libmagickcore-6.q16-2
  libmagickwand-6.q16-2 libmodplug1 libmount1 libmpcdec6 libmpg123-0 libmpx0 libncurses5 libncursesw5 libnet-http-perl
  libnettle6 libnm-glib4 libnm-util2 libnspr4 libnspr4-0d libnss3 libnss3-1d libnvidia-legacy-340xx-eglcore
  libnvidia-legacy-340xx-ml1 libopengl-perl libopenmpi1.6 libpackagekit-glib2-18 libpam-systemd libpci3 libpciaccess0
  libpcre16-3 libpcre3 libpcre3-dev libpcre32-3 libpcsclite1 libphonenumber6 libpipeline1 libpixman-1-0 libpixman-1-dev
  libplist3 libpoppler-glib8 libpoppler46 libpostproc-ffmpeg53 libppl-c4 libppl13 libproc-processtable-perl libprocps4
  libproxy-tools libpsl0 libpulse-mainloop-glib0 libpulse0 libpulsedsp libpython2.7 libpython2.7-minimal libpython2.7-stdlib
  libqdbm14 libqt4-xml libqt5core5a libqt5dbus5 libqt5gui5 libqt5network5 libqt5widgets5 libqt5x11extras5 libqtcore4 libqtdbus4
  libqtgui4 libquadmath0 librecode0 librsvg2-2 librsvg2-common libsane-common libseccomp2 libsecret-1-0 libsecret-common
  libsensors4 libslp1 libsmartcols1 libsmbclient libspice-server1 libsqlite3-0 libstdc++-4.9-dev libstdc++6
  libswresample-ffmpeg1 libswscale-ffmpeg3 libsystemd0 libtagc0 libtalloc2 libtdb1 libtevent0 libtext-wrapi18n-perl
  libthunarx-2-0 libtiff5 libtinfo5 libtracker-control-1.0-0 libtracker-sparql-1.0-0 libtsan0 libubsan0 libudev1 liburi-perl
  libusb-0.1-4 libusb-1.0-0 libuuid1 libv4l-0 libv4lconvert0 libva-drm1 libva-glx1 libva-x11-1 libva1 libval14 libvdpau1
  libvisual-0.4-0 libvlc5 libvlccore8 libwacom-common libwacom2 libwayland-egl1-mesa libwbclient0 libwebkit2gtk-4.0-37
  libwinpr-crt0.1 libwinpr-crypto0.1 libwinpr-dsparse0.1 libwinpr-environment0.1 libwinpr-file0.1 libwinpr-handle0.1
  libwinpr-heap0.1 libwinpr-input0.1 libwinpr-interlocked0.1 libwinpr-library0.1 libwinpr-path0.1 libwinpr-pool0.1
  libwinpr-registry0.1 libwinpr-rpc0.1 libwinpr-sspi0.1 libwinpr-synch0.1 libwinpr-sysinfo0.1 libwinpr-thread0.1
  libwinpr-utils0.1 libwireshark-data libwireshark5 libwiretap4 libwmf0.2-7 libwsutil4 libx264-146 libxatracker2 libxaw7
  libxml2 libxml2-utils lightdm linux-headers-siduction-amd64 linux-image-siduction-amd64 linux-libc-dev lm-sensors locales
  lsb-base lsb-release lsof lvm2 make man-db mesa-common-dev mime-support mount mousepad multiarch-support myspell-de-de
  ncurses-base ncurses-bin net-tools nscd ntfs-3g nvidia-legacy-340xx-alternative nvidia-legacy-340xx-driver
  nvidia-legacy-340xx-driver-bin nvidia-legacy-340xx-kernel-dkms nvidia-legacy-340xx-vdpau-driver openprinting-ppds
  openssh-client openssh-server openssh-sftp-server pciutils pcscd pinentry-gnome3 pinentry-gtk2 pokerth polipo poppler-utils
  pppconfig procps proj-data projectm-data psmisc pulseaudio pulseaudio-utils python-apt python-apt-common python-cairo
  python-imaging python-libxml2 python-numpy python-pil python-pkg-resources python-pyorbit python-six python-talloc
  python-xapian python2.7 python2.7-minimal python3-apt python3-pkg-resources python3-six qtcore4-l10n rar redshift
  redshift-gtk reiserfsprogs resolvconf rsyslog samba-dsdb-modules samba-libs screen shared-mime-info squashfs-tools ssl-cert
  synaptic systemd systemd-sysv tar thunar thunar-data thunar-dbg thunar-media-tags-plugin tracker transmission
  transmission-cli transmission-common transmission-gtk tzdata udev unrar unzip usbutils util-linux vim vim-common vim-runtime
  vlc vlc-data vlc-nox vpnc-scripts whois wireless-regdb wireshark wireshark-common wpasupplicant x11-xserver-utils xdg-utils
  xfce4-terminal xfdesktop4 xfdesktop4-data xfonts-intl-japanese xfonts-intl-japanese-big xfsprogs xorriso xserver-common
  xserver-xorg-core xserver-xorg-video-nvidia-legacy-340xx xterm xwayland zip
552 upgraded, 47 newly installed, 28 to remove and 1 not upgraded.
Need to get 569 MB of archives.
After this operation, 395 MB of additional disk space will be used.
Do you want to continue? [Y/n] n
Abort.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: devil on 2015/09/21, 09:38:31
Xfce should be pretty straight forward by now, as has been reported to us. Your output looks good to me. I would copy the list of removed packages and go over it after the upgrade to make sure everything got installed in new versions. Of course you can diff removed and installed before moving on.


greetz
devil
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: thunderrd on 2015/09/21, 10:11:22
OK, devil, thanks for putting an eye on that.  You've confirmed what I was thinking.

I'll try it out later, and post back if I see anything bad come up.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: DeepDayze on 2015/09/21, 15:28:36
OK, devil, thanks for putting an eye on that.  You've confirmed what I was thinking.

I'll try it out later, and post back if I see anything bad come up.

You could make a backup of the virtual machine before you d-u, as you can then roll back easily if you do have problems
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: thunderrd on 2015/09/21, 17:07:49
I've just finished this, and everything went fine.  All packages that were supposed to upgrade did, and there were no errors.

Thanks to all.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: mylo on 2015/09/23, 22:43:48
WOW!

Now it is more than thousand packs to be updated:

Code: [Select]
1006 aktualisiert, 109 neu installiert, 86 zu entfernen und 5 nicht aktualisiert.
I hope the release for update will come soon, but 80+ around to be removed remain like concrete.
Is there any expectation whether we talk about days or weeks to get d-u released?

The nice "Debian Transition" link gives percentages, but no end can be propagated therof or?
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: CCarpenter on 2015/09/23, 22:58:16
only thousand?

Code: [Select]
  1702 aktualisiert, 188 neu installiert, 134 zu entfernen und 4 nicht aktualisiert.
Es müssen noch 1.731 MB von 1.735 MB an Archiven heruntergeladen werden.
Nach dieser Operation werden 334 MB Plattenplatz zusätzlich benutzt.
 
 
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: reddark on 2015/09/23, 23:01:30
ihr könnt es ja mit apt upgrade versuchen etwas zu minimieren .. ;)
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: jaegermeister on 2015/09/24, 01:11:32
ihr könnt es ja mit apt upgrade versuchen etwas zu minimieren .. ;)


One thing is manually updating some low-level packages which are X-independent, another one is upgrading instead of dist-upgrading. Since this distro was born at the old kanotix and then sidux times, simple update has been a recipe for possible breakage/wreakage and totally unsupported. These are experiments to try on a test box, not on a production machine.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: der_bud on 2015/09/24, 08:27:10
...
I hope the release for update will come soon, but 80+ around to be removed remain like concrete.
Is there any expectation whether we talk about days or weeks to get d-u released?
 ...
AFAIK the list will never again drop to "0 to remove", because several packages and libraries get really replaced by others with a similar name, sometimes carrying an aditional "5" in it. So you have to go thoroughly through your list and watch if some of the 'to be removed' ones have a matching candidate in the 'newly installed' section.

This is definitely not a clear-to-go advice . It is a matter of every individual installation and software selection, combined with architecture and sources.list, spiced with desktop environment and drivers, if a dist-upgrade will be relatively save or at least repairable now or if it will go nuts. As the transition tracker is still around 40% today, most of the standard major packages seem done, but not all. From my very personal observation, LXDE and Cinnamon were safe to go these days. KDE pure debian needed some manual workarounds and dpkg-tricks before it worked. KDEnext on siduction repos is under progress, Santa is working at providing a clean upgrade path.  But even if he announces this thread as [solved] some day, that does not mean that the devs know that every single one of your personally installed packages is safe then.

As for apt upgrade , jaegermeister is generally right that in rolling unstable dist-upgrade is the supported way to go, but such a transition is a special situation. So apt upgrade as intermediate step before the next dist-upgrade might be a valid option to update some packages that seem save without removal. But still, not without having a tested backup available.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: mylo on 2015/09/24, 19:26:23
Thanks der_bud and jaegermeister for the very useful informations.
That is what i thought. For the day to come, just to be prepared:

I d-u since longer time with the next repo. So I d-u with it when the day is there or? Something else to obey?
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: plandream on 2015/09/26, 23:21:16
I did a D-U and it broke plasma workspace with kde next :-)


At least I don't need X on this machine.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: clubex on 2015/09/27, 13:03:31
On my upgraded KDE machine dolphin v4:15.08.1-1 isn't showing any previews. In Configure dolphin>General>previews the "Show previews for:" is completely empty.

I have ffmpegthumbnailer4v5, kdegraphics-thumbnailers and kdegraphic-strigi-plugins packages  installed.

Also installed are kdesk-dolphin-plugins, dolphin-plugins and libdolphinvcs5.

Has anyone else noticed this and more especially has anyone got a fix?

This is a freshly installed Indian Summer, dist-upgraded up to date.
Code: [Select]
CPU~Quad core AMD Phenom 9650 (-MCP-) speed/max~1150/2300 MHz Kernel~4.2.1-towo.1-siduction-amd64 x86_64 Up~2:29 Mem~732.4/7989.8MB HDD~250.1GB(64.8% used) Procs~201 Client~Shell inxi~2
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: madal on 2015/09/29, 07:47:29
Is someone going to inform us when it is safe to d-u?


I mean, how do I know if the blockers I currently have are due to kdenext not being finished yet; or if it is something I screwed up along the way?


madal
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: absolut on 2015/09/29, 11:22:51
originally, Santa was handling the whole situation including packaging for and supporting the users (gcc transition, kdenext, etc).

after browsing through the thread here, i am not completely sure about the current state of the situation... it would be really sad to see him drop the support, particularly because I had a positive and uncomplicated siduction+kde life by following his advice. also, i doubt that there is anybody available right now who would be able to take the workload /responsibility actively supporting the average user base (like me, who need a productive system with as fluent upgrade path as possible)

Santa, or anybody from the core team, can you please comment on the support situation?
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: devil on 2015/09/29, 12:04:32
The technical situation is as follows: We have two providers of KDE packages: one is debian unstable, the other is Santa's packages. Both rely in parts on Kubuntu's packaging, where Santa is involved as well. Historicaly over the past years, Debian's KDE packages were way behind upstream. Hence Santa started his own packaging by following upstream KDE as close as possible.


Siduction and it's users profited greatly from Santa's work and when the current transition started, he gave advice as how to handle the transition, which boiled down to waiting until things settled down. That was sound advice at the time, no matter which one of the two package streams you followed.


Along the way me and others in the team also started looking at how debian fares with respect to KDE in the transition and I transferred one of my systems from kdenext to pure debian and did a dist-upgrade, which was not easy at that point in time but worked out with lots of manual interception. Santa did not like this, as he probably thought, siduction was turning away from kdenext. I just did this in the best interest of our users.


What we have now is a situation where it is not clear if Santa will leave siduction or keep kdenext going for us. So right now, sound advice is hard to come by. What I can say is, that mixed systems (kdenext and switching to debian) will not work. If he really leaves, which I clearly do not hope, we will have to come up with a tool to convert users back to debian's packages regarding KDE.


It would be nice if Santa would chime in here and provide some clarity for users that make use of kdenext on what to expect and how to proceed. So please, as a kdenext user, have a little more patience, we will straighten the situation out as needed.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: absolut on 2015/09/29, 14:39:47
devil, thanks for your info
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: ralul on 2015/09/29, 21:52:00
The technical situation is as follows: We have two providers of KDE packages: one is debian unstable, the other is Santa's packages. Both rely in parts on Kubuntu's packaging, where Santa is involved as well. Historicaly over the past years, Debian's KDE packages were way behind upstream.
Debian unstable has a long period of a freeze when it boiles down to fix bugs for the coming Debian release. Kubuntu instead of a 2-to-3 years release cycle has a determined half year release cycle, hence
Quote
Hence Santa started his own packaging by following upstream KDE as close as possible.
Santas way to closely follow Kubuntu instead is a great way to get more of Kde upstream releases available for siduction:
Quote
Siduction and it's users profited greatly from Santa's work and when the current transition started, he gave advice as how to handle the transition, which boiled down to waiting until things settled down. That was sound advice at the time, no matter which one of the two package streams you followed.
Because Santas advice was true for the whole of siduction at first: This thread was adopted by all users of siduction. But after a while the dark heavens of Debian unstable cleared. At this moment users could purge kdenext and dist-upgrade towards a pure Debian unstable. This thread, meant especially for kdenext users, became obsolete for others.

In the long run siduction would widely profit from Santas way to follow kubuntus half year cycle. Naturally he needs a bit more time after such a transition, because he must wait for the Debian fundamental changes to get ready before he can build his kdenext again.

Another way would have been to pull in all of kde foundations into kdenext. But the repo had emerge a fat beast then (all of qt-dev and more) with an additional disadvantage: Not to be compatible any more with Debian unstable. The thin way Santa chose only has the sole disadvantage to have to wait until clouds cleared.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: piper on 2015/09/29, 23:02:47
Both Debian and Ubuntu build their releases from Debian unstable

Ubuntu/Kubuntu is just a six month snapshot of the current debian sid.

Ubuntu and Debian packages are binary incompatible.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: Santa on 2015/09/29, 23:14:12

Because Santas advice was true for the whole of siduction at first: This thread was adopted by all users of siduction. But after a while the dark heavens of Debian unstable cleared. At this moment users could purge kdenext and dist-upgrade towards a pure Debian unstable.


I repeat, again, that removing kdenext from sources.list and dist-upgrading is a very bad advice and a recipe to break your system. Also it's not true that "the dark heavens of Debian unstable cleared". I have been working lately on getting digikam and kaffeine (among others) installable.



This thread, meant especially for kdenext users, became obsolete for others.


This thread wasn't meant specially for kdenext users.



originally, Santa was handling the whole situation including packaging for and supporting the users (gcc transition, kdenext, etc).

after browsing through the thread here, i am not completely sure about the current state of the situation... it would be really sad to see him drop the support, particularly because I had a positive and uncomplicated siduction+kde life by following his advice. also, i doubt that there is anybody available right now who would be able to take the workload /responsibility actively supporting the average user base (like me, who need a productive system with as fluent upgrade path as possible)

Santa, or anybody from the core team, can you please comment on the support situation?



I'm working on the latest tweaks towards making the dist-upgrades safe again for KDE. The recommended way of proceed is still holding the dist-upgrade, and wait a few days for instructions. Please disregard any other advice as much as possible.


Rgarding my possible leaving of siduction, that will come later, you don't have to do anything special about that for now.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: Santa on 2015/09/29, 23:16:06
Both Debian and Ubuntu build their releases from Debian unstable


No.

Ubuntu/Kubuntu is just a six month snapshot of the current debian sid.


No.


Ubuntu and Debian packages are binary incompatible.


Yes.


In any case I fail to see the relation of these statements with the GCC 5 transition.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: piper on 2015/09/30, 00:06:25
Quote from: Santa
Quote from: piper on Today at 05:02:47 PM (http://forum.siduction.org/index.php?topic=5719.msg47571#msg47571)Both Debian and Ubuntu build their releases from Debian unstable

No.

Quote from: piper on Today at 05:02:47 PM (http://forum.siduction.org/index.php?topic=5719.msg47571#msg47571)Ubuntu/Kubuntu is just a six month snapshot of the current debian sid.

No.


Quote from: piper on Today at 05:02:47 PM (http://forum.siduction.org/index.php?topic=5719.msg47571#msg47571)Ubuntu and Debian packages are binary incompatible.

Yes.


In any case I fail to see the relation of these statements with the GCC 5 transition.

I took that directly from ubuntu's website or Canonical's, whichever one you want to look at

Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: Santa on 2015/09/30, 00:44:40
Quote from: Santa
Quote from: piper on Today at 05:02:47 PM (http://forum.siduction.org/index.php?topic=5719.msg47571#msg47571)Both Debian and Ubuntu build their releases from Debian unstable

No.

Quote from: piper on Today at 05:02:47 PM (http://forum.siduction.org/index.php?topic=5719.msg47571#msg47571)Ubuntu/Kubuntu is just a six month snapshot of the current debian sid.

No.


Quote from: piper on Today at 05:02:47 PM (http://forum.siduction.org/index.php?topic=5719.msg47571#msg47571)Ubuntu and Debian packages are binary incompatible.

Yes.


In any case I fail to see the relation of these statements with the GCC 5 transition.

I took that directly from ubuntu's website or Canonical's, whichever one you want to look at


In first place, I couldn't find such statements (at least exactly as you posted it) on any of the websites.


In second place, I don't really need to check a website to understand how debian and ubuntu development works: for sure, Ubuntu is not a 6 month snapshot of debian sid, there are differences and many packages which don't even exist in debian or are more updated and it's not the first time we import some of them here.


And I'm completely sure ubuntu builds their releases from ubuntu not from debian, that's obvious.


How is this related to the GCC 5 transition?
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: domicius on 2015/09/30, 00:52:34
Quote from: piper
I took that directly from ubuntu's website or Canonical's, whichever one you want to look at

Whoever is more knowledgeable could correct me here, but I think what you took directly from Ubuntu's/Canonical's websites is just a simplification of the matter. The real matter is it's not just a verbatim usage of Debian unstable packages (of course, but the statements above make it seem like it something that simple), there's a lot of continuous work involved in changing those packages, and that work can sometimes (most of the times?) be used in Debian, after additional work by Debian packagers (who are in some cases Ubuntu packagers as well). Additionally, I also fail to see how these facts have anything to do with the current situation.

Anyway, that's not the point of my post. The point is it really pains me (as I'm sure it pains others who aren't even posting) to see people misunderstanding each other in this thread.

I think this really hits the nail on why the misunderstanding started happening
Quote from: ralul
Because Santas advice was true for the whole of siduction at first: This thread was adopted by all users of siduction.

I for one silently "tolerated" so many of the "success" posts here even though they clearly were from people either 1) not using KDE 2) not using kdenext or 3) not using the packages that *I myself* use daily. So they didn't apply for me and I'm sure many others.

Now, does anybody thing a split of this thread is in order? I know it's not as simple as to say that this is just for kdenext folks, and others can discuss in another thread, but can one say if you've never used kdenext and don't rely on KDE packages at all, that it might be feasible for you to DU? (Still, I hope everybody uses common sense and doesn't blindly follow advices without looking what apt-get warns them).
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: absolut on 2015/09/30, 09:22:21

<< posting cropped >>

originally, Santa was handling the whole situation including packaging for and supporting the users (gcc transition, kdenext, etc).

after browsing through the thread here, i am not completely sure about the current state of the situation... it would be really sad to see him drop the support, particularly because I had a positive and uncomplicated siduction+kde life by following his advice. also, i doubt that there is anybody available right now who would be able to take the workload /responsibility actively supporting the average user base (like me, who need a productive system with as fluent upgrade path as possible)

Santa, or anybody from the core team, can you please comment on the support situation?



I'm working on the latest tweaks towards making the dist-upgrades safe again for KDE. The recommended way of proceed is still holding the dist-upgrade, and wait a few days for instructions. Please disregard any other advice as much as possible.


Rgarding my possible leaving of siduction, that will come later, you don't have to do anything special about that for now.

Santa, thanks a lot for your response and advice!

Looking forward to new updates. Thanks a lot for your commitment. Very much appreciated!
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: titan on 2015/09/30, 10:35:49
I think siduction is loosing  the plot. It is meant to be totally compatible with sid which this thread illustrates it is not. The devs should be supporting upgrading KDE with pure Debian repros only, not an incompatible  bespoke siduction/Ubuntu repro. I think a lot of users of kdenext will only be prolonging their transition back to kde sid.  There are plenty of other desktops available to use while waiting for KDE to emerge from the current transitional chaos. A lot of the current problems could have been avoided if the kdenext thread had been put into the experimental section of the forum and the main support for the gcc and qt5 transition pinned at the top of the upgrade section.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: piper on 2015/09/30, 11:14:58
Quote from: Santa
Quote from: piper on Yesterday at 06:06:25 PM (http://forum.siduction.org/index.php?topic=5719.msg47574#msg47574)Quote from: Santa

And I'm completely sure ubuntu builds their releases from ubuntu not from debian, that's obvious.



And I am leaving this at that  .........

I have never, in my lifetime seen anything like this

Why on earth does everyone in the debian world know this except you ?

Without debian and their packages, ubuntu WOULD NOT EXIST

I don't know where you have been since ubuntu came into this world, but, ubuntu has always been based and built on debian.

I have a hell of a lot to say on this subject Santa, but, I am biting my tongue and just let you think you know everything about debian, ubuntu, packaging, and reindeer.

After all,  I am just a moran right.

Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: horo on 2015/09/30, 11:17:44
Hi,

Me again - I want to bring my proposal from ^^^^ (far far above) to attention again - please split this topic into the original pro kdenext one (don't do anything until Santa tells you) and a more adventurous "I want to DU and I want it now!"-thread, with guidance how to pick up the pieces.
And maybe a third one with technical discussion without "ad-hominem" who is right and who is wrong - if a prudent moderator like e.g. devil would guide the hotheads we technical-minded users will benefit for sure.
THX

Ciao, Martin

P.S.: while typing I read piper's last post and it reinforces my opinion.

P.P.S.: Please stop "slam (http://www.kieler-linuxtage.de/grafiken/redner/childebrandt.jpg)"ming siduction!
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: hschn on 2015/09/30, 11:35:16
@horo
+++1
I'm interestet in debian, pc etc,
but not in any shitstorm
hschn
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: domicius on 2015/09/30, 11:36:27
Quote from: titan
I think siduction is loosing  the plot. It is meant to be totally compatible with sid which this thread illustrates it is not. The devs should be supporting upgrading KDE with pure Debian repros only, not an incompatible  bespoke siduction/Ubuntu repro. I think a lot of users of kdenext will only be prolonging their transition back to kde sid.  There are plenty of other desktops available to use while waiting for KDE to emerge from the current transitional chaos. A lot of the current problems could have been avoided if the kdenext thread had been put into the experimental section of the forum and the main support for the gcc and qt5 transition pinned at the top of the upgrade section.
kdenext is optional, and for that matter you don't even have to use towo's kernels, right? ;)

But there are many users who appreciate both of these contributions and don't want to use "other" desktops either.

And please, people, let's be careful about suggesting other people what to use, because while there are "plenty of other desktops available to use" (it's not like we don't know that), one can say there are plenty of other distributions and operating systems. One can even claim to another fellow forum member they can live without any of the packages/software they currently use and rely upon, because see, "we don't use them we're OK". ;) But if we go in that direction, where will we end up?

Also, the current situation isn't about "an incompatible bespoke siduction/Ubuntu repro" but due to Debian's GCC 5 transition (please read the linked broadcast to the Debian mailinglist) (https://lists.debian.org/debian-devel-announce/2015/07/msg00000.html). This transitions is far from over yet (at 39% currently, as you can see (https://release.debian.org/transitions/)).
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: piper on 2015/09/30, 11:41:24
Quote from: horo
Hi,

Me again - I want to bring my proposal from ^^^^ (far far above) to attention again - please split this topic into the original pro kdenext one (don't do anything until Santa tells you) and a more adventurous "I want to DU and I want it now!"-thread, with guidance how to pick up the pieces.
And maybe a third one with technical discussion without "ad-hominem" who is right and who is wrong - if a prudent moderator like e.g. devil would guide the hotheads we technical-minded users will benefit for sure.
THX

Ciao, Martin

P.S.: while typing I read piper's last post and it reinforces my opinion.

P.P.S.: Please stop "slam (http://www.kieler-linuxtage.de/grafiken/redner/childebrandt.jpg)"ming siduction!
If your comparing me to Slam by me saying this

"Without debian and their packages, ubuntu WOULD NOT EXIST

I don't know where you have been since ubuntu came into this world, but, ubuntu has always been based and built on debian."

It's time for me to leave, you win, I quit.

devil, delete my mod privileges, been a hell of a ride starting with KDE 1.0 and linux since the mid 90's
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: sunrat on 2015/09/30, 11:55:33
+1 @horo
I like that I can use kdenext and highly value Santa's contribution. I have not d-u since this thread started and eagerly but patiently await advice for when it is safe to do so. My system is working fine with only a couple of minor niggles brought on by the initial KF5 inflow, not gcc5.
And I'm sad to see what can only be described as flaming, as a major reason I have been using siduction for a few years is the hereto civility of the community compared to some of the other distros I have seen.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: vilde on 2015/09/30, 12:12:17
I have been away for a couple of weeks and coming back to find this moaning about and in this thread. It's unfair.

As amateur i feel this has been the most troublesome upgrade time or transition time or whatever it's called as long I have been on this train (since Kanotix) and I think this has been handled very well from the siduction team.

Siduction is Debian unstable, there will be trouble, and I'm here because I trust the the siduction team to handle the trouble for me, and my opinion is that they are doing it very well.

This transition has been affecting all of us not only kde users, my posts here about being able to d-u my fxce boxes was not for telling how good I am (because I'm  not) it was for only to show what was possible, at least for me, and to give that information to other users  and developers.
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: horo on 2015/09/30, 12:17:32
Hi piper,

As you address me I'll answer directly. I did'nt call YOU a slammer but if you think the shoe fits - wear it.
Your selective citation that omitted the nasty cheap shots doesn't calm down the hot mood.
Quote
I have never, in my lifetime seen anything like this
Why on earth does everyone in the debian world know this except you ?
I'm with you in going the debian way, my system is kdenext-free - but please let's discuss technical and not ad-hominem. I'm on the kanotix-sidux-aptosid-siduction-way since years and have seen that words can do much more harm than bugs, buffer overflows and software patents together.
Please calm down and talk _with_ each other - not against!

Piper, Santa et.al.: Could we consider some other options than dropping your good work in midstream. Your contribution is needed and highly appreciated.

Ciao, Martin

Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: titan on 2015/09/30, 12:21:47

kdenext is optional, and for that matter you don't even have to use towo's kernels, right? ;)

But there are many users who appreciate both of these contributions and don't want to use "other" desktops either.

And please, people, let's be careful about suggesting other people what to use, because while there are "plenty of other desktops available to use" (it's not like we don't know that), one can say there are plenty of other distributions and operating systems.

Forums are a difficult medium to converse in, I think you have taken a lot of what I said out of context. Most of the problems on siduction regarding KDE are in my opinion due to kdenext being endorsed as the way forward by siduction, if not overtly then subliminally by pinning this thread where it is. Because of this some users now are stuck in an unenviable position where it looks like the packager may stop work before the full transition and they will have a broken KDE. For those of us who use siduction as our main PC an alternative desktop is a viable option during the transition, I was not telling anyone what  to do. If you look at the aptosid forum in comparison there has only been a few posts about KDE's transition
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: domicius on 2015/09/30, 12:53:13
Quote from: titan
Forums are a difficult medium to converse in, I think you have taken a lot of what I said out of context.

I completely agree about the difficulty to convey messages in written form sometimes and if it seems I've taken anything out of context, that wasn't on purpuse, it was just how I read your (and not just your) post.

Quote from: titan
For those of us who use siduction as our main PC an alternative desktop is a viable option during the transition, I was not telling anyone what  to do.

I understand that and I fall in that category. By closely watching this subforum and always "listening" to apt-get before agreeing on DU, I still do my daily job (on this frankensystem I've had since many years ago based first only on sid, then aptosid and now siduction - yes, I don't like to mess with my installations, nor desktops for that matter, once I set things how I like them, I tend to keep them a long time that way, even forgetting they're not the default, so any disturbance in that is bad for me - kind of hate KDE upgrades, they always seem to ignore (at least some of) my previous settings).
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: devil on 2015/09/30, 15:53:32
Can we please stop using this thread as a forum for bickering. This thread is supposed to inform users about the state of affairs without the need to wade through hateful accusations back and forth. Thank you.
If Santa leaves the team, he will do so after the transition is done and kdenext fully upgradable again. He then will also provide means to migrate to debian proper.


Regarding splitting the thread: That already happened in the form of the KF5 issues thread (http://forum.siduction.org/index.php?topic=5792.0) .
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: ghstryder on 2015/09/30, 19:43:56
Thank you, Devil!
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: Santa on 2015/10/01, 17:37:00
Can we please stop using this thread as a forum for bickering. This thread is supposed to inform users about the state of affairs without the need to wade through hateful accusations back and forth. Thank you.
If Santa leaves the team, he will do so after the transition is done and kdenext fully upgradable again. He then will also provide means to migrate to debian proper.


Regarding splitting the thread: That already happened in the form of the KF5 issues thread (http://forum.siduction.org/index.php?topic=5792.0) .


Thanks for clarifying that.


kdenext was upgraded today, please read:
http://forum.siduction.org/index.php?topic=5801.0 (http://forum.siduction.org/index.php?topic=5801.0)
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: terroreek on 2015/10/01, 23:39:33
I'd like to add that I was able to successfully upgrade one of my gnome (indiansummer) installs, haven't done it on my laptop(december) just yet.

Only think I can note is that cheese crashes when it finds my webcam or launches but can't find my webcam. 
Title: Re: [ACHTUNG! URGENT!] GCC 5 TRANSITION, DO NOT DIST-UPGRADE or keep the pieces
Post by: musca on 2015/10/02, 01:07:53
Hello terroreek,

yes, all the other siduction desktops (gnome, cinnamon, xfce, lxde and lxqt) are upgradable. Please keep in mind, after dist-upgrading you can't install old packages that still depend on libstdc++6 version < 5.2.

Also work is in progress to get the Mate desktop into siduction and LXQT into debian.

Now it is a good time to close this thread.

Feel free to open new threads for individual questions.

greetings
musca