You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I searched open reports and couldn't find a duplicate
What happened?
The package installer for macOS fails if virtual_specs is provided in construct.yaml. I expected it not to fail 😄.
Additional Context
The construct.yaml listed below results in the following error upon installation.
The exact same file, but with virtual_specs removed, results in a successful install.
The install.log indicates a PackagesNotFoundError regarding __osx[version='>=12'] from a conda solve in the prepare_installation script. However, the documentation states "In PKG installers, __osx specs can be checked natively without the solver being involved as long as only >=, < or , are used." So there seems to be an inconsistency here. Perhaps I'm not implementing this feature correctly 😄.
I'm adding some code in #887. I'm assuming it had to do with SYSTEM_VERSION_COMPAT not being set. That said, that PR removes the conda-native checks for __osx and __glibc (they are being tested earlier anyway), so check that branch if you want.
Checklist
What happened?
The package installer for macOS fails if
virtual_specs
is provided inconstruct.yaml
. I expected it not to fail 😄.Additional Context
The
construct.yaml
listed below results in the following error upon installation.The exact same file, but with
virtual_specs
removed, results in a successful install.The
install.log
indicates aPackagesNotFoundError
regarding__osx[version='>=12']
from a conda solve in theprepare_installation
script. However, the documentation states "In PKG installers,__osx
specs can be checked natively without the solver being involved as long as only>=
,<
or,
are used." So there seems to be an inconsistency here. Perhaps I'm not implementing this feature correctly 😄.I'm using
constructor=3.9.3
.construct.yaml contents
install.log excerpt
The text was updated successfully, but these errors were encountered: