Skip to content

Fix: xl drop dawn/dawncut - #407

Open
SebastianPaucar wants to merge 2 commits into
masterfrom
fix/xl-drop-dawn-dawncut
Open

Fix: xl drop dawn/dawncut#407
SebastianPaucar wants to merge 2 commits into
masterfrom
fix/xl-drop-dawn-dawncut

Conversation

@SebastianPaucar

@SebastianPaucar SebastianPaucar commented Sep 1, 2026

Copy link
Copy Markdown

Briefly, what does this PR introduce? Please link to any relevant presentations or discussions.

This PR drops dawn and dawncut from xl/spack.yaml. No buildcache coverage and the URL source was broken. Look at this in https://github.com/eic/eic-spack/blob/develop/spack_repo/eic/packages/dawncut/package.py

    # dawn webpage not available anymore
    homepage = "https://geant4.kek.jp/~tanaka"
    url = "http://geant4.kek.jp/~tanaka/src/dawncut_1_54a.taz"
    maintainers = ["sly2j"]

This fixes fetch and SSL errors on build eic xl on * CI checks. With dawn and dawncut both removed from xl/spack.yaml, eic_xl now successfully concretized and built on amd64, amd64_v3, and arm64. Verified in #388. cc @wdconinc

What is the urgency of this PR?

  • High (please describe reason below)
  • Medium
  • Low

What kind of change does this PR introduce?

  • Bug fix (issue #__)
  • New feature (issue #__)
  • Optimization (issue #__)
  • Updated documentation
  • other: __

Please check if any of the following apply

  • This PR introduces breaking changes. Please describe changes users need to make below.
  • This PR changes default behavior. Please describe changes below.
  • AI was used in preparing this PR. Please describe usage below.

@wdconinc

wdconinc commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

Yeah, but we still use dawn in github.com/eic/epic...

@wdconinc

wdconinc commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

The source is supposed to be found in the new eic-spack-mirror repository, and that works with my local spack but somehow not in the container build. Can you see why? That would be preferred.

Other option is the project https://github.com/eic/dusk but that's not quite ready I fear.

@SebastianPaucar

Copy link
Copy Markdown
Author

The source is supposed to be found in the new eic-spack-mirror repository, and that works with my local spack but somehow not in the container build. Can you see why? That would be preferred.

Other option is the project https://github.com/eic/dusk but that's not quite ready I fear.

Digging into it. I will let you know.

@github-actions

github-actions Bot commented Sep 2, 2026

Copy link
Copy Markdown

Capybara summary for PR 407

@wdconinc

wdconinc commented Sep 4, 2026

Copy link
Copy Markdown
Contributor

So, when I run ./scripts/build-base.sh with the following diff:

diff --git a/containers/debian/Dockerfile b/containers/debian/Dockerfile
index 613f810e..eaafe8f2 100644
--- a/containers/debian/Dockerfile
+++ b/containers/debian/Dockerfile
@@ -358,6 +358,12 @@ git -C ${EICSPACK_ROOT} checkout ${EICSPACK_SHA:-${EICSPACK_VERSION}}
 spack repo add --scope spack "${EICSPACK_ROOT}/spack_repo/eic"
 EOF
 
+RUN --mount=type=cache,target=/var/cache/spack <<EOF
+set -e
+spack stage dawn
+spack stage dawncut
+EOF
+
 ## Workaround for Spack creating config files with limited permissions (see https://github.com/spack/spack/issues/52651)
 RUN chmod 644 ${SPACK_ROOT}/etc/spack/*.yaml ${HOME}/.spack/*.yaml

I get the following:

#27 [stage-0 16/18] RUN --mount=type=cache,target=/var/cache/spack <<EOF (set -e...)
#27 2.344 ==> Warning: The following issues were ignored while updating the indices of binary caches:
#27 2.344 FetchIndexError: Could not fetch manifest from https://ghcr.io/v2/eic/spack-v2026.06.0/manifests/index.spack, due to: GET https://ghcr.io/v2/eic/spack-v2026.06.0/manifests/index.spack returned 404: Not Found
#27 2.344 ==> Warning: the mirror at https://binaries.spack.io/v1.2.2 cannot be used in concretization (no index found)
#27 14.36 ==> Staged dawn in /tmp/root/spack-stage/spack-stage-dawn-3_91a-e36t4oaeg3z64ot3n5fg5zchyc4hxclb
#27 17.11 ==> Warning: The following issues were ignored while updating the indices of binary caches:
#27 17.11 FetchIndexError: Could not fetch manifest from https://ghcr.io/v2/eic/spack-v2026.06.0/manifests/index.spack, due to: GET https://ghcr.io/v2/eic/spack-v2026.06.0/manifests/index.spack returned 404: Not Found
#27 17.11 ==> Warning: the mirror at https://binaries.spack.io/v1.2.2 cannot be used in concretization (no index found)
#27 29.00 ==> Staged dawncut in /tmp/root/spack-stage/spack-stage-dawncut-1_54a-sqn7g6cafpkqerp22fssela3jszhtb4j
#27 DONE 29.5s

which seems to indicate the staging pulls correctly from the eic-spack-mirror source mirror (ignore the other warnings... different mirrors).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants