From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: HEADS UP package "fetchmail" vulnerable and 6.4.0 release candidate out
Date: Wed, 21 Aug 2019 19:39:00 -0000 [thread overview]
Message-ID: <87zhk273cw.fsf@Rainer.invalid> (raw)
In-Reply-To: <18a325b3-0934-0e7f-aa6b-45828ae03ce7@gmx.de> (Matthias Andree's message of "Tue, 20 Aug 2019 19:49:18 +0200")
Matthias Andree writes:
> 3. Please try to package 6.4.0.rc2 for x86 and x86_64 against Cygwin's
> libssl1.1, and see if you find any portability issues that would require
> fixing before 6.4.0. Deadline end of August 2019, and unless really
> needed for non-trivial code changes, rc2 is also the planned final
> candidate.
The package builds without any trouble on both architectures (I've
enabled Kerberos5, GSSAPI and NTLM also). The tests skip the two XHTML
validation tests, I have not been able to find out why that is.
> Source tarballs and detached ASCII-armored GnuPG signatures at
> <https://sourceforge.net/projects/fetchmail/files/branch_6.4/>.
Where's the public key for that signature?
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
DIY Stuff:
http://Synth.Stromeko.net/DIY.html
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2019-08-21 18:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-20 19:44 Matthias Andree
2019-08-21 19:39 ` Achim Gratz [this message]
2019-08-28 12:55 ` Corinna Vinschen
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=87zhk273cw.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin@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).