reassign 1106442 src:python3.13 affects 1106442 src:python-returns found 1106442 3.13.3-4 close 1106442 3.13.4-1 thanks
El 18/6/25 a las 14:00, Colin Watson escribió:
I tried this a couple of times in both unstable and testing and couldn't reproduce this failure, and it doesn't intuitively seem like the sort of test that should be flaky (despite being async). Could you please check to see whether you can still reproduce this?
Thanks for trying. I did a reverse debbisect and this is what I found: bisection finished successfully last bad timestamp: 20250603T082936Z first good timestamp: 20250604T022813Z the following packages differ between the last bad and first good timestamp: groff-base 1.23.0-8 -> 1.23.0-9 libpython3.13-minimal:amd64 3.13.3-4 -> 3.13.4-1 libpython3.13-stdlib:amd64 3.13.3-4 -> 3.13.4-1 python3.13 3.13.3-4 -> 3.13.4-1 python3.13-minimal 3.13.3-4 -> 3.13.4-1 I'm fixing the metadata. Thanks a lot.
