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

Uploaded integrit 3.02.00-1 (m68k) to erlangen



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

Format: 1.7
Date: Mon,  9 Sep 2002 21:15:32 +0200
Source: integrit
Binary: integrit
Architecture: m68k
Version: 3.02.00-1
Distribution: unstable
Urgency: low
Maintainer: Debian/m68k Build Daemon <buildd@kullervo.biophys.uni-duesseldorf.de>
Changed-By: Andras Bali <bali@debian.org>
Description: 
 integrit   - A file integrity verification program like tripwire
Closes: 124758 134869
Changes: 
 integrit (3.02.00-1) unstable; urgency=low
 .
   * New upstream release.
     - Several portability enhancements, test suite (not included
       in the Debian package).
     - Large file support.
     - Made i-ls accept multiple filenames.
     - Made i-ls and i-viewdb show SHA-1 checksums by default.
     - Changing to cmp-style exit status: 0 for no change; 1 for
       changes detected; 2 for error.
     - New database format, incompatible with the old one. Please
       read README.Debian.
   * Major clean-up in the package.
     - Removed install-time database generation, it was pointless,
       and didn't even work.
     - Added debconf question about sending out mails when no
       changes were detected.
     - /etc/integrit/integrit.debian.conf is no longer a conffile,
       as it is automatically modified by the postinst script.
     - Lowered priorities of debconf questions.
     - Fixed scripts (Closes: #134869).
   * Added debconf dependancy, removed fall-back mechanism.
   * Added mailx dependancy, required by the cron job.
   * Corrected spelling error in description (Closes: #124758).
Files: 
 1f2143594016bb0209dc5683959c5d1a 218232 admin optional integrit_3.02.00-1_m68k.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.6 <http://mailcrypt.sourceforge.net/>

iD8DBQE9fiqdcS3JWD3FdvcRAm4nAJ4ke3EoCwfhXBblVYOkuhFGmeKOlACggPVX
nZviVVSKAgiIL46FHC5NxRU=
=nf4r
-----END PGP SIGNATURE-----



Reply to: