Re: Trixie shipping an unstable beta version of Transmission
On Thu, Aug 14, 2025 at 11:47 AM Nicolas George <george@nsup.org> wrote:
>
> Anders Andersson (HE12025-08-13):
> > I'm surprised to see it in the stable release version. It's a pre-release
> > version, not feature-stable, and thus there are now some trackers I can no
> > longer use because they only allow actual releases.
>
> Normally, alpha = feature-stable but may contain bugs, beta =
> feature-stable and probably not many bugs left.
Normally, but the release notes literally says "We're not in feature
freeze yet": https://github.com/transmission/transmission/releases
> Can you elaborate on trackers? Do they check the exact version? The
> presence of “beta” in the version string?
These trackers keep a whitelist of allowed clients based on the exact version.
Since Debian is a popular system there are already discussions about
the problem on these trackers. The response from the admins are
typically "Just downgrade" but that's difficult here. There's no
Debian package to "revert" to.
You can't just build 4.0.6 either because the build script is broken.
There are patches to this, which should ideally go into a 4.0.7
release but that hasn't happened:
https://github.com/transmission/transmission/discussions/7109
> > - There was some important bug in the 4.0.6 stable version
>
> Do you remember what bug? Security? File corruptions? Specific to an
> architecture?
I don't remember and it is difficult to find. I think there were more
than one, but the important bug may have been fixed in a curl library
which is why 4.0.6 now works.
> > - Transmission development was abandoned so 4.1.0 never got out of beta
>
> Sad news. Anybody know the options to replace it eventually?
No, and the Transmission maintainers would probably call my claim of
"abadoned" hyperbolic, but when I read through the various tickets and
discussions last night there were numerous threads about "where are
the devs?" and pointers to internal contentions about the only devs
with write access just stopped doing anything, leaving hundreds of
tickets and push requests unanswered but they have also voiced
opinions about not wanting to give access to those who are active.
Ideally it can solve itself by either the core maintainers giving
access to new people, or with a fork.
https://github.com/transmission/transmission/issues/7058
https://github.com/transmission/transmission/issues/7568
https://github.com/transmission/transmission/issues/7623
Reply to: