spack/lib/spack
Todd Gamblin 0458de18de bugfix: don't look up patches from packages for concrete specs
The concretizer can fail with `reuse:true` if a buildcache or installation contains a
package with a dependency that has been renamed or deleted in the main repo (e.g.,
`netcdf` was refactored to `netcdf-c`, `netcdf-fortran`, etc., but there are still
binary packages with dependencies called `netcdf`).

We should still be able to install things for which we are missing `package.py` files.

`Spec.inject_patches_variant()` was failing this requirement by attempting to look up
the package class for concrete specs.  This isn't needed -- we can skip it.

- [x] swap two conditions in `Spec.inject_patches_variant()`
2023-05-15 09:15:49 -07:00
..
docs concretizer: don't change concrete environments without --force (#37438) 2023-05-14 13:36:03 +02:00
env cc: deal with -Wl,-rpath= without value, deal with NAG (#37215) 2023-05-05 12:16:31 +02:00
external Update archspec to v0.2.1 (#37633) 2023-05-12 18:59:58 +02:00
llnl Add llnl.util.filesystem.find_first (#36083) 2023-03-27 09:42:16 -07:00
spack bugfix: don't look up patches from packages for concrete specs 2023-05-15 09:15:49 -07:00
spack_installable license year bump (#34921) 2023-01-18 14:30:17 -08:00