[Bug 226443] net-p2p/deluge

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Thu Mar 8 07:14:46 UTC 2018


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226443

            Bug ID: 226443
           Summary: net-p2p/deluge
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: Individual Port(s)
          Assignee: rm at FreeBSD.org
          Reporter: rainbow at sanitylinux.org
          Assignee: rm at FreeBSD.org
             Flags: maintainer-feedback?(rm at FreeBSD.org)
 Attachment #191300 text/plain
         mime type:

Created attachment 191300
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=191300&action=edit
deluge 1.3.15 preferences.py patch

Deluge 1.3.15 has a bug that was meant to be fixed but wasn't.
This bug causes Preferences on a Thin Client setup (local installation of
net-p2p/deluge talking to a remote instance of net-p2p/deluge-cli) to have all
preferences greyed out in the thin client. Attempting to make any changes to
non-greyed out preferences (like plugin options), will cause a broken config to
be written to core.conf on the remote system, and will crash the remote daemon.

The issue is detailed on their bug tracker here:
http://dev.deluge-torrent.org/ticket/3039

The official diff in the deluge source tree is here:
http://dev.deluge-torrent.org/changeset/38d7b7cdfde3c50d

Generated patch (via make makepatch) is attached.

The file that should end up modified, once the fix is installed, is
/usr/local/lib/python2.7/site-packages/deluge/ui/gtkui/preferences.py

Deluge does not have a timeline available and visible for releasing 1.3.16, and
while mention of 1.3.15.1 was brought up in the bug report, no such tarball was
released.

This bug is confirmed to exist in the currently available 1.3.15 release
tarball.

I applied the fix in question to my own system and it resolved the issue.

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-ports-bugs mailing list