On 8/18/15, Dorival Pedroso <pedr...@cpmech.com> wrote: > Hi, > > I'm just wondering if there is a way to fix problems with libstdc++6 in > Debian unstable? > > I'm trying to install blender and/or python-scipy for example.
Are you working with your package manager's absolute latest updates that are drawn from the repositories? By that I mean and as example.... I use "apt-get" to install my packages. Others use synaptic and/or aptitude. For apt-get, I FREQUENTLY run the following from a terminal: apt-get update If you already knew that, my apologies in advance. Somewhere there will be a newcomer who didn't. :) I'm headed back outside right now to do more yard work but high on today's to-do list was to *try* to catch back up on this very topic here. As of very early yesterday morning, all those problems have disappeared off my own unstable versions. That's why I suggested the very basic thought of updating our package managers. NOTE: The rest of this is "meandering" on my own last couple days in this..... The previous errors I had that involved "libstdc++6" disappeared couple days ago. Those involved programs wanting to autoremove libreoffice. The NEW and similar errors began involving inkscape. Caused inkscape to be uninstallable in my newest pure/clean debootstrap. Also caused inkscape to be removed by too many other totally unrelated programs in my previous "stable" unstable (several months old) debootstrap copy. * * * Afterthought note there: Inkscape's in there with blender. Fingers are crossed that a fix is coming soon for blender's omissions, if not done already. :) * * * In my brand new and thus basically "empty" debootstrap here, gparted drug in a couple dependency packages that were previously deemed on hold for any inkscape install attempts. That same gparted was at that moment simultaneously trying to REMOVE inkscape in my "stable" unstable copy. At first I was thinking gparted FINALLY dragging in some "on hold" dependency packages in the newest empty/clean debootstrap might hint at a possible backdoor for these problems. Smacked myself in the head just now because I realized it was probably because those couple dependencies had just been fixed by Debian developers. It was interesting to watch the upgradeable list of packages appear to change without any (conscious) action on my part. Best as I could tell from this end, some of THAT.... is because there was a phenomenal amount of unrelated packages installing each other. In the days just before, those packages had been *theoretically* irreversibly UNINSTALLING each other. When packages INSTALL each other, the process occurs a lot more quietly *IF* you don't stop and read/comprehend the verbose output before you tell a package manager to go ahead and complete the install. Makes it easier to not "see", to miss what's been going on under the hood. Goodness, I hope some of that makes sense. Sorry I didn't have an answer, just wanted to note that my experience went a certain way, ended up very positive, and reflects that Debian developers are definitely busting backside on this. That observation is based on the progress that could be seen while running "apt-get update" multiple times a day over the last week. Cindy :) PS.. An afterthought on this for newcomers: Some things that helped me not miss a beat in daily computing through all this included knowing how to move things like .config files in between the various copies of distros I play with here. The ability to move around between multiple distros/releases comes from having self-taught myself how to create PARTITIONS. Those are FRIGHTENING at first but have been GREAT toys, oops, TOOLS in instances like this past week. ALWAYS have umpteen backup copies of whatever last distro copy of your own was working 100%... !!-*_ALWAYS_*-!! Don't be a hard head about HAVING to go pure unstable when unstable hits a bump like this past week. Keep a very stable *stable* copy of Debian around just for kicks, too. PPS.. That last one falls under.... don't do as I do... yada-yada.. *GRIN* -- Cindy-Sue Causey Talking Rock, Pickens County, Georgia, USA * Life Lesson Learned: They weren't just whistling Dixie when they named it "unstable" =D *
