From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Problem with transmission-4.0.6 in CU190
Date: Thu, 02 Jan 2025 10:46:13 +0000 [thread overview]
Message-ID: <8F735E58-90C5-4124-93DD-F473223B9589@ipfire.org> (raw)
In-Reply-To: <d67ddb10-6aed-4c5b-9fce-0342ce205653@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1944 bytes --]
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(a)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
>
next prev parent reply other threads:[~2025-01-02 10:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-01 13:32 Adolf Belka
2025-01-02 10:46 ` Michael Tremer [this message]
2025-01-02 11:13 ` Adolf Belka
2025-01-02 13:57 ` Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8F735E58-90C5-4124-93DD-F473223B9589@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox