> On Dec 9, 2024, at 6:16 AM, Chris Jones via macports-users
> <[email protected]> wrote:
>
>
> See https://github.com/macports/macports-ports/pull/27003
Thanks Chris!
>
> On 09/12/2024 10:11 am, Chris Jones via macports-users wrote:
>> Hi,
>> The change was intentional, see
>> https://trac.macports.org/ticket/70767
>> going back to the previous dep is not an option, but what could be done is
>> update the python312 port to not use the port:openssl dep, but instead use
>> the openssl PG to configure its build to use the isolated openssl3 port
>> instead. The reason this would help is the openssl port is just a shim port,
>> that installs into your primary prefix sym links to the files installed by
>> the openssl3 into an isolate location in libexec. Its only this shim port
>> than conflicts with libressl, the isolated openssl3 port does not.
>> But this is something you should discuss with the port maintainer here.
>> Chris
>> On 09/12/2024 1:54 am, Kastus Shchuka wrote:
>>> I have three versions of python3 installed: 3.10, 3.11, and 3.12. I also
>>> have libressl installed, but not openssl, as it is not possible to have
>>> both, and I prefer to use libressl.
>>>
>>> Up till version 3.12.6_0 of python312 I have no problems keeping up-
>>> to-date with python ports.
>>>
>>> With 3.12.7_0 python312 started to explicitly require openssl. Curiously
>>> enough, python310 and python311 still work fine and install with lbressl.
>>>
>>> ---> Computing dependencies for python310
>>> ---> Fetching archive for python310
>>> ---> Attempting to fetch
>>> python310-3.10.16_0+lto+optimizations.darwin_22.x86_64.tbz2 from
>>> http://mirror.fcix.net/macports/packages/python310
>>> ---> Attempting to fetch
>>> python310-3.10.16_0+lto+optimizations.darwin_22.x86_64.tbz2.rmd160 from
>>> http://mirror.fcix.net/macports/packages/python310
>>> ---> Installing python310 @3.10.16_0+lto+optimizations
>>> ---> Cleaning python310
>>> ---> Computing dependencies for python310
>>> ---> Deactivating python310 @3.10.15_0+lto+optimizations
>>> ---> Cleaning python310 ---> Activating
>>> python310 @3.10.16_0+lto+optimizations
>>> ---> Cleaning python310 ---> Computing
>>> dependencies for python311
>>> ---> Fetching archive for python311
>>> ---> Attempting to fetch
>>> python311-3.11.11_0+lto+optimizations.darwin_22.x86_64.tbz2 from
>>> http://mirror.fcix.net/macports/packages/python311
>>> ---> Attempting to fetch
>>> python311-3.11.11_0+lto+optimizations.darwin_22.x86_64.tbz2.rmd160 from
>>> http://mirror.fcix.net/macports/packages/python311
>>> ---> Installing python311 @3.11.11_0+lto+optimizations
>>> ---> Cleaning python311
>>> ---> Computing dependencies for python311
>>> ---> Deactivating python311 @3.11.10_0+lto+optimizations
>>> ---> Cleaning python311 ---> Activating
>>> python311 @3.11.11_0+lto+optimizations
>>> ---> Cleaning python311 ---> Updating
>>> database of binaries
>>> ---> Scanning binaries for linking errors
>>> ---> No broken files found. ---> No broken
>>> ports found.
>>>
>>>
>>> Unfortunately, there are quite a few port that require python312
>>> specifically (and not any python3), and I cannot upgrade those ports
>>> without replacing libressl with openssl.
>>>
>>> 7zip 24.08_0 < 24.09_0
>>> gobject-introspection 1.78.1_3 < 1.78.1_4
>>> libheif 1.18.2_1 < 1.19.5_1
>>>
>>> I wonder what was the reason for removing of path:lib/libssl.dylib
>>> dependency in python312 port.
>>>
>>> $ port cat python312 | grep ssl
>>> port:openssl \
>>> $ port cat python310 | grep ssl
>>> path:lib/libssl.dylib:openssl \
>>> $ port cat python311 | grep ssl
>>> path:lib/libssl.dylib:openssl \
>>>
>>>
>>> Is it possible to change that dependency back to what it was in 3.12.6_0?
>>> Here is *ssl* port that I have installed and active:
>>>
>>> $ port installed and \*ssl\* and active
>>> The following ports are currently installed:
>>> libressl @4.0.0_0 (active)
>>> openssl3 @3.4.0_0 (active)
>>> openssl11 @1.1.1w_1 (active)
>>>
>>>
>>> Thanks,
>>>
>>> Kastus
>>>
>
