a) private/runtests already contains logic to set NO_PKG_MANGLE; unfortunately it didn't work in ~rc3 due to a typo. The correct fix is to take 0c511db6cb526cbc3cf8877e2a25558fa5e4f40b from upstream, which corrects that issue by correctly exporting NO_PKG_MANGLE (rather than NO_PKG_MAGNGLE)
b) debian/rules contains two different ways in which private/runtests may be called, and the above only touches one of them
--- lintian- 2.5.0~rc3/ debian/ rules 2011-04-17 17:48:14.000000000 +0200 2.5.0~rc3ubuntu 1/debian/ rules 2011-04-21 19:20:39.000000000 +0200
+++ lintian-
@@ -26,13 +26,11 @@
[...]
- private/runtests $(PAR_ARGS) $(onlyrun)
+ NO_PKG_MANGLE=true private/runtests $(PAR_ARGS) $(onlyrun)
This is wrong, for a couple of reasons:
a) private/runtests already contains logic to set NO_PKG_MANGLE; unfortunately it didn't work in ~rc3 due to a typo. The correct fix is to take 0c511db6cb526cb c3cf8877e2a2555 8fa5e4f40b from upstream, which corrects that issue by correctly exporting NO_PKG_MANGLE (rather than NO_PKG_MAGNGLE)
b) debian/rules contains two different ways in which private/runtests may be called, and the above only touches one of them
Regards,
Adam