public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: ASSI <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: Exim upgrade to 4.92.3 needed for multiple CVEs
Date: Sat, 05 Oct 2019 08:02:00 -0000	[thread overview]
Message-ID: <871rvrliwx.fsf@Rainer.invalid> (raw)
In-Reply-To: <7ff3ade3-532f-1f94-c10f-f27c540f5bbc@alum.mit.edu> (Pierre	Humblet's message of "Fri, 4 Oct 2019 16:59:31 -0400")

[-- Attachment #1: Type: text/plain, Size: 200 bytes --]

Pierre Humblet writes:
> I will take a look next week and release the latest version.
>
> I would be happy to pass on this package to anyone interested, either
> as is or after I prepare the latest.


[-- Attachment #2: exim-cygwin.tar.xz --]
[-- Type: application/x-xz, Size: 41032 bytes --]

[-- Attachment #3: Type: text/plain, Size: 780 bytes --]

I've attached what I managed to get to so far.  You are pulling in some
windows headers that define BOOL in a conflicting way to exim, so I
boldly went and changed that definition in exim.  I have no idea if
that's going to work, but it at least compiles.

As I said, the postinstall script is missing (I would need to pull it from the
latest binary archive I guess) and I'd need to arrange for the install to
actually use your exim.conf instead of the default one (some
doins/insinto invocation probably).  The install also didn't install the
manpage, so that needs fixing too.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Waldorf MIDI Implementation & additional documentation:
http://Synth.Stromeko.net/Downloads.html#WaldorfDocs

  reply	other threads:[~2019-10-05  8:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-20 17:10 Exim official upgrade to 4.92.2 urgently needed Brian Inglis
2019-10-04  8:16 ` Exim upgrade to 4.92.3 needed for multiple CVEs Brian Inglis
2019-10-04 14:51   ` ASSI
2019-10-04 20:50     ` Brian Inglis
2019-10-04 20:59     ` Pierre Humblet
2019-10-05  8:02       ` ASSI [this message]
2019-10-05  8:09         ` ASSI

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=871rvrliwx.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --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).