Page History

...

• source /cds/sw/ds/ana/conda1/inst/etc/profile.d/conda.sh
• conda activate conda_build
• cd /cds/sw/ds/ana/conda1/manage/
• bin/ana-rel-admin --force --cmd psana-conda-src --name 4.0.53 --basedir `pwd`   (this command assembles all the source code from the tags into a .tar.gz file)

cp .tar.gz (from manage/downloads/anarel/) to where GitHub can see it:
/reg/g/psdm/web/swdoc/tutorials/

...

sha256sum /reg/g/psdm/web/swdoc/tutorials/psana-conda-4.0.10.tar.gz

The py2 and py3 psana recipes have now the pinning file (condathe 3 important files in the psana1-feedstock git repo are:  conda_build_config.yaml ) in them. You just need to update the meta.yaml file, run(specifies the versions of all package dependencies as recommended by condo) recipe/meta.yaml (specifies location of source code and psana build and run-time dependencies) recipe/build.sh (the actual scons build instructions).

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.  Use these commands:

source /cds/sw/ds/ana/conda2/manage/bin/psconda.sh
conda deactivate
conda activate conda_build

The py2 and py3 psana recipes have now the pinning file (conda_build_config.yaml) in them. You just need to update the meta.yaml file, run "conda build  "conda build recipe".  NOTE: need to do this above the recipe/ directory, to pick up the conda_build_config.yaml pinnings. (did this as user "cpo", but could also do as psreldev, although psreldev might need "anaconda login" as another user so "anaconda upload" will work) upload and build the environment from the "pinned" YAML file. 

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./psana1-feedstock while the py2 recipe is in https://github.com/slac-lcls/psana1-py2-feedstock.

Build the source code in the psana1-feedstock directory with the command 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.(effectively executes recipe/build.sh which has scons commands in it)

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

...