pyslsk package installation on RH9

Spacedog

ok, I've downloaded and installed Python 2.2 and wxPython, and still this doesn't work. I cant fine a 'install' file, which is supposed to provide help. why is it so complicated to install a simple program in linux. grrr.

I got the package from here...
http://www.sensi.org/~ak/pyslsk/

any thoughts?

[root@localhost spacedog]# pyslsk
You do not have Python Vorbis bindings installed.
Others will not be able to see the lengths and the bitrates
of Ogg Vorbis files that you share. Get binary RPMS from the pyslsk homepage
or the source from http://www.andrewchatham.com/pyogg/.
If you're using Debian, install the python-pyvorbis package.
Traceback (most recent call last):
File "/usr/bin/pyslsk", line 88, in ?
app = frame.MainApp(config)
File "/usr/lib/python2.2/site-packages/pysoulseek/wxgui/frame.py", line 530, in __init__
wxApp.__init__(self)
File "/usr/lib/python2.2/site-packages/wx/core.py", line 5042, in __init__
self._BootstrapApp()
File "/usr/lib/python2.2/site-packages/wx/core.py", line 4791, in _BootstrapApp
return _core.PyApp__BootstrapApp(*args, **kwargs)
File "/usr/lib/python2.2/site-packages/pysoulseek/wxgui/frame.py", line 534, in OnInit
self.frame = MainFrame(None,-1,'PySoulSeek %s' % utils.version, self.config, self)
File "/usr/lib/python2.2/site-packages/pysoulseek/wxgui/frame.py", line 97, in __init__
self.configwindow = ConfigWindow(self, -1, "Settings")
File "/usr/lib/python2.2/site-packages/pysoulseek/wxgui/configwindow.py", line 414, in __init__
self.transferspanel = TransfersPanel(nb, self)
File "/usr/lib/python2.2/site-packages/pysoulseek/wxgui/configwindow.py", line 232, in __init__
limitsizer.Add(0,0)
File "/usr/lib/python2.2/site-packages/wx/core.py", line 8242, in Add
return _core.Sizer_Add(*args, **kwargs)
TypeError: wxWindow, wxSizer, wxSize, or (w,h) expected for item


...from here it freezes until I ctrl+C

Ste-

http://nicotine.thegraveyard.org/

Try that instead.
Same program pretty much.


quick point the website says " Warning: if you compile PyGTK yourself, make sure you enable threading support by using ./configure --enable-thread " it should be threads.

I never got psyslsk to compile but nicotine runs like a dream.

Spacedog

Are all linux programs as hard to install as this, I thought RPM was suoopsed to simplify this instalation stuff? I'll try nicotine, but it's more an issue of being able to install stuff as opposed to getting slsk running.

I also need to find and install a driver for my sbLive value card, any thoughts of where to look?

Spacedog

ok, I'm trying to install pyogg and pyvorbis extentions before I start to install nicotine (as it recomends on the web site)...

[spacedog@localhost pyogg-1.3]$ python setup.py build
running build
running build_py
creating build
creating build/lib.linux-i686-2.2
creating build/lib.linux-i686-2.2/ogg
copying pysrc/__init__.py -> build/lib.linux-i686-2.2/ogg
running build_ext
building '_ogg' extension
creating build/temp.linux-i686-2.2
gcc -DNDEBUG -O2 -g -pipe -march=i386 -mcpu=i686 -D_GNU_SOURCE -fPIC -fPIC -DVERSION_MAJOR=1 -DVERSION_MINOR=3 -DVERSION="1.3" -I/usr/local/include -Iinclude -I/usr/include/python2.2 -c src/_oggmodule.c -o build/temp.linux-i686-2.2/_oggmodule.o
gcc -DNDEBUG -O2 -g -pipe -march=i386 -mcpu=i686 -D_GNU_SOURCE -fPIC -fPIC -DVERSION_MAJOR=1 -DVERSION_MINOR=3 -DVERSION="1.3" -I/usr/local/include -Iinclude -I/usr/include/python2.2 -c src/pyoggpacket.c -o build/temp.linux-i686-2.2/pyoggpacket.o
gcc -DNDEBUG -O2 -g -pipe -march=i386 -mcpu=i686 -D_GNU_SOURCE -fPIC -fPIC -DVERSION_MAJOR=1 -DVERSION_MINOR=3 -DVERSION="1.3" -I/usr/local/include -Iinclude -I/usr/include/python2.2 -c src/pyoggstreamstate.c -o
build/temp.linux-i686-2.2/pyoggstreamstate.o
gcc -DNDEBUG -O2 -g -pipe -march=i386 -mcpu=i686 -D_GNU_SOURCE -fPIC -fPIC -DVERSION_MAJOR=1 -DVERSION_MINOR=3 -DVERSION="1.3" -I/usr/local/include -Iinclude -I/usr/include/python2.2 -c src/pyoggpage.c -o build/temp.linux-i686-2.2/pyoggpage.o
gcc -DNDEBUG -O2 -g -pipe -march=i386 -mcpu=i686 -D_GNU_SOURCE -fPIC -fPIC -DVERSION_MAJOR=1 -DVERSION_MINOR=3 -DVERSION="1.3" -I/usr/local/include -Iinclude -I/usr/include/python2.2 -c src/pyoggpackbuff.c -o build/temp.linux-i686-2.2/pyoggpackbuff.o
gcc -DNDEBUG -O2 -g -pipe -march=i386 -mcpu=i686 -D_GNU_SOURCE -fPIC -fPIC -DVERSION_MAJOR=1 -DVERSION_MINOR=3 -DVERSION="1.3" -I/usr/local/include -Iinclude -I/usr/include/python2.2 -c src/pyoggsyncstate.c -o build/temp.linux-i686-2.2/pyoggsyncstate.o
gcc -DNDEBUG -O2 -g -pipe -march=i386 -mcpu=i686 -D_GNU_SOURCE -fPIC -fPIC -DVERSION_MAJOR=1 -DVERSION_MINOR=3 -DVERSION="1.3" -I/usr/local/include -Iinclude -I/usr/include/python2.2 -c src/general.c -o build/temp.linux-i686-2.2/general.o
gcc -shared build/temp.linux-i686-2.2/_oggmodule.o build/temp.linux-i686-2.2/pyoggpacket.o build/temp.linux-i686-2.2/pyoggstreamstate.o build/temp.linux-i686-2.2/pyoggpage.o build/temp.linux-i686-2.2/pyoggpackbuff.o build/temp.linux-i686-2.2/pyoggsyncstate.o build/temp.linux-i686-2.2/general.o -L/usr/local/lib -logg
-o build/lib.linux-i686-2.2/ogg/_ogg.so
[spacedog@localhost pyogg-1.3]$ cd ..
[spacedog@localhost spacedog]$ cd pyvorbis-1.3
[spacedog@localhost pyvorbis-1.3]$ python config_unix.py
Checking for Ogg ... success
Checking for Vorbis ... success
Wrote Setup file
[spacedog@localhost pyvorbis-1.3]$ python setup.py build
You must have the Ogg Python bindings
installed in order to build and install
these bindings. Import of ogg._ogg failed.


now I'm lost again! this is jibberish!

Ste-

I didn't bother with the pyvorbis etc plugins.
They are only needed for others to see what bitrate your stuff is.
It's easier without.
I tend not to install rpms but only as a last option as compiling the source code I find a lot easier.

As for your sound card is the driver not supplied ?
Most new distos use the emu10k1 driver for that sound card iirc.
I have the sb platinum live drive soundcard it uses that driver.
Have a look at http://sourceforge.net/projects/emu10k1 and http://opensource.creative.com/

Spacedog

This is me trying to install the emu driver...

[spacedog@localhost spacedog]$ cd emu10k1-v0.20a
[spacedog@localhost emu10k1-v0.20a]$ make
make -Cscripts
make[1]: Entering directory `/home/spacedog/emu10k1-v0.20a/scripts'
cc -I/lib/modules/`uname -r`/build/include get_version.c -o get_version
make -f /home/spacedog/emu10k1-v0.20a/scripts/Makefile.get_options -C /lib/modul
es/`uname -r`/build get_version_target
make[2]: Entering directory `/usr/src/linux-2.4.20-8'
**
** /lib/modules/2.4.20-8/build/.config is missing
** if this is a custom kernel then you need to run make config in /lib/modules/2
.4.20-8/build.
** if this is a distribution kernel then you need to copy the correct .config fi
le to /lib/modules/2.4.20-8/build.
** for RedHat kernels the .config file is one of the /lib/modules/2.4.20-8/build
/configs/*.config
**
make[2]: *** [get_version_target] Error 1
make[2]: Leaving directory `/usr/src/linux-2.4.20-8'
make[1]: *** [get_options] Error 2
make[1]: Leaving directory `/home/spacedog/emu10k1-v0.20a/scripts'
make: *** [opts] Error 2

...ok, I look at the readme...

2. Using RedHat distribution kernel sources.
Copy/link one of the config files in linux/configs/*.config
to linux/.config. The file should match your running kernel.

...WTF is:
1) linux/configs/*.config
2) linux/.config

Neither of these folders exist in the emu10k1-v0.20a or root folders. could they possibly make it less clear.

I don't want to like windows but someone's taking the piss, making it impossible to install anything in Linux.

Ste-

I found it hard at first aswell.
Have you thought about Fedora Core ?
I know the driver is included in that distro as I had it running the other day.
Not too sure about the errors you're getting, maybe one of the others could help.
./folder is a hidden folder by the way. anything with . in front is usually hidden if I'm not mistaken.

To turn on hidden folders in KDE drop down the view tab.
Hope this helps.


[edit] Did you get Nicotine running ?

Spacedog

no,

didn't get nicotine installed,
didn't get pyslsk installed,
didn't get python extentions installed,
didn't get sound drivers installed.
this :mad: :mad: :mad:


I just want to install something, anything, I've never been able to install a single program in linux because of crap like the above.

what ever happened to,

1) setup.exe
2) input install directory
DONE

I can only conclude that the open source community are a sadistic organisation of pure evil who plot to destroy the world be enraging everyone who attempts to use it's software to the extent of pure madness!

/me does a backflip through the nearest window and runs in circles screaming "woopwoopwoop!!!"

Ste-

I'm installing it myself at the moment so I'll post back in a bit when I get it working with what steps I took etc.

Ste-

Ok I now have it up and running with no problems.
First of make sure you have the following.

Requirements

Nicotine has the following dependecies:

* Python-2.2.0 or newer (Python 2.3 recommended due to improvements in the UTF-8 codec)
* GTK+-2.0 or newer (GTK+-2.2 recommended)
* PyGTK-1.99.16 or newer (older versions will NOT work)

I had problems with the latest PyGTK but 2.2 works so here's the link http://ftp.gnome.org/pub/GNOME/sources/pygtk/2.2/
When compiling that make sure to --enable-threads.

If you haven't got the other two try going into the add/remove programs in redhat (can't remember where it's located but go through the start menu)

Then downlaod the nicotine source code and simply "python ./nicotine"

Quick note you say you've never gotten anything to compile. Do you have the right compile tools installed ?
Gcc and C++ and other develop tools need to be installed, again check your add/remove programs.

Good Luck.
And stick with it. It gets easier.

hostyle

What distro are you using? Most distros have their own package management system: RPM, apt-get and others. Is the kernel source installed?

Generally when installing from source you cd into the unpacked directory, run ./configure, run make, and run make install. Sounds like you;re missing the ./cpmgogure step. Theres usually a README file and/or an INSTALL file in the base directory too. Have a look at that to see if their install procedure differs.

nadir

Spacedog: i feel your pain man, it was about 3 years ago, I had the exact same problem, I was trying to install pyslsk through rpm,-uromi on mandrake. I ended up completely b0rking the system, corrupted rpm data base and such, I fairly much had enough with mandrake, and moved to gentoo, python libs tend to break alot, which is annoying, incompatable version and such, and rpm playing havok with dependancy issues. In gentoo they have a python-update utility taht sorts out python specifically, cause of all the problems associated with it. so you cen just emerge pyslsk or nicotine and it works straight off.