openssl @1.0.1f_0 violates the layout of the ports-filesystems - activation failure

[lrenaud (Luke)]

The current version of openssl in the Macports database attempts to install files directly into the root of the port system, as well as the root of the filesystem. These files furthermore should have nothing to do with the actual port, and prevent it's activation if the port tool is being run as an unprivileged user.

--->  Computing dependencies for openssl
--->  Fetching distfiles for openssl
--->  Verifying checksums for openssl
--->  Extracting openssl
--->  Applying patches to openssl
--->  Configuring openssl
--->  Building openssl
--->  Staging openssl into destroot
Warning: violation by /.DS_Store
Warning: violation by /opt/local/.DS_Store
Warning: openssl violates the layout of the ports-filesystems!
Warning: Please fix or indicate this misbehavior (if it is intended), it will be an error in future releases!
--->  Installing openssl @1.0.1f_0
--->  Cleaning openssl
--->  Computing dependencies for openssl
--->  Activating openssl @1.0.1f_0
Error: org.macports.activate for port openssl returned: Image error: /opt/local/.DS_Store already exists and does not belong to a registered port.  Unable to activate port openssl. Use 'port -f activate openssl' to force the activation.
Please see the log file for port openssl for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_openssl/openssl/main.log

Attached is the primary output from the port tool, the output of attempted forced activation with a verbose flag, and the log file produced by the system.

[lrenaud (Luke)]

Results of attempted forced activation

[lrenaud (Luke)]

Output log for the build/activation attempt the system initially performs

[mark@…]

Cc Me!

[larryv (Lawrence Velázquez)]

I’m not seeing this with 1.0.2, so I’ll assume this isn’t an issue anymore.