Update Transmission app to 2.92?

Help and Support
1

I have my transmission installed via app store as I tried first using packaged version and found that it was working better than the original one (waiting until devices and network are mounted, etc).
The problem is that there is no way to update to 2.92 from the app store, and maybe those memory leaks and security bugs fixed will help with the freezes I get from time to time.
So, there is any plan to update app package to 2.90+??

2

Check the official changelog for Transmission, we only update it when there are real benefits in doing so.

You can build a newer version from source, if it improves things I will update the official version in the Store.

Sam

3

Current app in app store (or at least the one that I have installed) is 2.84 I don’t see an option to upgrade.
Current version of transmission is 2.92

Notable changes in 2.90:

  • Fix some more thread safety bugs in the tr_list datatype
  • Fix infinite loop when removing torrent data
  • Add support for CyaSSL/WolfSSL and PolarSSL cryptographic backends; bump OpenSSL minimum to v0.9.7
  • Fix several memory leaks and buffer overflows
  • Support miniupnpc API v14
  • Fix “prefetch-enabled” value type in settings.json (boolean instead of integer)
  • Fix some issues discovered by static analysis (cppcheck, coverity)
  • Fix invalid JSON encoding for non-printable characters
  • Fix multi-threaded locale use when encoding/decoding JSON data
  • Fix encrypted communication with libevent 2.1+
  • Prevent completed pieces modification by webseeds
  • Require absolute paths in RPC requests
  • Fix crash on session shutdown (evdns_getaddrinfo_cancel)
  • Retry if RPC server fails to bind to specified address
  • Improve error checking on metadata retrieval

Notable changes in 2.91:

  • Fix miniupnpc script to handle spaces and other special chars in paths

Probably updating to 2.90 would be enough, I asked for 2.92 as it is already available, but don’t expect to have a new version every transmission release unless it is something as big as 2.90 or something was broken.

4

I’m not a Transmission developer, I think only they can quantify the significance of an upgrade, and whether or not something was severely broken.

I also do not use Transmission. So I would advise just bumping the version in transmission-app-osmc, building, and if there are no regressions, I will accept a pull request. I cannot blindly bump versions, so I need community testing to verify new versions

Cheers

Sam