Description
With py-pybind11-stubgen available in our nightly, if a package is set up to generate stubs (see, e.g., DUNE-DAQ/conffwk#34 for what I'm talking about) then not only should building it in a work area create *.pyi files but building it in Spack should as well. However, this is not the case (e.g., there are no *.pyi files in /cvmfs/dunedaq-development.opensciencegrid.org/nightly/MYPYB_DEV_260723_A9/spack-0.22.0/opt/spack/linux-almalinux9-x86_64/gcc-14.3.0/conffwk-MYPYB_DEV_260723_A9-ji6smf2jmoloisi53uml5x6oykhmuwst, from today's https://github.com/DUNE-DAQ/daq-release/actions/runs/30020002034 MYPYFD_DEV_260723_A9 test build)
Steps to reproduce
Create a test nightly using v3.3.1 of daq-cmake and defaulting to the PawelPlesniak/Mypy branches where available.
Version and environment
N/A
Impact
Small/Isolated
Anything else?
No response
Description
With
py-pybind11-stubgenavailable in our nightly, if a package is set up to generate stubs (see, e.g., DUNE-DAQ/conffwk#34 for what I'm talking about) then not only should building it in a work area create*.pyifiles but building it in Spack should as well. However, this is not the case (e.g., there are no*.pyifiles in/cvmfs/dunedaq-development.opensciencegrid.org/nightly/MYPYB_DEV_260723_A9/spack-0.22.0/opt/spack/linux-almalinux9-x86_64/gcc-14.3.0/conffwk-MYPYB_DEV_260723_A9-ji6smf2jmoloisi53uml5x6oykhmuwst, from today's https://github.com/DUNE-DAQ/daq-release/actions/runs/30020002034MYPYFD_DEV_260723_A9test build)Steps to reproduce
Create a test nightly using
v3.3.1ofdaq-cmakeand defaulting to thePawelPlesniak/Mypybranches where available.Version and environment
N/A
Impact
Small/Isolated
Anything else?
No response