SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: slackware64 13.37 and -current, Dragonfly BSD
Posts: 1,810
Rep:
It looks like you may have two versions of python installed with the one pointed to by the symbolic link /usr/bin/python being python2.5. To test this try running python2.5 then python2.6 like this.
Code:
python2.5 -V
python2.6 -V
If both work and report differing versions of python you just need to run the following as root:
This will leave python2.5 in place that you can still run with python2.5. I think it would be better to totally uninstall python2.5 as having two versions of the same branch of python can cause problems. In any case your package directory /var/log/packages is also messed up as it did did report python2.5 as being installed.
It looks like you may have two versions of python installed with the one pointed to by the symbolic link /usr/bin/python being python2.5. To test this try running python2.5 then python2.6 like this.
Code:
python2.5 -V
python2.6 -V
If both work and report differing versions of python you just need to run the following as root:
This will leave python2.5 in place that you can still run with python2.5. I think it would be better to totally uninstall python2.5 as having two versions of the same branch of python can cause problems. In any case your package directory /var/log/packages is also messed up as it did did report python2.5 as being installed.
Hello:
I did the above, rebooted and did python -V which yielded: Python2.5.6
Honestly though, I would have attempted to fix it.
After all, there's no better way to learn then from fixing your own adventures.
I'd bet that's the way many experienced Slackers learned their way around
Distribution: slackware64 13.37 and -current, Dragonfly BSD
Posts: 1,810
Rep:
Good luck from me too - however I very much agree with what disturbed1 said. It's amazing how much you can learn by solving problems like this and, to be honest, this python version mix up should be very easy to diagnose and fix with a few more steps. You wouldn't believe the problems I have had on systems, such as having my entire file system's ownerships and permissions messed up - no fun that one, and had to fault find and fix. This process has increased my knowledge of how stuff all works by miles and it would yours too. I'm by no means saying I'm a Linux expert but your knowledge is rapidly enhanced when you have to fault find your system. What's more I think its maybe "the Slackware way".
What's more there's a very active and knowledgeable community here that's always very helpful - even the giants, (core team), of Slackware often contribute, Patrick Volkerding (our BDFL), Eric Hameleers, Robby Workman, Vincent Batts, John Jenkins ,Piter PUNK and others - (apologies if I have missed any team members but "and others" is meant to include you - no offence intended). Just notice how many times you'll see "Slackware Contributor" under someone's user name. The core Slackware team are very involved with the community and that's fantastic.
Distribution: slackware64 13.37 and -current, Dragonfly BSD
Posts: 1,810
Rep:
Edit : For type corrections see my next post ..
Quote:
Is there a way to determine if I have all the correct Slackware 13.37 files on my system?
Just make sure /etc/slackpkg/mirrors is correctly pointing to a Salckware 13.37 repo ands as root run
Code:
slackpkg update
skackpkg install-new
slackpkg update-all
# ONLY RUN THIS IF YOU HAVE NOTHING ADDITIIONAL TO SLACKWARE INSTALLED OR SET UP BLACKLISTS
slackpkg clean-system
Be careful this if you run it be sure to unselect anything added on to Slackware that you want to keep or it will be uninstalled.
Just make sure /etc/slackpkg/mirrors is correctly pointing to a Salckware 13.37 repo ands as root run
Code:
slackpkg update
skackpkg install-new
slackpkg update-all
# ONLY RUN THIS IF YOU HAVE NOTHING ADDITIIONAL TO SLACKWARE INSTALLED OR SET UP BLACKLISTS
slackpkg clean system
Be careful this if you run it be sure to unselect anything added on to Slackware that you want to keep or it will be uninstalled.
Thanks bgeddy - I will keep this on file for future reference.
After uninstalling python as suggested above, and then being unable to connect to the net to get additional help, I formatted my hard disk and re-installed from my new Slackware 13.37 DVD.
Thanks again to everyone for there help and advice on this topic.
Distribution: slackware64 13.37 and -current, Dragonfly BSD
Posts: 1,810
Rep:
Well as you mentioned putting this on file I think I should correct a few errors in my spelling and such - the commands should be this :
Code:
slackpkg update
skackpkg install-new
slackpkg upgrade-all
# ONLY RUN THIS IF YOU HAVE NOTHING ADDITIIONAL TO SLACKWARE INSTALLED OR SET UP BLACKLISTS
slackpkg clean-system
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.