Latest upstream release: 0.16.8 Current version in Fedora Rawhide: 0.16.7 URL: http://code.google.com/p/libtorrent/downloads/list Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring
This update fixes some bugs regarding magnet links and metadata downloading. Can this update be pushed to Fedora 18 and higher?
I have pushed this for Rawhide. It has a soname bump and I have rebuilt all the dependent packages as well. I haven't pushed it for Fedora 18 however. If there are compelling reasons, I can consider it.
(In reply to comment #2) > I have pushed this for Rawhide. It has a soname bump and I have rebuilt all > the dependent packages as well. I haven't pushed it for Fedora 18 however. > If there are compelling reasons, I can consider it. My comment mentioned a compelling reason. Magnet links don't work in torrent clients, such as Deluge, with the Fedora 18 version of rb_libtorrent. After rebuilding the latest rb_libtorrent for F18, Deluge works again.
(In reply to comment #2) > I haven't pushed it for Fedora 18 however. > If there are compelling reasons, I can consider it. There are several pyhton bindings issues fixed since 16.5 . I suspect this report is related to broken bindings. https://bugzilla.redhat.com/show_bug.cgi?id=907081
flush-0.9.12-5.fc18,fatrat-1.2.0-0.11.beta2.fc18,qbittorrent-3.0.8-5.fc18,springlobby-0.147-4.fc18,rb_libtorrent-0.16.8-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/flush-0.9.12-5.fc18,fatrat-1.2.0-0.11.beta2.fc18,qbittorrent-3.0.8-5.fc18,springlobby-0.147-4.fc18,rb_libtorrent-0.16.8-1.fc18
flush-0.9.12-5.fc18, fatrat-1.2.0-0.11.beta2.fc18, qbittorrent-3.0.8-5.fc18, springlobby-0.147-4.fc18, rb_libtorrent-0.16.8-1.fc18, leechcraft-0.5.85-2.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.