From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-apps@cygwin.com
Subject: Re: Exim upgrade to 4.92.3 needed for multiple CVEs
Date: Fri, 04 Oct 2019 20:50:00 -0000 [thread overview]
Message-ID: <1551c872-673f-6758-7fe0-5d6dd31f6fd9@SystematicSw.ab.ca> (raw)
In-Reply-To: <87imp4k1ho.fsf@Rainer.invalid>
On 2019-10-04 08:51, ASSI wrote:
> 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.
That was what I found and thought.
If you don't mind me asking, how much did you get to build, and what do you see
needing done?
If you got further than me, I might be willing to complete the packaging.
> 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.
+1
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
next prev parent reply other threads:[~2019-10-04 20:50 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 [this message]
2019-10-04 20:59 ` Pierre Humblet
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=1551c872-673f-6758-7fe0-5d6dd31f6fd9@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).