We're getting activations errors when metadata is being attached to read-only files on the buildbots. This causes errors on activation (with MP's libarchive and HFS compression) due to is likely bug in libarchive wrt. chmod() and setting metadata order-of-operations.
That said, do we know why this metadata is being created on some subset of files in some subset of ports? Like some (?!) of the gzipped manpages? Please take a look and chime in / add yourself to the cc: here if you can help: https://trac.macports.org/ticket/60176#comment:16 Thanks, - Eric
