[SOLVED] sbopkg: b0rked by bash upgrade in -current?
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.
Line
SBo 13.0 "SBo repository for Slackware 13.0" _SBo rsync slackbuilds.org::slackbuilds/13.0 GPG
of
/etc/sbopkg/repos.d/40-sbo.repo
specifies an unknown fetching tool (rsync).
... seems likely given the discussion in that previous thread that the bash upgrade (to 4.1.002) in the recent -current onslaught is responsible?
Thanks,
Glenn
Last edited by chexmix; 03-04-2010 at 08:28 AM.
Reason: fixed the issue, which was a non-issue
This issue should be fixed in SVN as of last October (http://code.google.com/p/sbopkg/issues/detail?id=32). If you can pull from SVN and test, I would greatly appreciate it. If you still have issues, please post a bug report in the sbopkg Issue Tracker at the Google Code site. Thanks.
Edit: this fix went in to sbopkg 0.31.0. Is that the version of sbopkg you are using? If not, can you please upgrade to 0.31.0 and try again?
I just did the current upgrade an hour or so ago and had sbopkg look for updates, I have't tried to build any packages but everything looks like it's a go. I have sbopkg 0.31 installed. I DID NOT overwrite any .conf files but saved the new ones as .new.
This issue should be fixed in SVN as of last October (http://code.google.com/p/sbopkg/issues/detail?id=32). If you can pull from SVN and test, I would greatly appreciate it. If you still have issues, please post a bug report in the sbopkg Issue Tracker at the Google Code site. Thanks.
Edit: this fix went in to sbopkg 0.31.0. Is that the version of sbopkg you are using? If not, can you please upgrade to 0.31.0 and try again?
OK, that must be it - I am using 0.30.1 on this box. Sorry for the alarm. I will install 0.31.0 when I get a chance ... maybe late tonight.
Someone else confirmed in IRC that 0.31.0 works fine on -current.
@chexmix, assuming this works for you, can you please edit the title of this thread and add [SOLVED] or something so folks browsing the list of threads will know the issue has been addressed? thanks.
Someone else confirmed in IRC that 0.31.0 works fine on -current.
@chexmix, assuming this works for you, can you please edit the title of this thread and add [SOLVED] or something so folks browsing the list of threads will know the issue has been addressed? thanks.
Done. I managed to install 0.31.0 remotely and it works like a charm - just like it always has!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.