...

• source /cds/sw/ds/ana/conda1/inst/etc/profile.d/conda.sh
• cd /cds/sw/ds/ana/conda1/manage/jenkins/
• conda env create -n ana-4.0.11 --file ana-env-py2.yaml
• conda env create -n ana-4.0.11-py3 --file ana-env-py3.yaml

...

New Pinned-Approach

Valerio writes: It's not different from the psana2 approach at all. All the feedstocks  First you need to package the source in a tar.gz like we always did, as shown in the "Checklist for building psana1 environments from feedstocks" section above.  The py2 and py3 psana recipes have now the pinning file in them. You just need to update the meta.yaml file, run "conda build recipe, " (did this as user "cpo") upload and build the environment from the "pinned" YAML file. (First you need to package the source in a tar.gz like we always did)

The py3 recipe is in https://github.com/slac-lcls/psana1-feedstock while the py2 recipe is in https://github.com/slac-lcls/psana1-py2-feedstock.

cpo thinks the psana1 recipes (both py2 and py3) need to be built with the python3 conda_build env from LCLS2 (source /cds/sw/ds/ana/conda2/manage/bin/psconda.sh).  If you don't do this I think we get this error from "conda build recipe/" since conda_build env in LCLS1 is py2.  built the recipes as user cpo.

TypeError: apply_pin_expressions() argument after ** must be a mapping, not unicode

The yaml files for creating the environment are in /cds/sw/ds/ana/conda1/manage/jenkins/.

cpo created the two env's like this:

source /reg/g/psdm/etc/psconda.sh -v2 (v2 to get experimental mamba solver)
conda env create --name ana-4.0.44-py3 --experimental-solver=libmamba --file=/cds/sw/ds/ana/conda1/manage/jenkins/ana-env-py3.yaml 
conda env create --name ana-4.0.44 --experimental-solver=libmamba --file=/cds/sw/ds/ana/conda1/manage/jenkins/ana-env-py2.yaml

LCLS2 Github Actions Approach (Deprecated)

...