LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 03-03-2010, 09:07 PM   #1
chexmix
Member
 
Registered: Apr 2002
Location: Arlington, MA
Distribution: Slackware, Debian, OpenBSD
Posts: 246
Blog Entries: 16

Rep: Reputation: 25
[SOLVED] sbopkg: b0rked by bash upgrade in -current?


Good evening all -

I recently upgraded my -current box, and now when I try to run sbopkg I get the exact error described in the following thread:

http://www.linuxquestions.org/questi...ssage.-751593/

The error fwiw is as follows:

root@catbutt:~# sbopkg
ERROR
sbopkg: Invalid repository descriptor

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
 
Old 03-03-2010, 09:31 PM   #2
chess
Member
 
Registered: Mar 2002
Location: 127.0.0.1
Distribution: Slackware and OpenBSD
Posts: 740

Rep: Reputation: 190Reputation: 190
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?

Last edited by chess; 03-03-2010 at 09:34 PM.
 
Old 03-03-2010, 09:38 PM   #3
damgar
Senior Member
 
Registered: Sep 2009
Location: dallas, tx
Distribution: Slackware - current multilib/gsb Arch
Posts: 1,949
Blog Entries: 8

Rep: Reputation: 203Reputation: 203Reputation: 203
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.

Last edited by damgar; 03-03-2010 at 10:23 PM.
 
Old 03-04-2010, 05:41 AM   #4
BroX
Member
 
Registered: Oct 2003
Location: Sweden
Distribution: Slackware64-current, SlackwareARM-15.0
Posts: 833

Rep: Reputation: 90
Upgrading sbopkg to 0.31.0 solved this issue for me.
 
Old 03-04-2010, 05:41 AM   #5
chexmix
Member
 
Registered: Apr 2002
Location: Arlington, MA
Distribution: Slackware, Debian, OpenBSD
Posts: 246

Original Poster
Blog Entries: 16

Rep: Reputation: 25
Quote:
Originally Posted by chess View Post
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.
 
Old 03-04-2010, 08:04 AM   #6
chess
Member
 
Registered: Mar 2002
Location: 127.0.0.1
Distribution: Slackware and OpenBSD
Posts: 740

Rep: Reputation: 190Reputation: 190
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.
 
Old 03-04-2010, 08:26 AM   #7
chexmix
Member
 
Registered: Apr 2002
Location: Arlington, MA
Distribution: Slackware, Debian, OpenBSD
Posts: 246

Original Poster
Blog Entries: 16

Rep: Reputation: 25
Quote:
Originally Posted by chess View Post
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!

Again, apologies for the premature post.

/gb
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Simple Shell Script is b0rked! r00tb00t Linux - Newbie 3 05-14-2009 07:34 PM
sound b0rked... ph00ka Slackware 1 09-09-2007 09:53 AM
Network b0rked? hacker supreme Linux - Networking 5 06-24-2007 06:10 PM
DISCUSSION: Upgrade to Slackware -current without a -current CD truthfatal LinuxAnswers Discussion 0 09-19-2006 01:42 PM
What first upgrade kernel or upgrade slack 10.0 to current Kelean Slackware 7 01-16-2005 06:54 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 11:24 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration