a query

General support for problems installing or using Deluge
Post Reply
shirish
Seeder
Seeder
Posts: 163
Joined: Fri May 25, 2007 4:01 am
Location: South Asia, India

a query

Post by shirish »

Hi all,
I know/knew only 5 commands for svn :-

Code: Select all

svn info deluge
svn co deluge
OR

Code: Select all

cd deluge
svn up
e.g.

Code: Select all

shirish@ubuntu:~$ svn info deluge
Path: deluge
URL: http://deluge-torrent.org/svn/trunk
Repository Root: http://deluge-torrent.org/svn
Repository UUID: b3ab561c-7021-0410-825b-ae720ed029d9
Revision: 963
Node Kind: directory
Schedule: normal
Last Changed Author: plisk
Last Changed Rev: 963
Last Changed Date: 2007-07-15 09:59:25 +0530 (Sun, 15 Jul 2007)

shirish@ubuntu:~$ cd deluge
shirish@ubuntu:~/deluge$ svn up
U    plugins/DesiredRatio/__init__.py
U    libtorrent/src/storage.cpp
U    libtorrent/src/piece_picker.cpp
U    src/common.py
U    src/interface.py
U    glade/dgtkpopups.glade
Updated to revision 966.
Now the next commands I know/knew are/were :-

Code: Select all

make clean
with e.g.

Code: Select all

shirish@ubuntu:~/deluge$ make clean
python setup.py clean
Attempting to detect your system information
32bit x86 system detected
Linux operating system detected
Libraries mt
running clean
removing 'build/temp.linux-i686-2.5' (and everything under it)
rm -rf ./build
rm msgfmt.pyc
find . -name *.pyc -exec rm {} \;
Now eternalswd told me that make clean should be used only when files are added/changed in the libtorrent directory or when deluge core.cpp is changed Hence :-

Code: Select all

shirish@ubuntu:~/deluge$ svn up
A    plugins/FirstLast
A    plugins/FirstLast/__init__.py
U    libtorrent/include/libtorrent/alert_types.hpp
U    src/core.py
U    src/interface.py
U    src/deluge_core.cpp
U    po/deluge.pot
Updated to revision 968.
See the entries about additions to libtorrent and change to deluge_core , because of this now make clean is needed.

Code: Select all

U    libtorrent/include/libtorrent/alert_types.hpp
U    src/deluge_core.cpp
The next ones which I know/knew are :-

Code: Select all

python setup.py build
sudo python setup.py install
with e.g.

Code: Select all

shirish@ubuntu:~/deluge$ python setup.py build
Attempting to detect your system information
32bit x86 system detected
Linux operating system detected
Libraries mt
running build
running build_py
creating build
creating build/lib.linux-i686-2.5
creating build/lib.linux-i686-2.5/deluge
copying src/__init__.py -> build/lib.linux-i686-2.5/deluge
copying src/plugins.py -> build/lib.linux-i686-2.5/deluge
copying src/common.py -> build/lib.linux-i686-2.5/deluge
copying src/core.py -> build/lib.linux-i686-2.5/deluge
copying src/interface.py -> build/lib.linux-i686-2.5/deluge
copying src/deluge_stats.py -> build/lib.linux-i686-2.5/deluge
copying src/dialogs.py -> build/lib.linux-i686-2.5/deluge
copying src/dgtk.py -> build/lib.linux-i686-2.5/deluge
copying src/pref.py -> build/lib.linux-i686-2.5/deluge
copying src/ipc_manager.py -> build/lib.linux-i686-2.5/deluge
running build_ext
building 'deluge_core' extension
creating build/temp.linux-i686-2.5
creating build/temp.linux-i686-2.5/libtorrent
creating build/temp.linux-i686-2.5/libtorrent/src
creating build/temp.linux-i686-2.5/libtorrent/src/kademlia
creating build/temp.linux-i686-2.5/src
gcc -pthread -fno-strict-aliasing -O2 -Wall -fPIC -I./libtorrent -I./libtorrent/include -I./libtorrent/include/libtorrent -I/usr/include/python2.5 -I/usr/include/python2.5 -c libtorrent/src/torrent.cpp -o build/temp.linux-i686-2.5/libtorrent/src/torrent.o -Wno-missing-braces -DHAVE_INCLUDE_LIBTORRENT_ASIO____ASIO_HPP=1 -DHAVE_INCLUDE_LIBTORRENT_ASIO_SSL_STREAM_HPP=1 -DHAVE_INCLUDE_LIBTORRENT_ASIO_IP_TCP_HPP=1 -DHAVE_PTHREAD=1 -DTORRENT_USE_OPENSSL=1 -DHAVE_SSL=1 -DNDEBUG -O2
Now the process told just above is known as compiling and would take anywhere from 15-20 mins. or more depending on processor speed as well as memory (perhaps) . At the end of the compiling people will get something like this :-

Code: Select all

Compiling po/ar.po
Compiling po/en_GB.po
Compiling po/pl.po
Compiling po/pt.po
Compiling po/tlh.po
Compiling po/ko.po
Compiling po/ta.po
Compiling po/da.po
Compiling po/et.po
Compiling po/he.po
Compiling po/uk.po
Compiling po/ast.po
Compiling po/sl.po
Compiling po/gl.po
Compiling po/tr.po
Compiling po/id.po
Compiling po/ca.po
Compiling po/sv.po
Compiling po/bg.po
Compiling po/sr.po
Compiling po/lt.po
Compiling po/fi.po
Compiling po/it.po
Compiling po/de.po
Compiling po/en_CA.po
Compiling po/eu.po
Compiling po/la.po
Compiling po/ja.po
Compiling po/es.po
Compiling po/ro.po
Compiling po/nl.po
Compiling po/hr.po
Compiling po/en_AU.po
Compiling po/sk.po
Compiling po/lv.po
Compiling po/cs.po
Compiling po/zh_TW.po
Compiling po/pt_BR.po
Compiling po/fr.po
Compiling po/el.po
Compiling po/zh_CN.po
Compiling po/hu.po
Compiling po/nb.po
Compiling po/ru.po
Those I guess are the translations.

The last stage in the cycle was :-

Code: Select all

shirish@ubuntu:~/deluge$ sudo python setup.py install
Attempting to detect your system information
32bit x86 system detected
Linux operating system detected
Libraries mt
running install
running build
running build_py
running build_ext
running build_scripts
running build_trans
running write_data_install_path
running install_lib
copying build/lib.linux-i686-2.5/deluge/deluge_core.so -> /usr/lib/python2.5/site-packages/deluge
copying build/lib.linux-i686-2.5/deluge/common.py -> /usr/lib/python2.5/site-packages/deluge
copying build/lib.linux-i686-2.5/deluge/interface.py -> /usr/lib/python2.5/site-packages/deluge
byte-compiling /usr/lib/python2.5/site-packages/deluge/common.py to common.pyc
byte-compiling /usr/lib/python2.5/site-packages/deluge/interface.py to interface.pyc
running install_scripts
copying build/scripts-2.5/deluge -> /usr/bin
changing mode of /usr/bin/deluge to 755
running install_data
copying glade/dgtkpopups.glade -> /usr/share/deluge/glade
copying plugins/DesiredRatio/__init__.py -> /usr/share/deluge/plugins/DesiredRatio
copying build/locale/zh_CN/LC_MESSAGES/deluge.mo -> /usr/share/locale/zh_CN/LC_MESSAGES
copying build/locale/ko/LC_MESSAGES/deluge.mo -> /usr/share/locale/ko/LC_MESSAGES
copying build/locale/en_GB/LC_MESSAGES/deluge.mo -> /usr/share/locale/en_GB/LC_MESSAGES
copying build/locale/sl/LC_MESSAGES/deluge.mo -> /usr/share/locale/sl/LC_MESSAGES
copying build/locale/hr/LC_MESSAGES/deluge.mo -> /usr/share/locale/hr/LC_MESSAGES
copying build/locale/en_AU/LC_MESSAGES/deluge.mo -> /usr/share/locale/en_AU/LC_MESSAGES
copying build/locale/de/LC_MESSAGES/deluge.mo -> /usr/share/locale/de/LC_MESSAGES
copying build/locale/ca/LC_MESSAGES/deluge.mo -> /usr/share/locale/ca/LC_MESSAGES
copying build/locale/cs/LC_MESSAGES/deluge.mo -> /usr/share/locale/cs/LC_MESSAGES
copying build/locale/fr/LC_MESSAGES/deluge.mo -> /usr/share/locale/fr/LC_MESSAGES
copying build/locale/ta/LC_MESSAGES/deluge.mo -> /usr/share/locale/ta/LC_MESSAGES
copying build/locale/id/LC_MESSAGES/deluge.mo -> /usr/share/locale/id/LC_MESSAGES
copying build/locale/ast/LC_MESSAGES/deluge.mo -> /usr/share/locale/ast/LC_MESSAGES
copying build/locale/nl/LC_MESSAGES/deluge.mo -> /usr/share/locale/nl/LC_MESSAGES
copying build/locale/en_CA/LC_MESSAGES/deluge.mo -> /usr/share/locale/en_CA/LC_MESSAGES
copying build/locale/lv/LC_MESSAGES/deluge.mo -> /usr/share/locale/lv/LC_MESSAGES
copying build/locale/pl/LC_MESSAGES/deluge.mo -> /usr/share/locale/pl/LC_MESSAGES
copying build/locale/it/LC_MESSAGES/deluge.mo -> /usr/share/locale/it/LC_MESSAGES
copying build/locale/eu/LC_MESSAGES/deluge.mo -> /usr/share/locale/eu/LC_MESSAGES
copying build/locale/uk/LC_MESSAGES/deluge.mo -> /usr/share/locale/uk/LC_MESSAGES
copying build/locale/la/LC_MESSAGES/deluge.mo -> /usr/share/locale/la/LC_MESSAGES
copying build/locale/sr/LC_MESSAGES/deluge.mo -> /usr/share/locale/sr/LC_MESSAGES
copying build/locale/tlh/LC_MESSAGES/deluge.mo -> /usr/share/locale/tlh/LC_MESSAGES
copying build/locale/pt_BR/LC_MESSAGES/deluge.mo -> /usr/share/locale/pt_BR/LC_MESSAGES
copying build/locale/ja/LC_MESSAGES/deluge.mo -> /usr/share/locale/ja/LC_MESSAGES
copying build/locale/da/LC_MESSAGES/deluge.mo -> /usr/share/locale/da/LC_MESSAGES
copying build/locale/ro/LC_MESSAGES/deluge.mo -> /usr/share/locale/ro/LC_MESSAGES
copying build/locale/el/LC_MESSAGES/deluge.mo -> /usr/share/locale/el/LC_MESSAGES
copying build/locale/lt/LC_MESSAGES/deluge.mo -> /usr/share/locale/lt/LC_MESSAGES
copying build/locale/nb/LC_MESSAGES/deluge.mo -> /usr/share/locale/nb/LC_MESSAGES
copying build/locale/tr/LC_MESSAGES/deluge.mo -> /usr/share/locale/tr/LC_MESSAGES
copying build/locale/bg/LC_MESSAGES/deluge.mo -> /usr/share/locale/bg/LC_MESSAGES
copying build/locale/ru/LC_MESSAGES/deluge.mo -> /usr/share/locale/ru/LC_MESSAGES
copying build/locale/et/LC_MESSAGES/deluge.mo -> /usr/share/locale/et/LC_MESSAGES
copying build/locale/fi/LC_MESSAGES/deluge.mo -> /usr/share/locale/fi/LC_MESSAGES
copying build/locale/gl/LC_MESSAGES/deluge.mo -> /usr/share/locale/gl/LC_MESSAGES
copying build/locale/sk/LC_MESSAGES/deluge.mo -> /usr/share/locale/sk/LC_MESSAGES
copying build/locale/he/LC_MESSAGES/deluge.mo -> /usr/share/locale/he/LC_MESSAGES
copying build/locale/hu/LC_MESSAGES/deluge.mo -> /usr/share/locale/hu/LC_MESSAGES
copying build/locale/es/LC_MESSAGES/deluge.mo -> /usr/share/locale/es/LC_MESSAGES
copying build/locale/pt/LC_MESSAGES/deluge.mo -> /usr/share/locale/pt/LC_MESSAGES
copying build/locale/sv/LC_MESSAGES/deluge.mo -> /usr/share/locale/sv/LC_MESSAGES
copying build/locale/zh_TW/LC_MESSAGES/deluge.mo -> /usr/share/locale/zh_TW/LC_MESSAGES
copying build/locale/ar/LC_MESSAGES/deluge.mo -> /usr/share/locale/ar/LC_MESSAGES
running install_egg_info
Removing /usr/lib/python2.5/site-packages/deluge-0.5.2.90.egg-info
Writing /usr/lib/python2.5/site-packages/deluge-0.5.2.90.egg-info
running unwrite_data_install_path
That was the installation thing. Now 2 derivative commands of the same are

Code: Select all

make
for

Code: Select all

sudo python setup.py build
as well as

Code: Select all

sudo python setup.py install
for

Code: Select all

sudo make install
Thanx markybob. Finally

Code: Select all

sudo make uninstall
when one doesn't need deluge-torrent anymore although why somebody wouldn't want it is beyond me but its useful in case when we mess something up big (atleast that's the way I see it).
Last edited by shirish on Sun Jul 15, 2007 9:54 am, edited 3 times in total.
Debian Sid, Intel Dual-Core, 512 kbps DL , 64 Kbps UL, deluge-1.3.5, pieces plugin, GNOME 3.4.x

All posts under creative commons http://creativecommons.org/licenses/by-nc/3.0/
Top
markybob
Compulsive Poster
Compulsive Poster
Posts: 1230
Joined: Thu May 24, 2007 11:27 pm
Location: Chicago, IL, USA
Contact:
Contact markybob

Re: a query

Post by markybob »

you should make clean when any cpp files are altered. this includes all the files in the libtorrent dir and deluge_core.cpp. make is the exact same as python setup.py build and make install is the exact same as python setup.py install
Top
shirish
Seeder
Seeder
Posts: 163
Joined: Fri May 25, 2007 4:01 am
Location: South Asia, India

Re: a query

Post by shirish »

Thanx markybob. another thing on gutsy all the libboost libraries are 1.34 hence :-

Code: Select all

shirish@ubuntu:~$ aptitude search libboost
i   libboost-date-time-dev                         - set of date-time libraries based on generic programming
i A libboost-date-time1.34.0                     - set of date-time libraries based on generic programming
i   libboost-dev                                          - Boost C++ Libraries development files
i   libboost-filesystem-dev                      - filesystem operations (portable paths, iteration over directories, etc) in C++
i A libboost-filesystem1.34.0                    - filesystem operations (portable paths, iteration over  directories, etc) in C++
i   libboost-regex1.34.0                         - regular expression library for C++                     
i   libboost-serialization-dev                   - serialization library for C++                          
i A libboost-serialization1.34.0                 - serialization library for C++                          
i   libboost-thread-dev                          - portable C++ multi-threading                           
i A libboost-thread1.34.0                        - portable C++ multi-threading
Just to show you one of the packages :-

Code: Select all

Package: libboost-filesystem-dev
State: installed
Automatically installed: no
Version: 1.34.0-1ubuntu2
Priority: optional
Section: universe/libdevel
Maintainer: Ubuntu Core developers <ubuntu-devel-discuss@lists.ubuntu.com>
Uncompressed Size: 410k
Depends: libboost-dev (= 1.34.0-1ubuntu2), libboost-filesystem1.34.0 (= 1.34.0-1ubuntu2)
Replaces: libboost-dev (< 1.31.0-1)
Description: filesystem operations (portable paths, iteration over directories, etc) in C++
 Part of the Boost C++ Libraries collection. 
 
 The Boost Filesystem Library provides portable facilities to query and manipulate paths, files, and
 directories.  The goal is to facilitate portable script-like operations from within C++ programs. 
 
 Homepage: http://boost.org/libs/filesystem/
Changelog of one of the libraries, maybe it might help you guys :-

Code: Select all

boost (1.34.0-1ubuntu2) gutsy; urgency=low

  * Explicitely build using gcc-4.1 and g++-4.1.
  * Set Ubuntu maintainer address.

 -- Matthias Klose <doko@ubuntu.com>  Tue, 03 Jul 2007 13:30:28 +0000

boost (1.34.0-1ubuntu1) gutsy; urgency=low

  * Merge with Debian; remaining changes:
    - pyste: drop dependencies on python-celementtree | python-elementtree.
    - GCCXMLParser.py: Use ElementTree from the python2.5 standard library.

 -- Matthias Klose <doko@ubuntu.com>  Wed, 16 May 2007 19:32:54 +0200

boost (1.34.0-1) unstable; urgency=low

  * New upstream release.
  * libboost-doc is properly created and filled, also on hppa (closes: #406883).

 -- Domenico Andreoli <cavok@debian.org>  Mon, 14 May 2007 00:06:49 +0200

boost (1.34.0~rc2-2) experimental; urgency=low

  * Re-applied workaround for toolchain bug on hppa (closes: #416496).
  * Partially synchronized with Ubuntu:
    - removed "python |" as alternative build dependency
    - libboost-python-dev now depends on python2.5-dev

 -- Domenico Andreoli <cavok@debian.org>  Thu, 10 May 2007 23:22:20 +0200

boost (1.34.0~rc2-1) experimental; urgency=low

  * Removed debian-specific virtual destructors of
    polymorphic_iarchive and polymorphic_oarchive. see
    http://lists.boost.org/Archives/boost/2006/09/110979.php.
  * Bumped shlibs to (>= 1.34.0~rc2-1), ABI might be changed since the
    first introduction of 1.34.0 snapshot from CVS almost a year ago.

 -- Domenico Andreoli <cavok@debian.org>  Thu, 10 May 2007 12:33:32 +0200

boost (1.34.0~beta1-2) experimental; urgency=low

  * libboost-serialization-dev now depends on libboost-serialization1.34.0,
    libboost-wave-dev on libboost-wave1.34.0.
  * Build depends on g++-4.1 (>= 4.1.2).

 -- Domenico Andreoli <cavok@debian.org>  Mon, 30 Apr 2007 17:26:55 +0200

boost (1.34.0~beta1-1) experimental; urgency=low

  * New upstream beta release.
  * Boost.Python is built using python 2.5.

 -- Domenico Andreoli <cavok@debian.org>  Sat, 28 Apr 2007 01:08:50 +0200

boost (1.33.1+1.34.0-cvs20070326-1) experimental; urgency=low

  * New upstream snapshot version.
  * Added missing shared library packages of Boost.Serialization and
    Boost.Wave.  Closes: #410157.
  * No unqualified .so symlinks are now provided, only -st.so/-mt.so
    are available.  Closes: #356705.

 -- Domenico Andreoli <cavok@debian.org>  Tue, 27 Mar 2007 13:50:30 +0200

boost (1.33.1+1.34.0-cvs20070221-1) experimental; urgency=low

  * New upstream snapshot version.
  * Improved the build process.
  * Now both st/mt variants are installed as well as their new symlinks
    to ease the linking. No, we still have not pkg-config support.

 -- Domenico Andreoli <cavok@debian.org>  Fri, 23 Mar 2007 13:47:15 +0100

boost (1.33.1+1.34.0-cvs20060531-1) experimental; urgency=low

  * New upstream snapshot version.
  * CSS file for HTML documentation is now correctly installed.
    Closes: #358986.
  * Standards-Version is now set to 3.7.2.

 -- Domenico Andreoli <cavok@debian.org>  Wed, 31 May 2006 16:09:49 +0200

boost (1.33.1-10) unstable; urgency=medium

  * boost/detail/sp_counted_base_gcc_ia64.hpp,
This is so everybody knows what libraries the users on gutsy are using. I would be updating this as & when anything new happens.
Cheers!
Debian Sid, Intel Dual-Core, 512 kbps DL , 64 Kbps UL, deluge-1.3.5, pieces plugin, GNOME 3.4.x

All posts under creative commons http://creativecommons.org/licenses/by-nc/3.0/
Top
Post Reply

Return to “Support”