Deluge Forum

We have changed the style of the packages in the PPA to match the packages that Jaunty and Debian Experimental contain.

These packages don't currently contain a "Conflicts: deluge-torrent, deluge-torrent-common" in the control file so as a result the upgrade will fail saying you are trying to overwrite files contained in another package. The short-term solution for this is to simply: The source has also been split out so now there are the following packages:

deluge - gtk client
deluge-common - common data files for all interfaces
deluge-console - the console interface
deluge-gtk - gtk client
deluged - the deluge daemon
deluge-web - the webui interface

deluge-torrent - a metapackage to handle switching over from the package in previous versions of Ubuntu/Debian
deluge-webui - metapackage
deluge-core - obsolete

What happend to the OpenSSL dependency?

Does the PPA version of Deluge still support encrypted communication?

wuggu wrote:What happend to the OpenSSL dependency?

Does the PPA version of Deluge still support encrypted communication?

I saw Deluge do not depends anymore from openssl neither from python-openssl, but it still support

...
# BitTorrent Protocol Encryption
# Mainline DHT
...

and others feature. See http://dev.deluge-torrent.org/wiki/About

I suppose all this stack are now included directly in libtorrent library. Have faith!

openssl is still a dependency: http://dev.deluge-torrent.org/wiki/Installing/Source

deluge will always support encrypted communication (in fact trunk uses openssl for communicating between the daemon and a client).

Yes, and I said that 'deluge ... support encrypted communication',
but in facts, only deluge-webui package (talking' about Deluge from Launchpad PPA by Deluge team, Ubuntu) suggest (do not require!) python-openssl

elcamilo wrote:Yes, and I said that 'deluge ... support encrypted communication',
but in facts, only deluge-webui package (talking' about Deluge from Launchpad PPA by Deluge team, Ubuntu) suggest (do not require!) python-openssl

If you are building the included libtorrent then you need openssl. If you install the libtorrent package separately then it should install openssl as a dependency. The webui has an optional dependency on pyopenssl if you want to use https.

Are you aware that installing the 1.2.0_rc1 update on Ubuntu jaunty breaks deluge completely? deluge-common depends on deluge-core being 1.2.0, but the version in repo is 1.1.9. This means that deluged doesn't install. Which means nothing can run.

diablo_man5666 wrote:Are you aware that installing the 1.2.0_rc1 update on Ubuntu jaunty breaks deluge completely? deluge-common depends on deluge-core being 1.2.0, but the version in repo is 1.1.9. This means that deluged doesn't install. Which means nothing can run.

See my reply to your other post here:
http://forum.deluge-torrent.org/viewtop ... 05#p106305

Aha. Thanks, I'm installing that now. I'm sure it'll work fine afterwords.

Hi all,

is there any chance that there will be a version of deluged 1.2.0 for Ubuntu Hardy?

Currently I'm running Hardy on my dedicated server and Jaunty on my laptop. I accidently upgraded deluge on my laptop and now I am unable to connect to deluged on my server via gtkui. And there doesn't seem to be an 1.2.0 of deluged in the launchpad repo for Hardy. Neither deluge-core nor deluged.

I am stuck at the moment because I cannot even revert my laptop version of deluge to 1.1.9.

Help is very much appreciated.

Regards