cool.
force pushed yours to my repo, and rebased some yak shaving onto it
hi,
--- Original Message ---
On Friday, March 17th, 2023 at 21:51, Barak A. Pearlmutter
wrote:
> I would say that marking lots of 100% downloaded torrent as 0%, and
> refusing to re-verify them, would count as a severity: important bug,
> and hence allow 4.0.2 to get into the release.
I would say that marking lots of 100% downloaded torrent as 0%, and
refusing to re-verify them, would count as a severity: important bug,
and hence allow 4.0.2 to get into the release. The release team wants
a high-quality release just as much as we do, and transmission is a
leaf package and
I'm on it.
But AFAIUI, the only chance of getting it through the freeze would be some
autopkgtests[0] :/
Regards,
[0] https://release.debian.org/testing/freeze_policy.html#hard
--- Original Message ---
On Thursday, March 16th, 2023 at 15:28, Sandro Tosi wrote:
>
> upstream released
> Really upstream should release 4.0.2 with these fixes right away,
> since 4.0.1 is, technically speaking, what we in the biz call
> "broken". But I digress.
upstream released 4.0.2:
https://github.com/transmission/transmission/releases/tag/4.0.2
--
Sandro "morph" Tosi
My website:
Leo,
Thanks for uploading 4.0.1-1. Good idea to disable libtransmission-dev for now.
I did a bit of testing, and it seems to get a bunch of those old "no
bencoded data to parse" errors, and a whole bunch of fully downloaded
torrents showed up as 0%. So I cherry-picked to the tip of
upstream/main
6 matches
Mail list logo
