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

Bug#398898: marked as done (lintian: zero-byte-file-in-doc-directory bogus complain on files in examples)

Your message dated Mon, 26 Feb 2007 23:41:44 -0800
with message-id <87d53w2gjr.fsf@windlord.stanford.edu>
and subject line Bug#398898: zero-byte-file-in-doc-directory bogus complain on files in examples
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: lintian
Version: 1.23.25
Severity: normal

Rsyncrypto is a package that performs rsync friendly encryption. The
package comes bundled with a "tests" directory, that gets installed into
/usr/share/doc/rsyncrypto/examples/tests. This directory contains known
plain texts, cipher texts and keys so that regression testing and
comparisons can be run.

Some of the files in said directory are records of when the internal
decision function decided to perform an IV reset. For some of the
regression testing files (reg1 and reg2), this file is empty.

When running version 0.18-1 (the version that introduced the tests
direcotry under examples) through lintian, I get the complaint:
O: rsyncrypto: zero-byte-file-in-doc-directory
usr/share/doc/rsyncrypto/examples/tests/reg1.rot
O: rsyncrypto: zero-byte-file-in-doc-directory
usr/share/doc/rsyncrypto/examples/tests/reg2.rot

(as you can see, I did an override). I believe that the override is
unnecessary, and the files under /usr/share/doc/*/examples should not be
checked for non-emptyness.

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-2-686
Locale: LANG=en_US, LC_CTYPE=he_IL (charmap=ISO-8859-8)

Versions of packages lintian depends on:
ii  binutils               2.17-3            The GNU assembler, linker and bina
ii  diffstat               1.43-2            produces graph of changes introduc
ii  dpkg-dev               1.13.22           package building tools for Debian
ii  file                   4.17-4            Determines file type using "magic"
ii  gettext                0.14.6-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-3           The on-line manual pager
ii  perl [libdigest-md5-pe 5.8.8-6.1         Larry Wall's Practical Extraction 

lintian recommends no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
> Rsyncrypto is a package that performs rsync friendly encryption. The
> package comes bundled with a "tests" directory, that gets installed into
> /usr/share/doc/rsyncrypto/examples/tests. This directory contains known
> plain texts, cipher texts and keys so that regression testing and
> comparisons can be run.
> 
> Some of the files in said directory are records of when the internal
> decision function decided to perform an IV reset. For some of the
> regression testing files (reg1 and reg2), this file is empty.

As noted earlier on this bug, I think it's best for this to stay an
override since this also catches real packaging issues.  (For example, I
can see someone copying the whole examples directory from upstream without
noticing that some of the examples or documentation were never finished
and are empty.)

We'll see if anyone else runs into this and reopens this bug or opens a
new one.  If so, I'll definitely reconsider.

-- 
Russ Allbery (rra@debian.org)               <http://www.eyrie.org/~eagle/>

--- End Message ---
Reply to: