It is obviously a signedness issue on 32 bit systems.

3.2.1-3 has the same issue on sid. So this has to be caused by a post-bookworm update of a different component.

Reply via email to