Page 1 of 1

[SOLVED] Frostwire 4.20 (from 13.1 repo) not connecting

Posted: 18. Feb 2012, 09:53
by Dennola4
Hey guys,

I was originally going to post this as a problem, but I found a solution. I thought I'd post it anyway as a convenience to other SalixOS 13.1 users having the same problem.

Problem -- I launched Frostwire 4.20 (which is now far from current, but still works just fine). It got stuck at "starting to connect", but never actually connected.
Solution -- You must replace ~/.frostwire4.20/gnutella.net with this newer version of the file >> http://forum.frostwire.com/download/file.php?id=528

Hope this helps someone. ;)

-Dennis in New Orleans

Re: [SOLVED] Frostwire 4.20 (from 13.1 repo) not connecting

Posted: 18. Feb 2012, 10:24
by djemos

Re: [SOLVED] Frostwire 4.20 (from 13.1 repo) not connecting

Posted: 20. Feb 2012, 05:22
by Dennola4
djemos,

wow, thanks. Is the .txz file ready to install as-is? In other words, would I download it, become root with su -, then: # slack-installpkg foo.txz and that's it? Or does it need to be built using the Slackbuild script?

Sorry if this sounds like a dumb question, I'm just used to installing packages either:

a) from repo with Gslapt
b) with # slapt-src -i foo
c) building the Slackbuild following exact instructions on slackbuilds.org

Not sure what to do with the page you gave me. :oops:

Dennis in New Orleans

Re: [SOLVED] Frostwire 4.20 (from 13.1 repo) not connecting

Posted: 20. Feb 2012, 06:47
by Akuna
Ensure that you have the following dependencies already installed in your machine => http://people.salixos.org/djemos/frostw ... ch-1dj.dep
Then download http://people.salixos.org/djemos/frostw ... ch-1dj.txz
And install it 'manually' with spkg

Code: Select all

# spkg -i /path/to/frostwire-5.3.2-noarch-1dj.txz
replacing /path/to/ with your actual path to the downloaded file

Re: [SOLVED] Frostwire 4.20 (from 13.1 repo) not connecting

Posted: 20. Feb 2012, 07:13
by Dennola4
Hey Akuna,

Thanks for the quick response.

Just curious....is there a benefit to using spkg rather than installpkg, or vice-versa? The man page for spkg says it is the unofficial Slackware package manager. The man pages for installpkg/removepkg (which I typically use out of habit) describe the same basic functionality, only with a few extra arguments. So would these extra arguments be the only reason to use the latter? Do the commands function identically otherwise?

Anyway, it is installed and running. Thanks djemos and Akuna.

:mrgreen:

Re: [SOLVED] Frostwire 4.20 (from 13.1 repo) not connecting

Posted: 20. Feb 2012, 08:38
by djemos

Re: [SOLVED] Frostwire 4.20 (from 13.1 repo) not connecting

Posted: 20. Feb 2012, 09:23
by Dennola4
Thanks, djemos.

So what I have learned after reading the link and then Googling is that installpkg, removepkg, upgradepkg, etc are all a part of the original Slackware pkgtools suite. Spkg was developed later as a faster and more efficient alternative to pkgtools which can run side-by-side with it, but boasts notably faster speeds. Further, a quick look at http://spkg.megous.com/ suggests that the SalixOS team directly endorses spkg as an evolution of pkgtools, which helps make my choice clear when deciding which to use.

Thanks again.

:geek: