Having upgrade from net-p2p/deluge-1.3.1 to net-p2p/deluge-1.3.2 I discovered on my amd64 machine that deluge cannot start in 'classic mode'. When starting it displays a dialog with the following error message ---snip-- Traceback (most recent call last): File "/usr/lib64/python2.7/site-packages/deluge/ui/gtkui/gtkui.py", line 295, in _on_reactor_start client.start_classic_mode() File "/usr/lib64/python2.7/site-packages/deluge/ui/client.py", line 559, in start_classic_mode self._daemon_proxy = DaemonClassicProxy(self.__event_handlers) File "/usr/lib64/python2.7/site-packages/deluge/ui/client.py", line 432, in __init__ self.__daemon = deluge.core.daemon.Daemon(classic=True) File "/usr/lib64/python2.7/site-packages/deluge/core/daemon.py", line 136, in __init__ from deluge.core.core import Core File "/usr/lib64/python2.7/site-packages/deluge/core/core.py", line 36, in <module> from deluge._libtorrent import lt File "/usr/lib64/python2.7/site-packages/deluge/_libtorrent.py", line 59, in <module> import libtorrent as lt ImportError: dynamic module does not define init function (initlibtorrent) ---snip--- My first step was to run python-updater, which had no effect on the problem. Then I did a little digging and found this forum post (http://forum.deluge-torrent.org/viewtopic.php?f=7&t=36755) which mentions deluge depends on libtorrent. I checked whether libtorrent was installed, and it wasn't. `equery depends libtorrent` also list no application installed that depend on it, meaning that neigher deluge nor any of its dependencies depend on libtorrent. I manually emerged libtorrent, then reemerged deluge, and now it works. The ebuild should be modified to include libtorrent in its RDEPENDs.
Hard to tell what exactly your problem was, but the dep is already there - >=net-libs/rb_libtorrent-0.14.9[python].
Then why does `equery d libtorrent` not show anything up? Corrupted portage tree maybe?
