sslscan error after upgrade

[smolikr]

sudo port upgrade outdated
--->  Computing dependencies for sslscan
--->  Fetching archive for sslscan
--->  Attempting to fetch sslscan-1.11.13-rbsec_1.darwin_18.x86_64.tbz2 from https://packages.macports.org/sslscan
--->  Attempting to fetch sslscan-1.11.13-rbsec_1.darwin_18.x86_64.tbz2 from http://nue.de.packages.macports.org/sslscan
--->  Attempting to fetch sslscan-1.11.13-rbsec_1.darwin_18.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/sslscan
--->  Fetching distfiles for sslscan
--->  Verifying checksums for sslscan
--->  Extracting sslscan
--->  Configuring sslscan
--->  Building sslscan
Error: Failed to build sslscan: command execution failed
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_net_sslscan/sslscan/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets to report a bug.

---

My Macports version is:

--->  Updating MacPorts base sources using rsync
MacPorts base version 2.5.4 installed,
MacPorts base version 2.5.4 downloaded.

[smolikr]

I also tried sudo port clean sslscan Password: ---> Cleaning sslscan

after this step, the result is:

sudo port echo requested bcwipe @1.7-7_0 fetch-crl @3.0.19_0 ghostscript @9.27_1+x11 nmap @7.70_0+pcre+ssl+subversion nmap @7.80_0+pcre+ssl+subversion nmap @7.80_1+pcre+ssl+subversion pcre @8.43_0 putty @0.70_0+gui scrub @2.6.1_0 sslscan @1.11.13-rbsec_0 tree @1.8.0_0 wget @1.20.3_1+gnutls youtube-dl @2019.07.30_0+ffmpeg+python37 youtube-dl @2019.08.13_0+ffmpeg+python37 zstd @1.4.2_0 zstd @1.4.3_0

when trying to launch sslscan, it returns:

sslscan dyld: Library not loaded: /opt/local/lib/libssl.1.0.0.dylib

Referenced from: /opt/local/bin/sslscan Reason: image not found

Abort trap: 6

[mf2k (Frank Schima)]

In the future, please use WikiFormatting, fill in the Port field and add the port maintainer(s) to Cc (port info --maintainers sslscan), if any.

[jmroot (Joshua Root)]

You haven't provided a log so it's impossible to be certain, but I would assume this is a duplicate of #58971.