Changes between Initial Version and Version 2 of Ticket #68791


Ignore:
Timestamp:
Nov 28, 2023, 3:35:41 AM (6 months ago)
Author:
ryandesign (Ryan Carsten Schmidt)
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #68791

    • Property Status changed from new to closed
    • Property Summary changed from openssl 3.2.0 incompatible with psql to openssl @3.2.0: incompatible with psql
    • Property Keywords openssl3 psql removed
    • Property Resolution changed from to duplicate
    • Property Port postgresql16 added; psql removed

  • Ticket #68791 – Description

    initial v2  
    1717}}}
    1818
    19 I chanced upon [https://stackoverflow.com/a/77558811 this stack overflow response] and gave reverting [https://github.com/macports/macports-ports/commit/95984554 commit 95984554] a shot. Results show that neither psql13 nor psql16 can run with openssl3@3.2.0, while both run fine with openssl3@3.1.4
     19I chanced upon [https://stackoverflow.com/a/77558811 this stack overflow response] and gave reverting [959845548b0dcf19985aeba7bfa1366bc2f4d55e/macports-ports] a shot. Results show that neither psql13 nor psql16 can run with openssl3@3.2.0, while both run fine with openssl3@3.1.4
    2020
    2121This might be reported upstream, I'm not sure whether with the openssl or the postgresql folks, but I wanted to open a bug here against openssl3 port since this port update triggered the breakage.