search

DUNE-DAQ / daq-release

Scripts and configuration files for the DUNE DAQ release
https://dune-daq-sw.readthedocs.io/en/latest/packages/daq-release/
2 stars 0 forks source link

Get consistent versions of `moo` between Spack and `dbt-pyvenv` #211

Closed jcfreeman2 closed 1 year ago

jcfreeman2 commented 2 years ago

Gordon Crone pointed out that his work area has moo version 0.5.7 rather than the desired 0.6.3 which we've specified in the ./configs/dunedaq-develop/dunedaq-develop.yaml file. Pengfei's noted that we still have py-moo 0.5.7 in Spack, and this is taking precedence over the dbt-pyvenv moo library. We should update ./spack-repos/externals/packages/py-moo/package.py so that it sets 0.6.3 rather than 0.5.7 as the version.

dingp commented 2 years ago

I did several things to fix the issue:

  1. updated package.py for py-moo with newer version 0.6.3;
  2. moved py-moo and its dependent python packages to the dunedaq section of release YAML, and specified the new version for py-moo, so py-moo 0.6.3 will be installed and used when building other daq packages;
  3. changed scripts/dbt-workarea-env.sh so the python lib in the local venv takes precedence over spack installed python modules (this is on thea/venv_setup branch, not on develop yet).
  4. changed scripts/dbt-setup-release.sh similarly.
dingp commented 2 years ago

The issue contains two parts:

a. new version of moo should have been used by spack when installing DAQ packages; b. local python modules in venv lib should have taken precedence over spack installed python packages.

So item 1 and 2 in the previous comment fixes a, and 3&4 fixes b.

dingp commented 2 years ago
image

The new nightly release NT22-11-09 built here showed correct moo version now.