Bug#1030857: testing

[Barak A. Pearlmutter]

Okay, I installed the package generated by 16c2e55a0 in my repo, which
is a 4.0.1-1 candidate. It seems to work okay EXCEPT ...

(a) is kicks out messages like this

Feb 26 21:49:35 sweat transmission-daemon[1174]: [2023-02-26
21:49:35.396] ERR torrent-metainfo.cc:630 no bencoded data to parse
(84) (./libtransmission/torrent-metainfo.cc:630)
Feb 26 21:49:35 sweat transmission-daemon[1174]: [2023-02-26
21:49:35.396] ERR torrent-metainfo.cc:630 no bencoded data to parse
(84) (./libtransmission/torrent-metainfo.cc:630)
Feb 26 21:49:35 sweat transmission-daemon[1174]: [2023-02-26
21:49:35.396] ERR torrent-metainfo.cc:630 no bencoded data to parse
(84) (./libtransmission/torrent-metainfo.cc:630)
Feb 26 21:49:35 sweat transmission-daemon[1174]: [2023-02-26
21:49:35.396] ERR torrent-metainfo.cc:630 no bencoded data to parse
(84) (./libtransmission/torrent-metainfo.cc:630)
Feb 26 21:49:35 sweat transmission-daemon[1174]: [2023-02-26
21:49:35.396] ERR torrent-metainfo.cc:630 no bencoded data to parse
(84) (./libtransmission/torrent-metainfo.cc:630)
Feb 26 21:49:35 sweat transmission-daemon[1174]: [2023-02-26
21:49:35.396] ERR torrent-metainfo.cc:630 no bencoded data to parse
(84) (./libtransmission/torrent-metainfo.cc:630)
Feb 26 21:49:35 sweat transmission-daemon[1174]: [2023-02-26
21:49:35.396] ERR torrent-metainfo.cc:630 no bencoded data to parse
(84) (./libtransmission/torrent-metainfo.cc:630)
Feb 26 21:49:35 sweat transmission-daemon[1174]: [2023-02-26
21:49:35.396] ERR torrent-metainfo.cc:630 no bencoded data to parse
(84) (./libtransmission/torrent-metainfo.cc:630)

And, it is refusing to verify a whole bunch of stuff that to my
knowledge was already downloaded just fine under 3.x. It just lists
them as 0%. Hitting "verify" on them does nothing, nor does resume or
re-announce. Some of them list as downloading; of those, sometimes one
wakes up and verifies and jumps to seeding.

No idea what's going on.

Not sure this is a sufficient show-stopper to preclude uploading this
version, but thought I'd mention it.

Looking at the post-release upstream commits, I suspect some may
address this. I could try cherry-picking some of those commits, or
maybe just merging the development tip, and seeing if that fixes the
problem. Or, maybe we should wait for 4.0.2 which might address this
properly? Is anyone in touch with upstream? It might help to get their
take, find out if they're going to do a point release fixing this
stuff sometime soon.

Bug#1030857: Testing

[Sandro Tosi]

> Unless morph vetoes it, I'd merge your 3 salsa MRs [0][1][2] and if no 
> obvious problems pop up during testing I'd just upload it. WDYT?

no issues here

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

Bug#1030857: Testing

[Leo Antunes]

Hi,

On Fri, 24 Feb 2023 21:28:18 + "Barak A. Pearlmutter" wrote:
> The upgraded daemon invalidates all downloaded data and wants to
> verify them, which is a local operation, but is still taking forever.
> I think that's supposed to be a feature not a bug.

Yeah, that makes sense.

> If someone were to test the clients that would be great!

Unless morph vetoes it, I'd merge your 3 salsa MRs [0][1][2] and if no obvious 
problems pop up during testing I'd just upload it. WDYT?


Cheers
Leo Antunes


[0] https://salsa.debian.org/debian/transmission/-/merge_requests/11
[1] https://salsa.debian.org/debian/transmission/-/merge_requests/12
[2] https://salsa.debian.org/debian/transmission/-/merge_requests/13

Bug#1030857: Testing

[Barak A. Pearlmutter]

Testing the 4.0.1 daemon.

Upgrade seems okay, although there's some straggler ghost file
/etc/init/itransmission-daemon.conf

The upgraded daemon invalidates all downloaded data and wants to
verify them, which is a local operation, but is still taking forever.
I think that's supposed to be a feature not a bug.

If someone were to test the clients that would be great!