internlm/SWE-Fixer-Train-110K huggingface dataset:
Repository: spack/spack

Issue:
Incorrect checksum for CRTM fix files @ version 2.4.0_emc
### Steps to reproduce

```console
% cat spack/var/spack/repos/builtin/packages/crtm-fix/package.py 
[...]
class CrtmFix(Package):
    """CRTM coefficient files"""

    homepage = "https://github.com/NOAA-EMC/crtm"
    url = "ftp://ftp.ssec.wisc.edu/pub/s4/CRTM/fix_REL-2.3.0_emc.tgz"

    maintainers = [
        "BenjaminTJohnson",
        "edwardhartnett",
        "AlexanderRichert-NOAA",
        "Hang-Lei-NOAA",
        "climbfuji",
    ]

    version("2.4.0_emc", sha256="88d659ae5bc4434f7fafa232ff65b4c48442d2d1a25f8fc96078094fa572ac1a")
    version("2.3.0_emc", sha256="1452af2d1d11d57ef3c57b6b861646541e7042a9b0f3c230f9a82854d7e90924")
[...]

% spack checksum crtm-fix@2.4.0_emc
==> Found 1 version of crtm-fix:
  
  2.4.0_emc  ftp://ftp.ssec.wisc.edu/pub/s4/CRTM/fix_REL-2.4.0_emc.tgz

==> Fetching ftp://ftp.ssec.wisc.edu/pub/s4/CRTM/fix_REL-2.4.0_emc.tgz

    version("2.4.0_emc", sha256="d0f1b2ae2905457f4c3731746892aaa8f6b84ee0691f6228dfbe48917df1e85e")
```

### Error message

```console
==> Installing crtm-fix-2.4.0_emc-ftl3fxdnhmvw43lgf74lunrcms7dxmqf
==> No binary for crtm-fix-2.4.0_emc-ftl3fxdnhmvw43lgf74lunrcms7dxmqf found: installing from source
==> Fetching ftp://ftp.ssec.wisc.edu/pub/s4/CRTM/fix_REL-2.4.0_emc.tgz
==> Error: ChecksumError: sha256 checksum failed for /path/to/cache/build_stage/spack-stage-crtm-fix-2.4.0_emc-ftl3fxdnhmvw43lgf74lunrcms7dxmqf/fix_REL-2.4.0_emc.tgz
    Expected 88d659ae5bc4434f7fafa232ff65b4c48442d2d1a25f8fc96078094fa572ac1a but got d0f1b2ae2905457f4c3731746892aaa8f6b84ee0691f6228dfbe48917df1e85e
```

### Information on your system

% spack debug report
* **Spack:** 0.20.0.dev0
* **Python:** 3.9.15
* **Platform:** linux-rhel7-broadwell
* **Concretizer:** clingo

### General information

- [X] I have run `spack debug report` and reported the version of Spack/Python/Platform
- [X] I have searched the issues of this repo and believe this is not a duplicate
- [X] I have run the failing commands in debug mode and reported the output


Discussion:

Resolving patch:
diff --git a/var/spack/repos/builtin/packages/crtm-fix/package.py b/var/spack/repos/builtin/packages/crtm-fix/package.py
--- a/var/spack/repos/builtin/packages/crtm-fix/package.py
+++ b/var/spack/repos/builtin/packages/crtm-fix/package.py
@@ -18,7 +18,7 @@ class CrtmFix(Package):
         "BenjaminTJohnson", "edwardhartnett", "AlexanderRichert-NOAA", "Hang-Lei-NOAA", "climbfuji"
     )
 
-    version("2.4.0_emc", sha256="88d659ae5bc4434f7fafa232ff65b4c48442d2d1a25f8fc96078094fa572ac1a")
+    version("2.4.0_emc", sha256="d0f1b2ae2905457f4c3731746892aaa8f6b84ee0691f6228dfbe48917df1e85e")
     version("2.3.0_emc", sha256="1452af2d1d11d57ef3c57b6b861646541e7042a9b0f3c230f9a82854d7e90924")
 
     variant("big_endian", default=True, description="Install big_endian fix files")


Test patch:
Repository: spack/spack

Issue:
[containerize] Dockerfile should avoid shell var substitition
The following `spack.yaml` with definitions fails because of lines like `&&   echo "    - - $packages" \ ` in the Dockerfile.
```yaml
spack:
  definitions:
  - compilers: [gcc@10.2.0]
  - packages: [libelf]
  specs:
  - matrix:
    - [$packages]
    - [$%compilers]
  packages:
    all:
      target: [x86_64]
  container:
    format: docker
    images:
      os: centos:7
      spack: 0.16.1
  config:
    install_missing_compilers: true
```


Discussion:
Maybe escaping only the `$` signs is the way to go after all then.

Resolving patch:
diff --git a/lib/spack/spack/container/writers/docker.py b/lib/spack/spack/container/writers/docker.py
--- a/lib/spack/spack/container/writers/docker.py
+++ b/lib/spack/spack/container/writers/docker.py
@@ -2,6 +2,8 @@
 # Spack Project Developers. See the top-level COPYRIGHT file for details.
 #
 # SPDX-License-Identifier: (Apache-2.0 OR MIT)
+import shlex
+
 import spack.tengine as tengine
 
 from . import PathContext, writer
@@ -17,14 +19,15 @@ class DockerContext(PathContext):
     @tengine.context_property
     def manifest(self):
         manifest_str = super(DockerContext, self).manifest
-        # Docker doesn't support HEREDOC so we need to resort to
+        # Docker doesn't support HEREDOC, so we need to resort to
         # a horrible echo trick to have the manifest in the Dockerfile
         echoed_lines = []
         for idx, line in enumerate(manifest_str.split("\n")):
+            quoted_line = shlex.quote(line)
             if idx == 0:
-                echoed_lines.append('&&  (echo "' + line + '" \\')
+                echoed_lines.append("&&  (echo " + quoted_line + " \\")
                 continue
-            echoed_lines.append('&&   echo "' + line + '" \\')
+            echoed_lines.append("&&   echo " + quoted_line + " \\")
 
         echoed_lines[-1] = echoed_lines[-1].replace(" \\", ")")
 


Test patch:
diff --git a/lib/spack/spack/test/container/docker.py b/lib/spack/spack/test/container/docker.py
--- a/lib/spack/spack/test/container/docker.py
+++ b/lib/spack/spack/test/container/docker.py
@@ -2,6 +2,8 @@
 # Spack Project Developers. See the top-level COPYRIGHT file for details.
 #
 # SPDX-License-Identifier: (Apache-2.0 OR MIT)
+import re
+
 import pytest
 
 import spack.container.writers as writers
@@ -149,3 +151,14 @@ def test_not_stripping_all_symbols(minimal_configuration):
     content = writers.create(minimal_configuration)()
     assert "xargs strip" in content
     assert "xargs strip -s" not in content
+
+
+@pytest.mark.regression("22341")
+def test_using_single_quotes_in_dockerfiles(minimal_configuration):
+    """Tests that Dockerfiles written by Spack use single quotes in manifest, to avoid issues
+    with shell substitution. This may happen e.g. when users have "definitions:" they want to
+    expand in dockerfiles.
+    """
+    manifest_in_docker = writers.create(minimal_configuration).manifest
+    assert not re.search(r"echo\s*\"", manifest_in_docker, flags=re.MULTILINE)
+    assert re.search(r"echo\s*'", manifest_in_docker)
Repository: spack/spack

Issue:
Error messages due to spec syntax error in packages should refer to the offending package
### Steps to reproduce

```
spack --env-dir utils/spack/redshift concretize --force && spack --env-dir utils/spack/redshift install --fail-fast
```


### Error message

```
==> Error: Unexpected token: ':'
```

This error message is bad because it gives no context. It should say which file and which line contains the error. It should say what was being parsed when the error occurred, etc.

The error was caused by this line I wrote:
```
    patch('link_gtest.patch', when=':1.1.8')
```

I forgot the `@` character in front of the version number.


### Information on your system

Irrelevant.

I clicked the three buttons under "General information" although I didn't do any of these things.

### General information

- [X] I have run `spack debug report` and reported the version of Spack/Python/Platform
- [X] I have searched the issues of this repo and believe this is not a duplicate
- [X] I have run the failing commands in debug mode and reported the output


Discussion:

Resolving patch:
diff --git a/lib/spack/spack/repo.py b/lib/spack/spack/repo.py
--- a/lib/spack/spack/repo.py
+++ b/lib/spack/spack/repo.py
@@ -1240,6 +1240,9 @@ def get_pkg_class(self, pkg_name):
             module = importlib.import_module(fullname)
         except ImportError:
             raise UnknownPackageError(pkg_name)
+        except Exception as e:
+            msg = f"cannot load package '{pkg_name}' from the '{self.namespace}' repository: {e}"
+            raise RepoError(msg) from e
 
         cls = getattr(module, class_name)
         if not inspect.isclass(cls):


Test patch:
Repository: spack/spack

Issue:
Add ability to configure the default max_processes upper limit value without locally patching spack
### Summary

It would be useful on OLCF machines to be able to configure the max number of processes used to solve an environment.

Currently, spack chooses a maximum number of processing threads that is [the lesser of the number of specs to solve or 16](https://github.com/spack/spack/blob/develop/lib/spack/spack/environment/environment.py#L1211-L1214). On OLCF resource login nodes, our admins use cgroup rules to limit the amount of memory and process walltime any individual user can consume. When Spack defaults to using 16 process, it is often possible for the 16 clingo solver threads to consume more memory than is available to a user under cgroup limitations. This causes the solver threads to be violently killed and hangs spack in the concretization phase.

Rather than changing https://github.com/spack/spack/blob/develop/lib/spack/spack/environment/environment.py#L1211-L1214 to a lower fixed upper limit literal in our local forks of spack, I would propose that the max threads used when solving an environment adopt the same upper limit value as `spack.config.build_jobs`.  We generally already set `build_jobs` to a lower value than 16 (or even the available number of CPUs) to avoid exceeding cgroup memory limitations. However, a separate, new configuration value would also be acceptable for our purposes.

### Rationale

_No response_

### Description

_No response_

### Additional information

```
$ spack --version  
0.17.1-1474-ef75fe153b
```

Possibly related to:
- https://github.com/spack/spack/issues/27865
- https://github.com/spack/spack/issues/17598
- https://github.com/spack/spack/issues/11072

### General information

- [X] I have run `spack --version` and reported the version of Spack
- [X] I have searched the issues of this repo and believe this is not a duplicate


Discussion:

Resolving patch:
diff --git a/lib/spack/spack/cmd/concretize.py b/lib/spack/spack/cmd/concretize.py
--- a/lib/spack/spack/cmd/concretize.py
+++ b/lib/spack/spack/cmd/concretize.py
@@ -29,6 +29,7 @@ def setup_parser(subparser):
     )
 
     spack.cmd.common.arguments.add_concretizer_args(subparser)
+    spack.cmd.common.arguments.add_common_arguments(subparser, ["jobs"])
 
 
 def concretize(parser, args):
diff --git a/lib/spack/spack/environment/environment.py b/lib/spack/spack/environment/environment.py
--- a/lib/spack/spack/environment/environment.py
+++ b/lib/spack/spack/environment/environment.py
@@ -1475,7 +1475,10 @@ def _concretize_separately(self, tests=False):
 
         # Solve the environment in parallel on Linux
         start = time.time()
-        max_processes = min(len(arguments), 16)  # Number of specs  # Cap on 16 cores
+        max_processes = min(
+            len(arguments),  # Number of specs
+            spack.config.get("config:build_jobs"),  # Cap on build jobs
+        )
 
         # TODO: revisit this print as soon as darwin is parallel too
         msg = "Starting concretization"


Test patch:
Repository: spack/spack

Issue:
`spack find` cannot display non concrete compilers in root specs
### Steps to reproduce

```console
$ spack compiler list
==> Available compilers
-- clang ubuntu20.04-x86_64 -------------------------------------
clang@=12.0.0

-- gcc ubuntu20.04-x86_64 ---------------------------------------
gcc@=9.4.0
$ spack env activate --temp
$ spack add zlib %gcc@9.4.0
```

### Error message

```console
$ spack find
==> In environment /tmp/spack-i_w602w3
==> Root specs
==> Error: Spec is not concrete: gcc@9.4.0
```

### Information on your system

* **Spack:** 0.20.0.dev0 (4627438373732dff7ce269b1afe5390a9046dd1c)
* **Python:** 3.8.10
* **Platform:** linux-ubuntu20.04-icelake
* **Concretizer:** clingo


### General information

- [X] I have run `spack debug report` and reported the version of Spack/Python/Platform
- [X] I have searched the issues of this repo and believe this is not a duplicate
- [X] I have run the failing commands in debug mode and reported the output


Discussion:

Resolving patch:
diff --git a/lib/spack/spack/cmd/__init__.py b/lib/spack/spack/cmd/__init__.py
--- a/lib/spack/spack/cmd/__init__.py
+++ b/lib/spack/spack/cmd/__init__.py
@@ -347,7 +347,7 @@ def iter_groups(specs, indent, all_headers):
             spack.spec.architecture_color,
             architecture if architecture else "no arch",
             spack.spec.compiler_color,
-            f"{compiler.name}@{compiler.version}" if compiler else "no compiler",
+            f"{compiler}" if compiler else "no compiler",
         )
 
         # Sometimes we want to display specs that are not yet concretized.


Test patch:
diff --git a/lib/spack/spack/test/cmd/find.py b/lib/spack/spack/test/cmd/find.py
--- a/lib/spack/spack/test/cmd/find.py
+++ b/lib/spack/spack/test/cmd/find.py
@@ -357,3 +357,18 @@ def test_find_loaded(database, working_env):
     output = find("--loaded")
     expected = find()
     assert output == expected
+
+
+@pytest.mark.regression("37712")
+def test_environment_with_version_range_in_compiler_doesnt_fail(tmp_path):
+    """Tests that having an active environment with a root spec containing a compiler constrained
+    by a version range (i.e. @X.Y rather the single version than @=X.Y) doesn't result in an error
+    when invoking "spack find".
+    """
+    test_environment = ev.create_in_dir(tmp_path)
+    test_environment.add("zlib %gcc@12.1.0")
+    test_environment.write()
+
+    with test_environment:
+        output = find()
+    assert "zlib%gcc@12.1.0" in output
Repository: spack/spack

Issue:
Malformed version entry in microarchitectures.json
### Steps to reproduce

Install spack on neoverse_v1 system and try to install anythign using recent GCC. This will result in spack only building for neoverxse_n1:

spack solve reports:
```
%----------------------------------------------------------------------------
% Target compatibility
%----------------------------------------------------------------------------
compiler_supports_target(0,"neoverse_n1").
compiler_supports_target(0,"armv8.4a").
compiler_supports_target(0,"cortex_a72").
compiler_supports_target(0,"armv8.3a").
compiler_supports_target(0,"armv8.2a").
compiler_supports_target(0,"armv8.1a").
compiler_supports_target(0,"aarch64").
compiler_supports_target(0,"aarch64").
```


The issue comes from `def satisfies_constraint(entry, version):` in `microarchitectures.py`. 
It reads entries `"versions": "10.0"` in `microachitectures.json` wrong. It thinks this means min_version=10.0, max_version=<undefined> .

I checked: If I make the entry: `"versions": "10.0:10.0"` it works as expected.


So, the crux of the issue is `min_version, max_version = version.split(":")`.

### Error message

_No response_

### Information on your system

[ec2-user@ip-10-7-3-3 ~]$ spack debug report
* **Spack:** 0.21.0.dev0 (16e92794209a10588d70b62420059459d4aed334)
* **Python:** 3.7.16
* **Platform:** linux-amzn2-neoverse_v1
* **Concretizer:** clingo


### General information

- [X] I have run `spack debug report` and reported the version of Spack/Python/Platform
- [X] I have searched the issues of this repo and believe this is not a duplicate
- [X] I have run the failing commands in debug mode and reported the output


Discussion:

Resolving patch:
diff --git a/lib/spack/external/__init__.py b/lib/spack/external/__init__.py
--- a/lib/spack/external/__init__.py
+++ b/lib/spack/external/__init__.py
@@ -18,7 +18,7 @@
 
 * Homepage: https://pypi.python.org/pypi/archspec
 * Usage: Labeling, comparison and detection of microarchitectures
-* Version: 0.2.1 (commit 4b1f21802a23b536bbcce73d3c631a566b20e8bd)
+* Version: 0.2.1 (commit 9e1117bd8a2f0581bced161f2a2e8d6294d0300b)
 
 astunparse
 ----------------


Test patch:
Repository: spack/spack

Issue:
e4s ci: add hdf5-vol-daos
Add `hdf5-vol-daos` to E4S CI stacks

CC @hyoklee @wspear


Discussion:

Resolving patch:
diff --git a/var/spack/repos/builtin/packages/pmdk/package.py b/var/spack/repos/builtin/packages/pmdk/package.py
--- a/var/spack/repos/builtin/packages/pmdk/package.py
+++ b/var/spack/repos/builtin/packages/pmdk/package.py
@@ -37,6 +37,7 @@ class Pmdk(Package):
     variant("rpmem", default=False, description="Build remote persistent memory components")
 
     depends_on("cmake", when="@1.12.1:")
+    depends_on("pkgconfig", when="@1.12.1:")
     depends_on("ncurses", when="@1.6:")
     depends_on("libfabric", when="+rpmem")
     # documentation requires doxygen and a bunch of other dependencies


Test patch:
Repository: spack/spack

Issue:
e4s ci: add hdf5-vol-daos
Add `hdf5-vol-daos` to E4S CI stacks

CC @hyoklee @wspear


Discussion:

Resolving patch:
diff --git a/var/spack/repos/builtin/packages/protobuf-c/package.py b/var/spack/repos/builtin/packages/protobuf-c/package.py
--- a/var/spack/repos/builtin/packages/protobuf-c/package.py
+++ b/var/spack/repos/builtin/packages/protobuf-c/package.py
@@ -20,5 +20,5 @@ class ProtobufC(AutotoolsPackage):
     version("1.4.1", sha256="4cc4facd508172f3e0a4d3a8736225d472418aee35b4ad053384b137b220339f")
     version("1.3.2", sha256="53f251f14c597bdb087aecf0b63630f434d73f5a10fc1ac545073597535b9e74")
 
-    depends_on("protobuf")
+    depends_on("protobuf@:3.21.12")
     depends_on("pkgconfig", type="build")


Test patch:
Repository: spack/spack

Issue:
GSI-ncdiag: new version 1.1.0
### Summary

A new version of the GSI-ncdiag library was developed to support changes to the GSI, primarily a new subroutine that converts input doubles to singles and screens for `NaN` in the process.

### Rationale

This version of ncdiag helps to fix problems with the GSI wherein an attempt to convert double `NaN`s to singles cause `floating-invalid` errors and unpredictable behavior.

### Description

_No response_

### Additional information

_No response_

### General information

- [X] I have searched the issues of this repo and believe this is not a duplicate


Discussion:

Resolving patch:
diff --git a/var/spack/repos/builtin/packages/gsi-ncdiag/package.py b/var/spack/repos/builtin/packages/gsi-ncdiag/package.py
--- a/var/spack/repos/builtin/packages/gsi-ncdiag/package.py
+++ b/var/spack/repos/builtin/packages/gsi-ncdiag/package.py
@@ -10,10 +10,12 @@ class GsiNcdiag(CMakePackage):
     """GSI NetCDF Diagnostics Library and Utility Tools"""
 
     homepage = "https://github.com/NOAA-EMC/GSI-ncdiag"
-    url = "https://github.com/NOAA-EMC/GSI-ncdiag/archive/refs/tags/v1.0.0.tar.gz"
+    url = "https://github.com/NOAA-EMC/GSI-ncdiag/archive/refs/tags/v1.1.1.tar.gz"
 
     maintainers("ulmononian")
 
+    version("1.1.1", sha256="29ac8c22d2bbf11d5b437cbd53168aef99cdaa2c17d9a9c30b49fae4f7c6b1f2")
+    version("1.1.0", sha256="9195801301209d6f93890944d58ffee4e24a4e35502ab27560a8c440ee53df4c")
     version("1.0.0", sha256="7251d6139c2bc1580db5f7f019e10a4c73d188ddd52ccf21ecc9e39d50a6af51")
 
     variant("serial", default=True, description="Enable Serial NetCDF diagnostics")


Test patch:
Repository: spack/spack

Issue:
Revert "py-mypy: add 1.3.0"
Reverts spack/spack#38286

Checking if reverting this one fixes `develop` CI


Discussion:

Resolving patch:
diff --git a/lib/spack/spack/bootstrap/environment.py b/lib/spack/spack/bootstrap/environment.py
--- a/lib/spack/spack/bootstrap/environment.py
+++ b/lib/spack/spack/bootstrap/environment.py
@@ -175,12 +175,12 @@ def black_root_spec() -> str:
 
 def flake8_root_spec() -> str:
     """Return the root spec used to bootstrap flake8"""
-    return _root_spec("py-flake8")
+    return _root_spec("py-flake8@3.8.2:")
 
 
 def pytest_root_spec() -> str:
     """Return the root spec used to bootstrap flake8"""
-    return _root_spec("py-pytest")
+    return _root_spec("py-pytest@6.2.4:")
 
 
 def ensure_environment_dependencies() -> None:


Test patch:
Repository: spack/spack

Issue:
Bugfix/meson: fix _if_ninja_target_execute
Looks like `MesonBuilder` isn't referencing the package's implementation of `_if_ninja_target_execute`.  This PR should fix that.


Discussion:

Resolving patch:
diff --git a/lib/spack/spack/build_systems/meson.py b/lib/spack/spack/build_systems/meson.py
--- a/lib/spack/spack/build_systems/meson.py
+++ b/lib/spack/spack/build_systems/meson.py
@@ -209,5 +209,5 @@ def install(self, pkg, spec, prefix):
     def check(self):
         """Search Meson-generated files for the target ``test`` and run it if found."""
         with fs.working_dir(self.build_directory):
-            self._if_ninja_target_execute("test")
-            self._if_ninja_target_execute("check")
+            self.pkg._if_ninja_target_execute("test")
+            self.pkg._if_ninja_target_execute("check")


Test patch:
Repository: spack/spack

Issue:
Installation issue: py-mpi4py doesn't build with py-cython@3.0.0
### Steps to reproduce the issue

With a spack installation that has the recent py-cython@3.0.0:

```console
$ spack install py-mpi4py
```

@adamjstewart
@pradyunsg

### Error message

See spack-build-out.txt attached.

### Information on your system

* **Spack:** 0.21.0.dev0 (d996b4d2402cf8c2c0301fe75dd3e621d5ac7d3e)
* **Python:** 3.11.2
* **Platform:** linux-ubuntu23.04-aarch64
* **Concretizer:** clingo

### Additional information

[spack-build-out.txt](https://github.com/spack/spack/files/12094599/spack-build-out.txt)
[spack-build-env.txt](https://github.com/spack/spack/files/12094598/spack-build-env.txt)

### General information

- [X] I have run `spack debug report` and reported the version of Spack/Python/Platform
- [X] I have run `spack maintainers <name-of-the-package>` and **@mentioned** any maintainers
- [X] I have uploaded the build log and environment files
- [X] I have searched the issues of this repo and believe this is not a duplicate


Discussion:

Resolving patch:
diff --git a/var/spack/repos/builtin/packages/py-mpi4py/package.py b/var/spack/repos/builtin/packages/py-mpi4py/package.py
--- a/var/spack/repos/builtin/packages/py-mpi4py/package.py
+++ b/var/spack/repos/builtin/packages/py-mpi4py/package.py
@@ -36,6 +36,9 @@ class PyMpi4py(PythonPackage):
     depends_on("mpi")
     depends_on("py-cython@0.27.0:", type="build")
 
+    # https://github.com/mpi4py/mpi4py/pull/311
+    conflicts("^py-cython@3:")
+
     @when("@3.1:")
     def install_options(self, spec, prefix):
         return ["--mpicc=%s -shared" % spec["mpi"].mpicc]


Test patch:
Repository: spack/spack

Issue:
[SIRIUS] Update package
As a maintainer and developer of SIRIUS I would like to update and simplify the spack package for it. The following is changed
* versions below 6.0 are removed from the recipe. If needed they can be found in tagged release of spack
* versions below 7.3 are flagged as deprecated
* dependency on cmake>=3.23 is expicitely introduced
* propery set CMAKE_CUDA_ARCHITECTURES for cmake of SIRIUS

The build of SIRIUS is tested with this updates and is working (https://gitlab.com/cscs-ci/ci-testing/webhook-ci/mirrors/4931289112286619/3535154434359889/-/jobs/4949593897)


Discussion:
Ping @mtaillefumier and @simonpintarelli 
@mtaillefumier package audit for cp2k doesn't pass; but we discussed that cp2k of old needs also to be deprecated
I will fix this asap

Resolving patch:
diff --git a/var/spack/repos/builtin/packages/sirius/package.py b/var/spack/repos/builtin/packages/sirius/package.py
--- a/var/spack/repos/builtin/packages/sirius/package.py
+++ b/var/spack/repos/builtin/packages/sirius/package.py
@@ -342,8 +342,10 @@ def cmake_args(self):
                     )
 
                 # Make SIRIUS handle it
+                elif "@6:7.4.3" in spec:
+                    args.append(self.define("CMAKE_CUDA_ARCH", ";".join(cuda_arch)))
                 else:
-                    args.append(self.define("CUDA_ARCH", ";".join(cuda_arch)))
+                    args.append(self.define("CMAKE_CUDA_ARCHITECTURES", ";".join(cuda_arch)))
 
         if "+rocm" in spec:
             archs = ",".join(self.spec.variants["amdgpu_target"].value)


Test patch: