public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Pierre Humblet <Pierre.Humblet@alum.mit.edu>
To: cygwin-apps@cygwin.com
Subject: Re: Exim upgrade to 4.92.3 needed for multiple CVEs
Date: Fri, 04 Oct 2019 20:59:00 -0000	[thread overview]
Message-ID: <7ff3ade3-532f-1f94-c10f-f27c540f5bbc@alum.mit.edu> (raw)
In-Reply-To: <87imp4k1ho.fsf@Rainer.invalid>

On 10/4/2019 10:51 AM, ASSI wrote:

> Brian Inglis writes:
> […]
>
> I am looking at that package, but sadly it is in an advanced state of
> bitrot.  The source package doesn't contain all the files that are
> actually needed for the binary package.  Besides, exim itself uses one
> of these homegrown build systems that has of course changed since the
> last time exim was built for Cygwin.  I've got it to compile, but the
> packaging is incomplete and requires quite a bit more work than I was
> planning to spend.
>
> I would suggest to drop the package unless Pierre provides an update
> himself, but if anybody wants to adopt the package and fix things up
> properly I'll be happy to let you have the incomplete cygport file and
> patches.
>
>
> Regards,
> Achim.

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.

Pierre

  parent reply	other threads:[~2019-10-04 20:59 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 [this message]
2019-10-05  8:02       ` ASSI
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=7ff3ade3-532f-1f94-c10f-f27c540f5bbc@alum.mit.edu \
    --to=pierre.humblet@alum.mit.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).