#63623 closed defect (worksforme)
dependency on openssl broken???
| Reported by: | mouse07410 (Mouse) | Owned by: | cjones051073 (Chris Jones) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | Cc: | mascguy (Christopher Nielsen), jmroot (Joshua Root) | |
| Port: | openssl |
Description
MacOS Big Sur 11.6, Xcode-13.0, current Macports.
Port seems to believe that openssl @1.1.1l_1 is older than and needs to be updated to openssl @1.1_0.
$ port version Version: 2.7.1 $ port outdated The following installed ports are outdated: links 2.24_0 < 2.25_0 openssl 1.1.1l_1 < 1.1_0 (epoch 1 < 2) $ port installed openssl The following ports are currently installed: openssl @1.1_0 openssl @1.1.1l_1 (active)
Then, something weird - not sure if it's related:
$ port -d outdated The following installed ports are outdated: links 2.24_0 < 2.25_0 openssl 1.1.1l_1 < 1.1_0 (epoch 1 < 2) p5.26-algorithm-diff (1.201.0_0 is installed; the port was not found in the port index) p5.26-authen-sasl (2.160.0_0 is installed; the port was not found in the port index) p5.26-b-cow (0.4.0_0 is installed; the port was not found in the port index) p5.26-capture-tiny (0.480.0_0 is installed; the port was not found in the port index) p5.26-cgi (4.530.0_0 is installed; the port was not found in the port index) p5.26-clone (0.450.0_0 is installed; the port was not found in the port index) p5.26-cpan-meta (2.150.10_0 is installed; the port was not found in the port index) p5.26-cpan-meta-requirements (2.140.0_0 is installed; the port was not found in the port index) p5.26-cpan-meta-yaml (0.18.0_0 is installed; the port was not found in the port index) p5.26-devel-checkbin (0.40.0_0 is installed; the port was not found in the port index) p5.26-digest-hmac (1.40.0_0 is installed; the port was not found in the port index) p5.26-digest-sha1 (2.130.0_4 is installed; the port was not found in the port index) p5.26-encode (3.100.0_0 is installed; the port was not found in the port index) p5.26-encode-locale (1.50.0_0 is installed; the port was not found in the port index) p5.26-error (0.170.290_0 is installed; the port was not found in the port index) p5.26-extutils-makemaker (7.600.0_0 is installed; the port was not found in the port index) p5.26-extutils-manifest (1.730.0_0 is installed; the port was not found in the port index) p5.26-gssapi (0.280.0_3 is installed; the port was not found in the port index) p5.26-html-parser (3.760.0_0 is installed; the port was not found in the port index) p5.26-html-tagset (3.200.0_4 is installed; the port was not found in the port index) p5.26-http-date (6.50.0_0 is installed; the port was not found in the port index) p5.26-http-message (6.320.0_0 is installed; the port was not found in the port index) p5.26-inc-latest (0.500.0_0 is installed; the port was not found in the port index) p5.26-io (1.450.0_0 is installed; the port was not found in the port index) p5.26-io-html (1.4.0_0 is installed; the port was not found in the port index) p5.26-io-socket-inet6 (2.720.0_0 is installed; the port was not found in the port index) p5.26-io-socket-ip (0.410.0_0 is installed; the port was not found in the port index) p5.26-io-socket-ssl (2.71.0_0 is installed; the port was not found in the port index) p5.26-locale-gettext (1.70.0_0 is installed; the port was not found in the port index) p5.26-lwp-mediatypes (6.40.0_0 is installed; the port was not found in the port index) p5.26-module-build (0.423.100_0 is installed; the port was not found in the port index) p5.26-module-metadata (1.0.37_0 is installed; the port was not found in the port index) p5.26-mozilla-ca (20200520_0 is installed; the port was not found in the port index) p5.26-net-libidn (0.120.0_5 is installed; the port was not found in the port index) p5.26-net-smtp-ssl (1.40.0_0 is installed; the port was not found in the port index) p5.26-net-ssleay (1.900.0_0 is installed; the port was not found in the port index) p5.26-perl-ostype (1.10.0_0 is installed; the port was not found in the port index) p5.26-pod-escapes (1.70.0_0 is installed; the port was not found in the port index) p5.26-pod-simple (3.420.0_0 is installed; the port was not found in the port index) p5.26-podlators (4.140.0_0 is installed; the port was not found in the port index) p5.26-scalar-list-utils (1.560.0_0 is installed; the port was not found in the port index) p5.26-socket (2.31.0_0 is installed; the port was not found in the port index) p5.26-socket6 (0.290.0_0 is installed; the port was not found in the port index) p5.26-sub-name (0.260.0_0 is installed; the port was not found in the port index) p5.26-sub-uplevel (0.280.0_0 is installed; the port was not found in the port index) p5.26-term-readkey (2.380.0_0 is installed; the port was not found in the port index) p5.26-test-deep (1.130.0_0 is installed; the port was not found in the port index) p5.26-test-exception (0.430.0_0 is installed; the port was not found in the port index) p5.26-test-fatal (0.16.0_0 is installed; the port was not found in the port index) p5.26-test-needs (0.2.9_0 is installed; the port was not found in the port index) p5.26-test-nowarnings (1.40.0_1 is installed; the port was not found in the port index) p5.26-test-warn (0.360.0_0 is installed; the port was not found in the port index) p5.26-time-local (1.300.0_0 is installed; the port was not found in the port index) p5.26-timedate (2.330.0_0 is installed; the port was not found in the port index) p5.26-try-tiny (0.300.0_0 is installed; the port was not found in the port index) p5.26-uri (5.90.0_0 is installed; the port was not found in the port index) p5.26-version (0.992.900_0 is installed; the port was not found in the port index) $
Change History (14)
comment:1 Changed 3 years ago by mouse07410 (Mouse)
comment:2 Changed 3 years ago by mascguy (Christopher Nielsen)
| Cc: | mascguy added |
|---|
comment:3 Changed 3 years ago by mascguy (Christopher Nielsen)
| Cc: | jmroot added |
|---|---|
| Owner: | set to cjones051073 |
| Status: | new → assigned |
I saw something similar in one of my macOS installations last night... 10.12 maybe?
@cjones/@jmroot, any thoughts?
comment:4 Changed 3 years ago by cjones051073 (Chris Jones)
Please make sure your ports tree is fully up to date and try again ? The current version of openssl is 1.1_3 and the above is 1.1_0
> port info openssl openssl @1.1_3 (devel, security) Variants: universal Description: Shim port installing symbolic links in primary prefix pointing to the openssl11 installation. Library Dependencies: openssl11 Conflicts with: libressl, libressl-devel Platforms: darwin License: MIT Maintainers: none
comment:5 Changed 3 years ago by mouse07410 (Mouse)
Please make sure your ports tree is fully up to date and try again ?
I tried multiple times, and I always do sudo port sync && sudo port selfupdate before doing (or re-doing) something. So, absolutely, got the same result.
Maybe it's less relevant now, as I deleted all of the installed ports, and re-populating one-by-one. Royal pain in the neck, because restore_ports.tcl never ever worked for me.
I'd like to add that making v1.1 newer than v1.1.1 was, in my opinion, a very bad idea:
openssl 1.1.1l_1 < 1.1_0 (epoch 1 < 2)
comment:6 Changed 3 years ago by cjones051073 (Chris Jones)
Changing the numbering scheme, dropping the minor patch versions from the shim port was necessary, and the epoch is there for this very scenario. Nothing wrong with doing this.
I suspect you must of had some manual intervention on your install area, to get a message like
Error: Failed to activate openssl: Image error: /opt/local/include/openssl already exists and does not belong to a registered port.
It would have been useful if you had deactivated all openssl and the curl-ca-bundle ports, and then had a look to see what was there, but I guess thats not an option now.
comment:7 Changed 3 years ago by cjones051073 (Chris Jones)
Also, your port tree *cannot* have been up to date if you had been trying to in stall openssl 1.1_0.....
comment:8 Changed 3 years ago by cjones051073 (Chris Jones)
| Resolution: | → worksforme |
|---|---|
| Status: | assigned → closed |
comment:9 follow-up: 10 Changed 3 years ago by mouse07410 (Mouse)
I suspect you must of had some manual intervention on your install area
No, Macports simply got confused by versioning, and did not install 1.1_0 over deactivated 1.1.1l. I did not know which one to force out either.
Also, your port tree *cannot* have been up to date if you had been trying to install openssl 1.1_0
It was - at the date/time of this ticket creation! Of course, during the last 37 hours openssl moved from 1.1_0 to 1.1_3 and then 1.1_5.
I suspect 1.1_0 broke things, subsequently improved in 1.1_3 and fixed in 1.1_5. I was "lucky" to catch the half-baked release 1.1_0.
comment:10 Changed 3 years ago by cjones051073 (Chris Jones)
Replying to mouse07410:
I suspect you must of had some manual intervention on your install area
No, Macports simply got confused by versioning, and did not install 1.1_0 over deactivated 1.1.1l. I did not know which one to force out either.
No, Macports had no issues with the versions. It understands epochs just fine. Your error message was clear - there where files under /opt/local/include/openssl that where not registered to any port and hence openssl could not activate as it wanted to create that area. Since you wiped the area before investigating we cannot t this point know what they where.
Also, your port tree *cannot* have been up to date if you had been trying to install openssl 1.1_0
It was - at the date/time of this ticket creation! Of course, during the last 37 hours openssl moved from 1.1_0 to 1.1_3 and then 1.1_5.
there is no openssl 1.1_5 version..... 1.1_3 i still the latest. (openssl11 is at 1.1.1l_5 but that is a different port).
Yes, at the time you opened the ticket 1.1_0 might still have been the latest. But things have been fixed since then which is why I asked you to try again with the latest versions, which at the time (and still is) openssl 1.1_3.
I suspect 1.1_0 broke things, subsequently improved in 1.1_3 and fixed in 1.1_5. I was "lucky" to catch the half-baked release 1.1_0.
comment:11 Changed 3 years ago by mouse07410 (Mouse)
here is no openssl 1.1_5 version..... 1.1_3 is still the latest. (openssl11 is at 1.1.1l_5 but that is a different port).
Could you please explain what I'm observing now on all of my machines after successful update? Does it look correct to you?
$ port -v installed | grep openssl openssl @1.1_3 (active) requested_variants='' platform='darwin 20' archs='x86_64' date='2021-10-14T15:42:14-0400' openssl11 @1.1.1l_5 (active) requested_variants='' platform='darwin 20' archs='x86_64' date='2021-10-14T15:41:59-0400' py39-openssl @19.1.0_1 (active) requested_variants='' platform='darwin 20' archs='noarch' date='2021-10-13T22:11:35-0400' qt5-qtbase @5.15.2_2+openssl (active) requested_variants='' platform='darwin 20' archs='x86_64' date='2021-10-13T19:35:06-0400'
Note that OpenSSL was not installed explicitly, but (in this case) as a dependency of other ports.
comment:12 Changed 3 years ago by cjones051073 (Chris Jones)
looks fine to me. what exactly confuses you ?
comment:13 Changed 3 years ago by mascguy (Christopher Nielsen)
@Mouse, bear in mind that port openssl is now a shim port, which creates symlinks to openssl11. So it's correct that you have both installed.
comment:14 Changed 3 years ago by mouse07410 (Mouse)
looks fine to me. what exactly confuses you ?
This:
"1.1_3 is still the latest. (openssl11 is at 1.1.1l_5 but that is a different port)."
port
opensslis now a shim port, which creates symlinks toopenssl11. So it's correct that you have both installed.
Thanks
I removed all the ports via
sudo port -f uninstall installed, and tried from scratch.OpenSSL port screw-up still breaks it: