Page 1 of 2
FAQ: Please read this first!
Posted: Wed Jun 13, 2007 11:52 pm
by andar
The FAQ is on our main site,
http://deluge-torrent.org/faq.php
Please, please please go there and read before posting for help. Otherwise you will be chastised
We have a lot of stuff to do and we'd rather be programming instead of answering the same question over and over again.
LFS installation
Posted: Sun Jun 17, 2007 6:33 pm
by xio
Two tips about installation on LFS (for deluge-svn rev. 659):
1. If boost (version 1.33.1 for me) is compiled from sources, then it is necessary to make a symlink in include dir from 'boost-1_33_1/boost/' to 'boost', like this:
Code: Select all
blacksun-2 : root [~] # ln -s /usr/include/{boost-1_33_1/boost,boost}
blacksun-2 : root [~] # ll /usr/include/boost
lrwxrwxrwx 1 root root 31 2007-06-17 20:38 /usr/include/boost -> /usr/include/boost-1_33_1/boost/
2. Boost-1.33.1 installs '*-mt' libs with 'gcc' prefix:
Code: Select all
blacksun-2 : root [~] # paco -fx boost | grep gcc-mt.so
/usr/lib/libboost_date_time-gcc-mt.so
/usr/lib/libboost_filesystem-gcc-mt.so
/usr/lib/libboost_iostreams-gcc-mt.so
/usr/lib/libboost_prg_exec_monitor-gcc-mt.so
/usr/lib/libboost_program_options-gcc-mt.so
/usr/lib/libboost_python-gcc-mt.so
/usr/lib/libboost_regex-gcc-mt.so
/usr/lib/libboost_serialization-gcc-mt.so
/usr/lib/libboost_signals-gcc-mt.so
/usr/lib/libboost_test_exec_monitor-gcc-mt.so
/usr/lib/libboost_thread-gcc-mt.so
/usr/lib/libboost_unit_test_framework-gcc-mt.so
/usr/lib/libboost_wserialization-gcc-mt.so
, but deluge isn't aware of this:
Code: Select all
blacksun-1 : io [~/build/deluge] $ cat setup.py | grep -- -mt
librariestype = ['boost_filesystem-mt', 'boost_date_time-mt',
'boost_thread-mt', 'z', 'pthread', 'ssl']
So in order to build deluge, we have to either make symlinks in /usr/lib or to modify setup.py file. I choose the second variant:
Code: Select all
blacksun-1 : io [~/build/deluge] $ sed -i s/-mt/-gcc-mt/g setup.py
blacksun-1 : io [~/build/deluge] $ cat setup.py | grep -- -mt
librariestype = ['boost_filesystem-gcc-mt', 'boost_date_time-gcc-mt',
'boost_thread-gcc-mt', 'z', 'pthread', 'ssl']
3. Build process should now finish without errors.
Re: FAQ: Please read this first!
Posted: Thu Jul 05, 2007 5:14 pm
by shirish
nicely compiled andar
Re: FAQ: Please read this first!
Posted: Sat Aug 11, 2007 2:19 am
by marcus
HI
I'm running PClinuxOS 2007 and I don't have Libboost-filesystem-dev. I've looked around and I don't seem to be able to find source code either.
I've installed all the Libboost systems from my repositories and the Install is still complaining the above is missing. Does it have a dfferent name or something. I have looked on boost.org, but there doesn't seem to be a seperate package for this there.
I want to upgrade from 5.3 (which is inmy repository) because it crashes without warning or notice at adhoc times, but its the best client I've come accross for Linux yet
Re: FAQ: Please read this first!
Posted: Sat Aug 11, 2007 2:30 am
by markybob
marcus wrote:HI
I'm running PClinuxOS 2007 and I don't have Libboost-filesystem-dev. I've looked around and I don't seem to be able to find source code either.
I've installed all the Libboost systems from my repositories and the Install is still complaining the above is missing. Does it have a dfferent name or something. I have looked on boost.org, but there doesn't seem to be a seperate package for this there.
I want to upgrade from 5.3 (which is inmy repository) because it crashes without warning or notice at adhoc times, but its the best client I've come accross for Linux yet
you should go to pclinuxos's irc channel or forum and ask them. i havent the slightest idea what they call things there
Re: FAQ: Please read this first!
Posted: Mon Aug 27, 2007 6:00 pm
by stanks
$ rm ~/.config/deluge
You need to add -r, because you have to remove directory not file.
$ rm -r ~/.config/deluge
Re: FAQ: Please read this first!
Posted: Tue Sep 18, 2007 12:10 am
by Montsegur87
One dependecy to this guide is subversion itself , add subversion package.
Code: Select all
sudo apt-get install g++ python-all-dev python-all python-dbus python-gtk2 python-xdg python-support libboost-dev libboost-thread-dev libboost-date-time-dev libboost-filesystem-dev libboost-serialization-dev libssl-dev zlib1g-dev subversion
Re: FAQ: Please read this first!
Posted: Tue Oct 09, 2007 5:02 pm
by csulok
how does one create a .deb package with the install commands? usually checkinstall does this for ubuntu, using c/c++ source codes, however i have little to no experience with python scripts.. is it different?
Re: FAQ: Please read this first!
Posted: Fri Oct 12, 2007 3:26 pm
by nepbabu.cx
On my Debian machine, deluge worked flawlessly. However on Ubuntu Feisty using Xfce, after 'make install' it showed problem. On close examination, the problem was:
Code: Select all
$ deluge
Traceback (most recent call last):
File "/usr/bin/deluge", line 112, in <module>
bus = dbus.SessionBus()
File "/var/lib/python-support/python2.5/dbus/_dbus.py", line 669, in __new__
mainloop=mainloop)
File "/var/lib/python-support/python2.5/dbus/_dbus.py", line 293, in __new__
mainloop=mainloop)
dbus.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
The problem occured because, somehow, session bus above (bus = dbus.SessionBus( ) ) couldn't be started and hence an exception 'dbus.DBusException: org.freedesktop.DBus.Error.NoReply' occured.
To solve this, start deluge like this instead:
and pray that it works.
Re: FAQ: Please read this first!
Posted: Thu Nov 01, 2007 8:57 pm
by Dragoon
...
The problem occured because, somehow, session bus above (bus = dbus.SessionBus( ) ) couldn't be started and hence an exception 'dbus.DBusException: org.freedesktop.DBus.Error.NoReply' occured.
To solve this, start deluge like this instead:
and pray that it works.
Thanks! This worked for me.
Is there any chance of getting this fixed? Or do I have to remember to do this every time.