Page History

...

Sometimes our precise pinned package versions disappear from conda-forge.  In the past when this happened Valerio was able to manually modify the above pinned yaml files to choose a nearby version.  This so far has not broken the fast conda-solver behavior.

New Pinnings

From time to time, an important package with big ramifications in the environment needs to be updated (e.g.: mypy). Or a general refresh of the packages in the environment. is needed. In these cases, new pinnings and new pinning files need to be created. This requires performing the following steps:

• In all feedstocks, replace conda_build_config.yaml with the version from: conda-forge-pinning-feedstock/conda_build_config.yaml at main · conda-forge/conda-forge-pinning-feedstock (github.com)
• Rebuild all feedstocks in the following order:
  • libnl
  • libnl3
  • rmda-core
  • libfabric
  • roentdek
  • amityping
  • cameralink-gateway
  • epix-100a-gen2
  • epix
  • lcls2-ephi-hr-pcie
  • lcls2-pgp-pcie-apps
  • lcls2_timetool
  • networkfox
  • prometheus-cpp
  • xtcdata
  • psalg
  • psana
  • psdaq
  • ami
  • psmon 
• Create new production and dev environment (see above)
• Create new conda_build_config.yaml using the script in the section above and copy it in every feedstock to create packages with pinned dependecies in the future