* Jakub Wilk <jwilk@debian.org>, 2016-03-02, 00:28:
But to be honest I have no idea why this tag is produced for packages that have no Multi-Arch field at all, which implies that that are `Multi-Arch: no' already...It was a bug, but I believe I fixed it in 2.5.41. If it's not fixed, please tell us how to reproduce it.
Oh, never mind. For some reason I thought you were talking about a different tag.
Indeed, the pedantic old-style-config-script is emitted even for Multi-Arch-less packages.
-- Jakub Wilk