On Thursday 26 Nov 2015 12:07 CET, Dave Farrance wrote: > Cecil Westerhof <ce...@decebal.nl> wrote: > >> On Wednesday 25 Nov 2015 23:58 CET, Laura Creighton wrote: >>> >>> Your Suse system probably wants to use python for something. If >>> your system python is damaged, you badly need to fix that, using >>> the system package managers tools, before Suse does some sort of >>> update on you, using the broken python, which damages more of your >>> system. >> >> I tried that. But it installs only things in /usr/lib and >> /usr/lib64, nothing in /usr/bin, but at the same time it is adamant >> that it installed python. I wanted a quick fix, but it looks like >> that is not going to work. :'-( I'll have to find a way to get >> things fixed. > > A complete reinstall of Suse (after saving your home directory and > work) might be quickest if you're in the dark about what's broken. > > But you might be able to fix it. If you can figure out which > packages contain the damaged files, then do forced reinstalls of > those. I've not used Suse, but a quick Google tells me that the > syntax is: > > zypper in -f <package-name> > > So you'll want to try package names like "python" and "python2.7".
Sadly that also only installs only libraries and no applications. -- Cecil Westerhof Senior Software Engineer LinkedIn: http://www.linkedin.com/in/cecilwesterhof -- https://mail.python.org/mailman/listinfo/python-list
