Bug#1012875: transmission-gtk: Issue when parsing hybrid BitTorrent v1 / v2 torrents

[Vasil Kolev]

Package: transmission-gtk
Version: 3.00-1
Severity: important
Tags: patch upstream

Dear Maintainer,

transmission has a known fixed when parsing hybrid v1/v2 torrent files that
is reported as

Skipping unknown torrent:...

This has been reported upstream at https://github.com/transmission/transmission/issues/1813
and is fixed in https://github.com/transmission/transmission/pull/1964, but there hasn't
been a new release of transmission after 3.0 to include this patch.

Can it be considered for this patch to be included?

-- System Information:
Debian Release: 11.3
APT prefers stable-security
APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-13-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_USER, TAINT_WARN
Locale: LANG=bg_BG.UTF8, LC_CTYPE=bg_BG.UTF8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages transmission-gtk depends on:
ii libayatana-appindicator3-1 0.5.5-2
ii libc6 2.31-13+deb11u3
ii libcurl4 7.74.0-1.3+deb11u1
ii libevent-2.1-7 2.1.12-stable-1
ii libgdk-pixbuf2.0-0 2.40.2-2
ii libglib2.0-0 2.66.8-1
ii libgtk-3-0 3.24.24-4+deb11u2
ii libminiupnpc17 2.2.1-1
ii libnatpmp1 20150609-7.1
ii libpango-1.0-0 1.46.2-3
ii libssl1.1 1.1.1n-0+deb11u1
ii transmission-common 3.00-1
ii zlib1g 1:1.2.11.dfsg-2+deb11u1

Versions of packages transmission-gtk recommends:
ii xdg-utils 1.1.3-4.1

transmission-gtk suggests no packages.

-- debconf-show failed

[Sandro Tosi]

> transmission has a known fixed when parsing hybrid v1/v2 torrent files that
> is reported as
>
> Skipping unknown torrent:...
>
> This has been reported upstream at https://github.com/transmission/transmission/issues/1813
> and is fixed in https://github.com/transmission/transmission/pull/1964, but there hasn't
> been a new release of transmission after 3.0 to include this patch.
>
> Can it be considered for this patch to be included?

it looks like work for releasing v4.0 has begun, so we're gonna wait
for that to include this fix.

--
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi