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.
