When 2.34.6-1~deb11 came along on Aug 16, I had great hopes it might
accidentally fix this, too -- but alas, it didn't.

Reply via email to