From: Stephen John Smoogen <smooge@gmail.com>
To: Andy Romens <Romens.Andy@hotmail.com>
Cc: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Questions on how to upgrade Apache
Date: Thu, 8 Apr 2021 10:33:38 -0400 [thread overview]
Message-ID: <CANnLRdh5nVPnKRkSqcKe1GEPk-yZCJO3LD9CmvGL_MTnnYZjEQ@mail.gmail.com> (raw)
In-Reply-To: <CH0PR14MB493040002A8FBD0C1643E204FB749@CH0PR14MB4930.namprd14.prod.outlook.com>
On Thu, 8 Apr 2021 at 10:02, Andy Romens via Cygwin <cygwin@cygwin.com>
wrote:
> Hi Cygwin (or whoever gets these, I just signed up),
>
> I got a question for you all. I need to update Apache from 2.4.39 to
> 2.4.46. I have searched far and wide on the web to see if there is a way to
> do that, but so far nothing has turned up. Any idea on how to do this or if
> an updated package will get released soon-ish for Apache? Background info,
> we are running Cygwin on a Windows 2012 Server. Anything else, please let
> me know and I will investigate.
>
>
It looks like the apache package is obsolete and orphaned currently. You
will need to compile a version of apache on the cygwin system itself to
update to a newer version.
https://cygwin.com/cygwin-pkg-maint
> Thank you in advance,
> -Andy
> --
> Problem reports: https://cygwin.com/problems.html
> FAQ: https://cygwin.com/faq/
> Documentation: https://cygwin.com/docs.html
> Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
>
--
Stephen J Smoogen.
next prev parent reply other threads:[~2021-04-08 14:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 20:34 Andy Romens
2021-04-06 20:37 ` Andy Romens
2021-04-08 5:30 ` Andrey Repin
2021-04-09 0:26 ` Brian S. Wilson
2021-04-08 13:22 ` Andy Romens
2021-04-08 14:33 ` Stephen John Smoogen [this message]
2021-04-08 15:49 ` Andy Romens
2021-04-08 15:57 ` Eliot Moss
2021-04-08 16:37 ` René Berber
2021-04-08 18:33 ` Glenn Strauss
2021-04-08 19:53 ` bzs
2021-04-09 6:23 ` KAVALAGIOS Panagiotis (EEAS-EXT)
2021-04-09 9:08 ` Csaba Raduly
2021-04-09 11:59 ` Brian S. Wilson
2021-04-09 14:46 ` Brian Inglis
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=CANnLRdh5nVPnKRkSqcKe1GEPk-yZCJO3LD9CmvGL_MTnnYZjEQ@mail.gmail.com \
--to=smooge@gmail.com \
--cc=Romens.Andy@hotmail.com \
--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).