rTorrent 0.9.3 seems to have been out a while now, this seems like a bug fix release so could it be pushed for cauldron? Release notes below RTorrent 0.9.3 and libTorrent 0.13.3 released - Added extensive unit test for tracker code. - When setting timeouts above/below the max bounds use the boundary value instead of discarding it. - Handle short min_interval properly in promiscious mode. - Properly handle min_interval after successful tracker requests. - Fixed a bug where manual tracker update for a preferred tracker that fails would end up rerequesting instantly. - Send stopped event before disabling tracker controller. - Wait for disowned http requests to finish to ensure stopped event gets sent to tracker on client shutdown. - Fixed compilation issues with latest clang version. - Added backtrace to internal_error. - Added logging of segfault/bus signal and backtrace to LOG_CRITICAL. - Added 'catch' command to allow safely calling commands that might fail with input_error. Note that double-brackets are required as the method needs to be called by the 'catch' command, not the parser. catch = ((foo.bar,"bad input")) - For POSIX threads config script try none first to avoid adding flags when not needed. - Allow functions and lists of functions to be passed to view.event_{added,removed}. http://libtorrent.rakshasa.no/downloads/libtorrent-0.13.3.tar.gz http://libtorrent.rakshasa.no/downloads/rtorrent-0.9.3.tar.gz This release fixes some serious issues with tracker requesting, and adds a suite of unit tests to ensure future modifications pass some basic sanity tests. Jari Sundell
Source RPM: (none) => rtorrent
CC: (none) => jani.valimaaAssignee: bugsquad => remcoSource RPM: rtorrent => rtorrent libtorrent
I have a local build of new libtorrent/rtorrent so I can commit changes to SVN and make a freeze push request as it fixes "some serious issues".
Actually 0.13.3/0.9.3 is unstable release. Should we stay on stable one?
I think we should stay on stable as long as upstream makes a clear distinction between stable and unstable releases. Of course, this also depends on what "serious issues" we are looking at here.
I'm OK to stay on stable one.
Ok, let's close the report then.
Status: NEW => RESOLVEDResolution: (none) => WONTFIX