Santiago Vila
2025-03-02 10:00:02 UTC
Reply
Permalinkthanks
I cannot reproduce the bug in a freshly created unstable chroot, so I'm lowering the
severity for the time being. Please let me know how to reproduce the issue.
The issue was reproducible at the date I reported it, so I used debbisectseverity for the time being. Please let me know how to reproduce the issue.
to see why it does not fail anymore:
bisection finished successfully
last bad timestamp: 20250228T151043Z
first good timestamp: 20250228T210243Z
the following packages differ between the last good and first bad timestamp:
apt 2.9.30 -> 2.9.31
libapt-pkg7.0:amd64 2.9.30 -> 2.9.31
python3-click 8.2.0-1 -> 8.2.0+0.really.8.1.8-1
AFAIK, click 8.2.0 was known to break too many packages so it was
reverted for trixie.
I'm keeping the bug open (with the lower severity) because this issue
will be back eventually.
Thanks.