Hi everyone.
Frohes neues, Beste wensen, Happy new year.
Someone on the forum has flagged up that version 4.0.6 of transmission is banned by a lot of torrent sites due to a bug in it.
It checks if you are using ipv4 and or ipv6. If you are not using ipv6 then the code goes through the whole check again and this was apparently causing significant load on torrent sites.
This issue was found and fixed with a patch on 2nd Sept 2024 but version 4.0.7 has not been released. It looks like they don't intend to do that but to focus on the 4.1.0 release candidate work.
Unfortunately no message was put on the 4.0.6 release notes that it should not be used if ipv6 was not being used. So I found version 4.0.6 and provided an update patch for it on 24th Sept 2024.
The forum user would like to revert to version 4.0.5
What would be the best option - revert transmission to 4.0.5 or add the transmission patch that fixes the issue.
The transmission patch fix could only apply to CU191.
Could a reversion of transmission to 4.0.5 be made to work with CU190. How would that work with the cached versions of the addons in the install. Would users have to clear their caches or are there alternative ways to install the older version once it is in the addons download server.
What feedback do you all have on the best approach from the two above or is there another approach that I haven't thought of.
Regards,
Adolf.
Hello,
Happy New Year!
We can easily revert back to 4.0.5 and even release this fast for Core Update 190 users.
We simply would count up the release version as usual. That is the only thing that Pakfire looks at, so there downgrade of the version number does not matter.
Are you sending a patch?
Best, -Michael
On 1 Jan 2025, at 13:32, Adolf Belka adolf.belka@ipfire.org wrote:
Hi everyone.
Frohes neues, Beste wensen, Happy new year.
Someone on the forum has flagged up that version 4.0.6 of transmission is banned by a lot of torrent sites due to a bug in it.
It checks if you are using ipv4 and or ipv6. If you are not using ipv6 then the code goes through the whole check again and this was apparently causing significant load on torrent sites.
This issue was found and fixed with a patch on 2nd Sept 2024 but version 4.0.7 has not been released. It looks like they don't intend to do that but to focus on the 4.1.0 release candidate work.
Unfortunately no message was put on the 4.0.6 release notes that it should not be used if ipv6 was not being used. So I found version 4.0.6 and provided an update patch for it on 24th Sept 2024.
The forum user would like to revert to version 4.0.5
What would be the best option - revert transmission to 4.0.5 or add the transmission patch that fixes the issue.
The transmission patch fix could only apply to CU191.
Could a reversion of transmission to 4.0.5 be made to work with CU190. How would that work with the cached versions of the addons in the install. Would users have to clear their caches or are there alternative ways to install the older version once it is in the addons download server.
What feedback do you all have on the best approach from the two above or is there another approach that I haven't thought of.
Regards,
Adolf.
-- Sent from my laptop
Hi Michael,
On 02/01/2025 11:46, Michael Tremer wrote:
Hello,
Happy New Year!
We can easily revert back to 4.0.5 and even release this fast for Core Update 190 users.
We simply would count up the release version as usual. That is the only thing that Pakfire looks at, so there downgrade of the version number does not matter.
Are you sending a patch?
I wasn't sure how to do it but based on your reply, I just need to do a normal update patch but in this case the PAK_VER gets incremented and the package version number will go to 4.0.5, so that looks easy enough for me to do.
I will ship out a patch as soon as possible.
Regards,
Adolf.
Best, -Michael
On 1 Jan 2025, at 13:32, Adolf Belka adolf.belka@ipfire.org wrote:
Hi everyone.
Frohes neues, Beste wensen, Happy new year.
Someone on the forum has flagged up that version 4.0.6 of transmission is banned by a lot of torrent sites due to a bug in it.
It checks if you are using ipv4 and or ipv6. If you are not using ipv6 then the code goes through the whole check again and this was apparently causing significant load on torrent sites.
This issue was found and fixed with a patch on 2nd Sept 2024 but version 4.0.7 has not been released. It looks like they don't intend to do that but to focus on the 4.1.0 release candidate work.
Unfortunately no message was put on the 4.0.6 release notes that it should not be used if ipv6 was not being used. So I found version 4.0.6 and provided an update patch for it on 24th Sept 2024.
The forum user would like to revert to version 4.0.5
What would be the best option - revert transmission to 4.0.5 or add the transmission patch that fixes the issue.
The transmission patch fix could only apply to CU191.
Could a reversion of transmission to 4.0.5 be made to work with CU190. How would that work with the cached versions of the addons in the install. Would users have to clear their caches or are there alternative ways to install the older version once it is in the addons download server.
What feedback do you all have on the best approach from the two above or is there another approach that I haven't thought of.
Regards,
Adolf.
-- Sent from my laptop
Hello,
On 2 Jan 2025, at 11:13, Adolf Belka adolf.belka@ipfire.org wrote:
Hi Michael,
On 02/01/2025 11:46, Michael Tremer wrote:
Hello, Happy New Year! We can easily revert back to 4.0.5 and even release this fast for Core Update 190 users. We simply would count up the release version as usual. That is the only thing that Pakfire looks at, so there downgrade of the version number does not matter. Are you sending a patch?
I wasn't sure how to do it but based on your reply, I just need to do a normal update patch but in this case the PAK_VER gets incremented and the package version number will go to 4.0.5, so that looks easy enough for me to do.
Yes, you can simply revert the commit and the manually increment the PAK_VER number. Git commit —amend will be of great help :)
I will ship out a patch as soon as possible.
Thank you!
-Michael
Regards,
Adolf.
Best, -Michael
On 1 Jan 2025, at 13:32, Adolf Belka adolf.belka@ipfire.org wrote:
Hi everyone.
Frohes neues, Beste wensen, Happy new year.
Someone on the forum has flagged up that version 4.0.6 of transmission is banned by a lot of torrent sites due to a bug in it.
It checks if you are using ipv4 and or ipv6. If you are not using ipv6 then the code goes through the whole check again and this was apparently causing significant load on torrent sites.
This issue was found and fixed with a patch on 2nd Sept 2024 but version 4.0.7 has not been released. It looks like they don't intend to do that but to focus on the 4.1.0 release candidate work.
Unfortunately no message was put on the 4.0.6 release notes that it should not be used if ipv6 was not being used. So I found version 4.0.6 and provided an update patch for it on 24th Sept 2024.
The forum user would like to revert to version 4.0.5
What would be the best option - revert transmission to 4.0.5 or add the transmission patch that fixes the issue.
The transmission patch fix could only apply to CU191.
Could a reversion of transmission to 4.0.5 be made to work with CU190. How would that work with the cached versions of the addons in the install. Would users have to clear their caches or are there alternative ways to install the older version once it is in the addons download server.
What feedback do you all have on the best approach from the two above or is there another approach that I haven't thought of.
Regards,
Adolf.
-- Sent from my laptop
-- Sent from my laptop
-
Adolf Belka -
Michael Tremer