On 6/21/24 02:56, Adam D. Barratt wrote:
I assume you mean *un*stable there, as clearly the update isn't already in stable.
Sorry for the typo, yes unstable.
The metadata for #1073853 indicates that the issue is not fixed in unstable or testing. I assume that's simply an oversight, in which case please add appropriate fixed versions and go ahead.
This should be fixed now. Thanks.
