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

Bug#444355: lintian: Bogus diagnostics for hard-linked files



Package: lintian
Version: 1.23.34
Severity: normal

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

The ion3-doc package contains two files with two names (hard-links)
each:
    /usr/share/doc/ion3-doc/ionconf/{ionconf,index}.html
    /usr/share/doc/ion3-doc/ionconf/{ionnotes,index}.html

In a tarball, the second and subsequent names for a file are
represented by reference to the first, rather like symbolic links.
lintian doesn't process these references properly, and so produces the
diagnostics:

E: doc-base-file-references-missing-file
W: zero-byte-file-in-doc-directory

There may well be other checks that have the same problem.

- -- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable'), (100, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.22-2-686
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)

Versions of packages lintian depends on:
ii  binutils               2.18-1            The GNU assembler, linker and bina
ii  diffstat               1.43-2            produces graph of changes introduc
ii  dpkg-dev               1.13.25           package building tools for Debian
ii  file                   4.17-5etch2       Determines file type using "magic"
ii  gettext                0.16.1-1          GNU Internationalization utilities
ii  intltool-debian        0.35.0+20060710.1 Help i18n of RFC822 compliant conf
ii  libparse-debianchangel 1.0-1             parse Debian changelogs and output
ii  man-db                 2.4.3-6           The on-line manual pager
ii  perl [libdigest-md5-pe 5.8.8-7           Larry Wall's Practical Extraction 

lintian recommends no packages.

- -- no debconf information

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFG/Dyr79ZNCRIGYgcRAp+BAJ9GIWknwO1hOF2gxKzyLmCrg6RrhwCg1t7K
tvis3RX41A3erIy1UpJ/Ick=
=nRUO
-----END PGP SIGNATURE-----




Reply to: