search

conda-forge / boost-feedstock

A conda-smithy repository for boost.
BSD 3-Clause "New" or "Revised" License
15 stars 41 forks source link

Corrupted libs with osx-arm64 build? #178

Closed h-vetinari closed 1 year ago

h-vetinari commented 1 year ago

Just noticed this in CI:

SafetyError: The package for libboost located at /Users/runner/miniforge3/pkgs/libboost-1.82.0-h72cdd8a_4
appears to be corrupted. The path 'lib/libboost_atomic.dylib'
has an incorrect size.
  reported size: 87312 bytes
  actual size: 86178 bytes

SafetyError: The package for libboost located at /Users/runner/miniforge3/pkgs/libboost-1.82.0-h72cdd8a_4
appears to be corrupted. The path 'lib/libboost_chrono.dylib'
has an incorrect size.
  reported size: 61328 bytes
  actual size: 60194 bytes

SafetyError: The package for libboost located at /Users/runner/miniforge3/pkgs/libboost-1.82.0-h72cdd8a_4
appears to be corrupted. The path 'lib/libboost_container.dylib'
has an incorrect size.
  reported size: 123552 bytes
  actual size: 122421 bytes

and so on...

This seems to have been overlooked in #164, unfortunately. šŸ˜‘

We did have some other SafetyErrors for the unification related to CMake metadata, which got fixed in 43373e65b5721f029fd59db95cf9ab7cd74dc9b8 and 3c87dcf6d04df7b904c46d5267459d5a78a4624d; this could be similar in principle.

What I could imagine happening: we're generating signature with cctools upon first installation (for libboost), which changes the artefacts. Once we copy them again for libboost-devel, the signature doesn't get generated, and so conda gets confused with the sizes?