When enabling a emul32 bit build, it goes through the process of building the package twice, but the first build isn't using the emul32/x86_64.yml profile, so simply builds the same 64bit build twice.
To reproduce, enable emul32 and witness the 64bit profile on the initial build. Tested with mason locally so not due to out of date boulder in protosnek.
When enabling a emul32 bit build, it goes through the process of building the package twice, but the first build isn't using the emul32/x86_64.yml profile, so simply builds the same 64bit build twice.
To reproduce, enable emul32 and witness the 64bit profile on the initial build. Tested with
mason
locally so not due to out of dateboulder
in protosnek.