[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#479629: lintian: error when run against python-levenshtein



Package: lintian
Version: 1.23.47
Severity: normal

Hello,
this is the error I recieve running lintian against python-levenshtein:

$ lintian ../python-levenshtein_0.10.1-1_amd64.changes 
Can't use string ("1") as an ARRAY ref while "strict refs" in use at /usr/share/lintian/checks/menus line 418, <IN> line 5.
internal error: cannot run menus check on package python-levenshtein
N: Skipping check of binary package python-levenshtein

indeed there is no menu file in the packge:

~/tmp/deb/python/python-levenshtein-0.10.1$ ls debian/
changelog  compat  control  copyright  patches
python-levenshtein.doc-base  rules  watch

Regards,
Sandro

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.22-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages lintian depends on:
ii  binutils            2.18.1~cvs20080103-4 The GNU assembler, linker and bina
ii  diffstat            1.45-2               produces graph of changes introduc
ii  dpkg-dev            1.14.16.6            package building tools for Debian
ii  file                4.23-2               Determines file type using "magic"
ii  gettext             0.17-2               GNU Internationalization utilities
ii  intltool-debian     0.35.0+20060710.1    Help i18n of RFC822 compliant conf
ii  libdigest-sha-perl  5.46-1+b1            Perl extension for SHA-1/224/256/3
ii  libparse-debianchan 1.1.1-2              parse Debian changelogs and output
ii  liburi-perl         1.35.dfsg.1-1        Manipulates and accesses URI strin
ii  man-db              2.5.1-3              on-line manual pager
ii  perl [libdigest-sha 5.10.0-9             Larry Wall's Practical Extraction 

lintian recommends no packages.

-- no debconf information



Reply to: