Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 08 Mar 2018 07:14:43 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-ports-bugs@FreeBSD.org
Subject:   [Bug 226443] net-p2p/deluge
Message-ID:  <bug-226443-13@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D226443

            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@FreeBSD.org
          Reporter: rainbow@sanitylinux.org
          Assignee: rm@FreeBSD.org
             Flags: maintainer-feedback?(rm@FreeBSD.org)
 Attachment #191300 text/plain
         mime type:

Created attachment 191300
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D191300&action=
=3Dedit
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 confi=
g to
be written to core.conf on the remote system, and will crash the remote dae=
mon.

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.

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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-226443-13>