SlackwareThis Forum is for the discussion of Slackware Linux.
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.
What is the output of `cat -A /etc/sbopkg/repos.d/40-sbo.repo`
# $Id: 40-sbo.repo 669 2009-07-08 16:22:00Z chess.griffin $$
# SlackBuilds.org repository file$
# DO NOT EDIT THIS FILE. CHANGES WILL BE OVERWRITTEN.$
# See README-repos.d in the sbopkg /doc directory for$
# information on this directory and how to create$
# custom repository files.$
# Repo Branch Description Tag Tool Link CheckGPG$
SBo 13.0 "SBo repository for Slackware 13.0" _SBo rsync slackbuilds.org::slackbuilds/13.0 GPG$
SBo 12.2 "SBo repository for Slackware 12.2" _SBo rsync slackbuilds.org::slackbuilds/12.2 GPG$
SBo 12.1 "SBo repository for Slackware 12.1" _SBo rsync slackbuilds.org::slackbuilds/12.1 GPG$
SBo 12.0 "SBo repository for Slackware 12.0" _SBo rsync slackbuilds.org::slackbuilds/12.0 GPG$
SBo 11.0 "SBo repository for Slackware 11.0" _SBo rsync slackbuilds.org::slackbuilds/11.0 GPG$
and `/bin/bash --version`? (3.2 will also mess it up.)
GNU bash, version 4.0.24(2)-release (i486-slackware-linux-gnu)
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
ok, so my question now is how it got installed. This is a bit worrisome to me, because I am 100% sure I installed nothing from testing on this computer. The only possibility I can think of is that this somehow came from a "slackpkg upgrade-all". I don't use any other package manager. Hmmm. Maybe I should abandon slackpkg and sbopkg and go back to the manual way.
Thanks for noticing this. I'm sorry I responded no to the version question before, but really, I don't understand how it is possible.
How does slackpkg treat upgrades when different versions exist in the main branch and in /testing?
I don't know. While I naturally use sbopkg, I don't use slackpkg, but that was my initial suspect, too. Slackpkg may have an option to enable or disable /testing. If it's allowed to look in /testing it's going to correctly see that you have a bash installed and that bash 3.1 isn't the newest, so will upgrade you. But its default configuration certainly shouldn't do that. It's my understanding that it's a solid, sensible program, but if you can't find anything amiss in your configuration and/or that is the default, you might report it to the slackpkg folks as a bug.
I upgraded to 3.1.17 and it works fine. slackpkg upgrade-all does not suggest upgrading to the /testing version. So I must have been sleep-walking one night. Thanks for the help, and sorry again for the misinformation.