Core 190 downgrade Transmission to 4.0.5

Add-Ons
1

Is there a way to downgrade Transmission from 4.0.6 back to 4.0.5?
Transmission 4.0.6 is still banned by a lot of sites.

I know… I should have looked at the list of upgrades that would be applied along with core 190 :slight_smile:

Thanks
Pete

1 Like
2

Not easily. There was a forum user in the past that asked about downgrading and apparently he found a way, although that needed a lot of manual manipulation of files to deal with cached versions etc, etc.

It is somewhere in the forum but I haven’t been able to find it. If you find it you will need to review the changes to make your own conclusion about the risks.

I have searched and found this issue in the transmission github.

A commit has been merged back at the start of September 2024 that fixes this issue and there was a request for doing a 4.0.7 release. The Transmission devs said they preferred to keep working on the new version 4.1.0, although they would look at the possibility. It is now 4 months later and nothing has occurred so it looks like it will not happen.

Unfortunately no comment about this issue was added to the 4.0.6 release notes otherwise I would probably not have done the update at the end of September.

No mention was made of this issue also during the Testing phase of CU190.

It looks like there are two options.

  1. Move transmission back to version 4.0.5 but then users would have to manually deal with clearing caches otherwise the older version might not be able to be installed. When added to version CU191 then the update.sh script would deal with clearing the caches etc and make sure that any existing users are moved to the older version.
  2. Add the patch that fixes the issue but that can only be done with CU191

I will raise this on the Development mailing list to see what the best option is, or if there is another approach that I haven’t thought of.

2 Likes
3

Perhaps a 3rd option is to revert back to CU189 and wait til 191 to upgrade?

4

No that doesn’t work. The addon version is not tied to a Core Update. The addon version update is carried out at a certain Core Update but once the addon is updated then only that version is available to all Core Update versions.

EDIT:
Just to be sure I checked it out on my vm testbed.

If the major version changes then the update version available is the one available at the last CU in that major version.

So if you install 2.27 Core Update 182, the last CU in major version 2.27, then you will have transmission-4.0.4 available but your system would be 8 Core Updates out of date. Once you move to installing 2.29 Core Update 183 then you will automatically have transmission-4.0.6 as the version available.

So installing any CU from 183 to 190 will give you transmission-4.0.6

EDIT2:
Additionally if you are downloading transmission-4.0.6 in Core Update 187 and run the command
transmission-show --version
then you will get the message

version `CXXABI_1.3.15’ not found

due to the version of gcc in CU187 being different to the one in CU190.

2 Likes
5

I always like Deluge for torrents.
https://deluge-torrent.org/

6

The last commit for deluge was July 2022.

The last commit for transmission was today.

1 Like
7

I did find find the post about downgrading via pakfire Pakfire: downgrading package

But I didn’t want to try that just yet. I will follow transmission 4.1.0 progress, maybe they are close to a release?!?!?!?!?

Thank you for all the replies.
Pete

8

I have had a reply back on the dev mailing list and reverting transmission to version 4.0.5 is much easier than I thought.

I will be supplying a patch for the reversion later today and when it is merged it will apply to Core Update 190.

I will inform on this thread when it has been merged in so you can do the update to the older version.

3 Likes
9

The reversion of transmission from 4.0.6 to 4.0.5 has now been merged and fed out into the systems.

I had a CU 190 vm system with transmission 4.0.6 installed and when I just checked some minutes ago I found that in the top right hand box of the Pakfire page it showed the “update” of transmission from 4.0.6 to 4.0.5.

Press the Update button and the system will replace version 4.0.6 with 4.0.5 on your IPFire machine.

4 Likes
10

Thank you so much for fixing this.

Pete

11

Status information, in the transmission github issues the problem with 4.0.6 is being considered fixed and the issue closed by the release of 4.1.0-beta.1

So it looks like there will not be a 4.0.7 release and we will need to wait for a full release of 4.1.0

Meantime we will stay on 4.0.5

1 Like