public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps@cygwin.com
Subject: Re: [HHITP] mailutils 3.2
Date: Fri, 31 Mar 2017 14:34:00 -0000	[thread overview]
Message-ID: <4f7fe92f-a9bf-d29b-a2b2-1f7eb366c242@cornell.edu> (raw)
In-Reply-To: <f9e8820e-ae0e-a515-e4ad-822d19dc6564@cornell.edu>

On 3/27/2017 4:55 PM, Ken Brown wrote:
> On 3/27/2017 3:32 PM, Yaakov Selkowitz wrote:
>> On 2017-03-24 14:54, Ken Brown wrote:
>>> This is a half-hearted ITP for GNU mailutils
>>> (https://www.gnu.org/software/mailutils/mailutils.html).  I'd like some
>>> feedback before I proceed.
>>>
>>> My only interest in mailutils is that it provides a utility
>>> movemail.exe, which is used by emacs.[*]  But I looked into providing a
>>> complete build of mailutils and various subpackages along the lines of
>>> Debian[**], and it turned out to be straightforward.  My cygport file
>>> and patches are attached.  I ran the testsuite, and there were 42
>>> failures and 3 skips out of 978 tests.  The failures ought to be looked
>>> at, but I don't this is too bad.
>>
>> FWIW, even on Debian, the tests succeed until comsatd tests 2-7 all
>> fail, at which point make check terminates.  So if those are your first
>> failures, it may just be the testsuite.
>
> No, the comsatd tests all pass.  The failures I'm seeing are in imap4d,
> maidag, and sieve.  And for some reason that I haven't figured out, the
> pop3d tests aren't run.  The tests use dejagnu, and they report that
> runtest can't be found.

I found a workaround, and the pop3d tests now run and all 112 pass.  So 
I'm feeling a little more confident that the build is OK.  I'll probably 
send a real ITP within a few days.

Ken

  reply	other threads:[~2017-03-31 14:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-24 19:55 Ken Brown
2017-03-27 19:32 ` Yaakov Selkowitz
2017-03-27 20:55   ` Ken Brown
2017-03-31 14:34     ` Ken Brown [this message]
2017-03-28 12:40 ` Andrew Schulman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4f7fe92f-a9bf-d29b-a2b2-1f7eb366c242@cornell.edu \
    --to=kbrown@cornell.edu \
    --cc=cygwin-apps@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).