This may well create fresh new issues, but that's a matter for other days.
And that's enough time on this matter.
I've revised the logic slightly, and the fix for this specific user's issue is now in 2.2.37. When
or if unit193 packages that, and when or if that package gets into the appropriate debian pool, will
determine when the debian issue itself is resolved.
