Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 30 Apr 2018 18:02:38 +0000
From:      bugzilla-noreply@freebsd.org
To:        apache@FreeBSD.org
Subject:   [Bug 227868] www/apache24: 2.4.33 won't start anymore with LibreSSL
Message-ID:  <bug-227868-16115-YPnSgkJjKZ@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-227868-16115@https.bugs.freebsd.org/bugzilla/>
References:  <bug-227868-16115@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D227868

Bernard Spil <brnrd@freebsd.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|New                         |In Progress
                 CC|                            |brnrd@freebsd.org

--- Comment #3 from Bernard Spil <brnrd@freebsd.org> ---
(In reply to Jens K. Loewe from comment #0)
(In reply to M. Macha from comment #1)
(In reply to mark.j.lysek from comment #2)

Hi all,

Can you please let me know how you updated
(poudriere/portmaster/portupdate/"make") and what order you used when updat=
ing?
Did you read UPDATING before building?

I currently believe that using portmaster/portupgrade _only_ works when
 1. Update ports tree (and thus LibreSSL to 2.7)
 2. Run `portmaster -r libressl`
 3. Run `portmaster -a`
Any other method will lead to non-functional environment.

I'm sorry for the issues this causes. It's undoable to bump all portrevisio=
ns
(about half the ports tree). I've yet to receive reports of issues when usi=
ng
poudriere, you are **strongly** recommended to stop using
portmaster/portupgrade which are basically unsupported.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-227868-16115-YPnSgkJjKZ>