briantoby
commented
3 months ago Problem is not Mac specific. Confirmed that I see the same bug on Linux.
Closed briantoby closed 2 months ago
briantoby
commented
3 months ago Problem is not Mac specific. Confirmed that I see the same bug on Linux.
jaimergp
commented
2 months ago Hm, I didn't know we could use abs paths there. I would approach this via:
~/builds as a channelchannels_remap if necessaryIOW, something like this:
name: gsas2full
version: 5773
channels:
- /Users/user/builds # [osx]
- /home/user/builds # [linux]
- C:\\tmp\\builds # [win]
- https://conda.anaconda.org/conda-forge
conda_default_channels:
- https://conda.anaconda.org/conda-forge
specs:
- python=3.11
- numpy=1.26
- matplotlib=3.8
- wxpython=4.2.1
- pillow
- pyopengl
- scipy
- conda
- requests
- hdf5
- h5py
- imageio
- git
- gitpython
- pywin32 [win]
- gsas2complete=5773
post_install: g2postinstall.sh [unix]
post_install: g2postinstall.bat [win]
license_file: EULA.txt
welcome_image: gsas2-welcome.png
icon_image: gsas2.png
keep_pkgs: False
register_python_default: False
initialize_by_default: False
write_condarc: TrueI was not aware that one could designate a local directory as a channel. This makes for a nice simplification in my construct.yaml. (It would be even nicer if I could set that channel as an argument to the constructor command). As far as I can tell, this change to the .yaml addresses the problem I was seeing before.
Checklist
What happened?
I have have been using conda constructor for a while to build a package that includes a conda package that is included from local storage rather than downloaded (see construct.yaml, below). The process has been working for me for a number of years, but recently I rebuilt the installer (for MacOS) using command
CONDA_SOLVER=classic constructor g2fulland got an installer (bash script) that fails, looking for that file under its original location:Here is the message again, but from
CONDA_VERBOSITY=2 bash /Volumes/SharedFolders/pi/misc/gsas2full-5773-MacOSX-x86_64.shIf I revert back to constructor=3.3, the created installer does work OK (but not when I tried constructor 3.6, 3.5 or 3.4 first; N.B. with 3.3 I can use command
constructor g2full). Once I have reverted, upgrading constructor back to 3.7 seems to leave things working. I need to do a fresh miniforge install to get back to the buggy constructor. Very perplexing.N.B. The package I am building is rather big and messy, but the conda build & constructor information is all in GitHub and I am happy to provide more details. I'm not so sure if I can come up with a smaller & cleaner example that fails.
Conda Info
Conda Config
Conda list
Additional Context
No response