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

RFS: dma (updated, bugs fixed)



Dear mentors,

I am looking for a sponsor for the new version 0.0.2009.07.17-2
of my package "dma".  It updates the packaging a bit and fixes two bugs
from the Debian BTS - allows the spool directory to live on a filesystem
like XFS that does not set the d_type field in the dirent structure, and
generates better, longer, more random, more reliable Message-Id fields on
new messages if the MUA has not done so.

It builds a single binary package:
dma        - lightweight mail transport agent

The package has been tested with lintian and pbuilder.

The upload would fix these bugs: 544357 (spool on XFS), 544475 (better
Message-Id)

The package can be found on mentors.debian.net:
http://mentors.debian.net/debian/pool/main/d/dma/dma_0.0.2009.07.17-2.dsc

I would be glad if someone uploaded this package for me.

JFYI, here's the changelog entry:

dma (0.0.2009.07.17-2) unstable; urgency=low

  * Allow the spool directory to live on a filesystem that does not
    set the d_type member of the dirent structure, like XFS.
    Closes: #544357
  * Randomize the Message-Id a bit more.  Closes: #544475
  * Bump Standards-Version to 3.8.3 with no changes.
  * Only enable the build hardening wrapper if the "hardening" build
    option is specified.
  * Switch the copyright file header from the Wiki to DEP 5.
  * Remove the manual page ".Dx" patch - the groff version in Squeeze
    knows about the .Dx mdoc macro.  Add a lintian override for
    the "Unknown DragonFly version" error.
  * Convert the patch file headers to the DEP 3 format.

 -- Peter Pentchev <roam@ringlet.net>  Tue, 01 Sep 2009 13:36:33 +0300

G'luck,
Peter

-- 
Peter Pentchev	roam@ringlet.net    roam@space.bg    roam@FreeBSD.org
PGP key:	http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint	FDBA FD79 C26F 3C51 C95E  DF9E ED18 B68D 1619 4553
If I were you, who would be reading this sentence?

Attachment: pgpjP_ojWNvoo.pgp
Description: PGP signature


Reply to: