jedi-base-env and bufrquery: why is it off? (for me?)

[mathomp4]

This is an odd one, and I've already pinged @climbfuji on Slack but maybe others here know (@srherbener ?)

Namely, @Dooruk asked about a new bufr-query and I asked EMC and they released 0.0.5. Nice. (And see #1875 for here) So then, I thought, well, I could install it at NAS (at least) for him to test (and then maybe @ashley314 at NCCS after that). But, huh, I had no bufr-query at NAS. This surprised me because jedi-base-env has:

spack-stack/repos/spack_stack/spack_repo/spack_stack/packages/jedi_base_env/package.py

Line 24 in 7b253ba

variant("bufrquery", default=True, description="Build bufr-query library")

and the only other reference I see to the bufrquery variant is in the aws-ubuntu2404 readme where it is turned off.

But, I look in my concretize logs and:

 -   2mbf7p6      ^jedi-base-env@1.0.0~bufrquery+fftw+hdf4 build_system=bundle arch=linux-rhel8-x86_64_v3

So I'm just wondering: How is this happening. I'm sure there's a reason, but I can't see why. The default is True and I see nothing in my setup asking it for ~bufrquery.

[climbfuji]

Seems like a concretizer bug. Please remove the variant and make it a hard dependency, that works for me.

[mathomp4]

Seems like a concretizer bug. Please remove the variant and make it a hard dependency, that works for me.

Okay. I'll give that a shot...once my current "rebuild the whole oneapi stack at NAS because things looked slightly wrong" is done. :)

ETA: For @mathomp4 if you come across this one day: Do everything on afe nodes. Just avoid pfe.