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

Uploaded nmh 1.0.4+dev-20010317-1 (sparc) to ftp-master



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

Format: 1.7
Date: Sat, 10 Nov 2001 13:03:30 -0500
Source: nmh
Binary: nmh
Architecture: sparc
Version: 1.0.4+dev-20010317-1
Distribution: unstable
Urgency: low
Maintainer: Debian/sparc Build Daemon <buildd@sparc.debian.org>
Changed-By: Doug Porter <dsp@debian.org>
Description: 
 nmh        - A set of electronic mail handling programs.
Closes: 90286 100482 112505
Changes: 
 nmh (1.0.4+dev-20010317-1) unstable; urgency=low
 .
   * Update to the latest CVS snapshot which I have marked 20010317, because
     the most recent commits were made on the March 17, 2001.
   * Bring up to par with Debian Policy 3.5.6.
   * Fix sbr/mts.c so that it discards trailing whitespace from values when
     reading mts.conf.  (closes: Bug#112505)
   * Applied patch submitted by Colin Watson <cjw44@flatline.org.uk> that
     fixed a bug in the forw(1) and mhstore(1) man pages which caused groff
     to eat a line.  (closes: Bug#90286)
   * The original patch to man/Makefile.in which moved the mh-chart and nmh
     man pages from section one to seven was inadequate, but it has now been
     fixed.
   * Provide a symbolic link for the nmh(7) man page so that it is
     accessible as mh(7) too.  (closes: Bug#100482)
   * Fix the S1G bug in sbr/fmt_scan.c.
   * Make /etc/nmh/rcvdistcomps.outbox a conffile.
   * Install mh_profile(5) as a symbolic link to mh-profile(5), not a hard
     link.
   * New package maintainer.  My thanks to the previous maintainer, Ruud de
     Rooij, for all his work.
Files: 
 b8f0f5f4bd7087483356a5a928376e77 2101998 mail optional nmh_1.0.4+dev-20010317-1_sparc.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.6 <http://mailcrypt.sourceforge.net/>

iEYEARECAAYFAjvuuDMACgkQgD/uEicUG7B1BwCgk3MOhvN1sDkxsL4NWXdJXP+7
+BAAn3I3Lvanr5/NwvgYKtwlstwSHBzL
=g1qU
-----END PGP SIGNATURE-----



Reply to: