Bug 480637

Summary:	deluge: Duplication of system libraries
Product:	[Fedora] Fedora	Reporter:	Alexey Kuznetsov <axet>
Component:	deluge	Assignee:	Peter Gordon <peter>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	10	CC:	peter
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-01-19 18:36:57 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Alexey Kuznetsov 2009-01-19 15:53:30 UTC

https://fedoraproject.org/wiki/Packaging/Guidelines#Duplication_of_system_libraries


[axet@axet-laptop deluge]$ rpm -qil deluge|grep libtor
/usr/lib/python2.5/site-packages/deluge/libtorrent.so

Comment 1 Peter Gordon 2009-01-19 18:36:57 UTC

I fixed this about two weeks ago in Rawhide; but keeping it built against an internal copy of libtorrent in Fedora 9/10 is a necessary evil at this point. Deluge *requires* the 0.14 series of libtorrent at minimum for its functionality. (In fact, I just tried it with a system copy of libtorrent .13 and it simply hangs on starting the daemon.)

However, the upgrade from rb_libtorrent 0.13 to 0.14 changes the API/ABI and breaks backward-compatibility, so it is only in Rawhide at this time. In fact, Deluge in Rawhide *is* using the system copy of rb_libtorrent, so this is no longer an issue there. See: https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00373.html

It is that older Fedora releases are using such old versions of libtorrent which causes Deluge to require its own internal (far newer) copy. And upgrading those Fedora releases with the newer libtorrent is a definite no-go at this point in time, due to these compatibility-breaking changes.

Apologies for any inconvenience this may cause! 

Thanks for the bug report; and please feel free to re-open this with more details if you have any further questions or comments, et al. :)