Description of problem: Clients, such as Deluge, can set bandwidth limits on download / upload. These limits are no longer honored with version 1.1.6. Version-Release number of selected component (if applicable): rb_libtorrent-1.1.6-1 rb_libtorrent-python2-1.1.6-1
This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle. Changing version to '28'.
Please report the issue upstream https://github.com/arvidn/libtorrent/issues
It has been reported. https://github.com/arvidn/libtorrent/issues/2857
I can confirm that the suggested workaround does allow rate limiting to work again. --- - DEPRECATED_SET(rate_limit_utp, false, &session_impl::update_rate_limit_utp), + DEPRECATED_SET(rate_limit_utp, true, &session_impl::update_rate_limit_utp), I can patch rb_libtorrent if you wish.
rb_libtorrent-1.1.7-3.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-2ce08fb2be
rb_libtorrent-1.1.7-3.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-9de7e7bba3
rb_libtorrent-1.1.7-3.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-2ce08fb2be
rb_libtorrent-1.1.7-3.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-9de7e7bba3
rb_libtorrent-1.1.7-3.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.
rb_libtorrent-1.1.7-3.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.