Am Mon, 05 Feb 2024 08:36:28 +0000 schrieb Steve Langasek <vor...@debian.org>:
> we have identified > mpg123 as a source package shipping runtime libraries whose ABI > either is affected by the change in size of time_t, or could not be > analyzed via abi-compliance-checker (and therefore to be on the safe > side we assume is affected). I am not aware of mpg123 API being affected at all by time_t changes. There's internal use of time_t, but nothing that users should see. So nothing to see here … can you just mark it as unaffected manually? Otherwise, I'd be interested to know how I managed to slip in a sliver of time_t. Alrighty then, Thomas
