Hi Gianfranco, Thanks for sponsoring the binNEW upload of twinkle.
I had a closer look at the lintian warning issued by debomatic: X: twinkle source: maybe-not-arch-all-binnmuable twinkle -> twinkle-common N: N: Tag to attempt to measure the number of packages that might have an N: issue with arch:all binNMUs. N: N: At this time, please do <not> attempt to "fix" the problem. It is not N: clear what the solution is (if any at all). Nor is it clear that this is N: something that will be supported. N: N: Severity: wishlist, Certainty: possible N: N: Check: version-substvars, Type: source N: N: This tag is marked experimental, which means that the code that N: generates it is not as well-tested as the rest of Lintian and might N: still give surprising results. Feel free to ignore experimental tags N: that do not seem to make sense, though of course bug reports are always N: welcome. N: This experimental check not only flags twinkle but all packages that have a "Depends: foo (= ${source:Version})" on an arch:all package. As stated, there is nothing that can be done to solve that at the moment, since neither ${binary:Version} nor ${source:Version} would be appropriate for the case of an arch:all binNMU. Peter