Downgrade or Pin transmission to 4.0.5

[sethrosenblum]

Is this a new Bug?

• I checked that the bug hasn't been reported before

Package Name

transmission

Package Version

4.0.6

Device Model

DS918+

Device Architecture

x86_64

Firmware Version

DSM 7.1.1-42962 Update 7

What happened?

Issue

There's a problem with Transmission 4.0.6 that has caused that version to be banned by lots of different trackers, making it kind of useless for Synology users: transmission/transmission#7078

The issue has been fixed in version 4.1.0, but that version is still in beta, and there doesn't seem to be any urgency to put out a 4.0.7 bugfix that this community could get out quickly: transmission/transmission#7086

It would be nice if SynoCommunity could pin Transmission to version 4.0.5-26 for now to fix the headache this causes for users, but really I opened this ticket so I could publish my workaround for downgrading, as there aren't clear steps in one place out there:

Workaround

1. Enable SSH on your Synology NAS: Control Panel > Terminal & SNMP > Enable SSH service
2. SSH into your NAS box
3. back up your INFO file (just in case) cp /var/packages/transmission/INFO transmission-INFO.bak
4. sudo vi /var/packages/transmission/INFO (this is from https://github.com/SynoCommunity/spksrc/wiki/Frequently-Asked-Questions#downgrade-a-package-without-uninstalling-advanced)
5. Edit version="4.0.6-27" to read version="4.0.4"
6. Look up your NAS box's SynoCommunity Arch here: https://github.com/SynoCommunity/spksrc/wiki/Synology-and-SynoCommunity-Package-Architectures
7. Download transmission 4.0.5-26 for your architecture from here: https://synocommunity.com/package/transmission
8. Go to Package Center > Manual Install > Browse and choose the .spk file you just downloaded
9. Finish installation, transmission should restart on the old version.
10. Don't upgrade the package again!

Reproduction steps

...

Install Log

N/A

Service Log

Other Logs

[hgy59]

These steps are documented in our wiki:
https://github.com/SynoCommunity/spksrc/wiki/Frequently-Asked-Questions
at the bottom under Downgrade a package without uninstalling (Advanced)

And you can edit the INFO file after downgrade again to 4.0.6-27 and you will have 4.0.5 without the status update available in package center.

[hgy59]

@sethrosenblum but Version 4.0.5 has another issue open #5999
I offered there test packages to drill down the cause of the issue, but never got feedback...

The first issue you mentioned above provides a patch (file announcer-http.cc)
Shall we add this patch and other related changes to transmission package - and is this a solution?

[sethrosenblum]

I won't speak to the wisdom of having a SynoCommunity-specific version of Transmission floating out there.

But, I will say that the tracker I was having trouble with uses client whitelists and blacklists to ban misbehaving clients. I presume many others do this as well. So, even if you fix the issue in transmission, you'd have to use a new version number to make this work for most users. And I can imagine a lot of unintended consequences there.

[hgy59]

I won't speak to the wisdom of having a SynoCommunity-specific version of Transmission floating out there.

@sethrosenblum you must see the full story:
The downgrade to 4.0.5 is not a soultion for all users. There is an issue in 4.0.5 and other users need to downgrade to 4.0.4.
The target of my proposal in #5999 was to find a version between 4.0.4 and 4.0.5 (only official commits) that works for those users.

If we must pin transmission to a specific version now, we would pin to v4.0.4.

I guess we will not pin the package to any former version and you have to manually downgrade to what ever version you want and wait for the next release of transmission (either 4.0.7 or 4.1.0).

[mreid-tt]

@sethrosenblum, a new beta version of Transmission v4.1.0 has been released. I’ve created a test build at https://github.com/SynoCommunity/spksrc/actions/runs/12930511900. If you’re interested, you can install the build and provide feedback.