Package: lintian Version: 1.23.42 Severity: minor Hi,
I accidentally created a zero-byte 'debian/prerm' script in my package. That of course was not intentional or useful, but the output of lintian contained quite some 'uninitialized value's and was unclear as to the source of this problem: Now running lintian... Use of uninitialized value in pattern match (m//) at /usr/share/lintian/checks/menus line 548. Use of uninitialized value in pattern match (m//) at /usr/share/lintian/checks/menus line 548. Use of uninitialized value in pattern match (m//) at /usr/share/lintian/checks/menus line 553. Use of uninitialized value in pattern match (m//) at /usr/share/lintian/checks/menus line 558. Tried to issue unknown tag unknown-interpreter Use of uninitialized value in pattern match (m//) at /usr/share/lintian/checks/infofiles line 174. Use of uninitialized value in pattern match (m//) at /usr/share/lintian/checks/infofiles line 174. Use of uninitialized value in pattern match (m//) at /usr/share/lintian/checks/infofiles line 179. Use of uninitialized value in pattern match (m//) at /usr/share/lintian/checks/infofiles line 184. Tried to issue unknown tag unknown-interpreter Making $interp in checks/menus initialized to 'unknown' when reading <IN> fails would eliminate the warnings and give the appropriate tag. Same goes for checks/infofiles. [alert! code duplication] Thijs
pgpMdOsdQJ3c8.pgp
Description: PGP signature
