Skip to content

Conversation

@cyrush
Copy link
Member

@cyrush cyrush commented Jul 7, 2025

spack configs created with post 1.0 spack will undermine bootstrap of older spack (0.23.0) - here is an example of the error message you get:

[exe: /Users/harrison37/Work/github/llnl/conduit/_jhhh/spack/bin/spack -D /Users/harrison37/Work/github/llnl/conduit/_jhhh/spack_env concretize --fresh ]
==> Error: a single spec was requested, but parsed more than one:
[email protected] languages:=fortran
          ^^^^^^^^^^^^^^^^^^^

Note the := syntax is newer then spack 0.23.0

This adds -b to the our clean command, to re-bootstrap and avoid config issues from undermining builds.

Co-authored-by: Chris White <[email protected]>
@cyrush
Copy link
Member Author

cyrush commented Jul 7, 2025

This also works w/o using clean --bootstrap thoughts?

        # set bootstrap location in dest dir
        bstrp_cmd = "{0} bootstrap root --scope=site {1}".format(self.spack_exe(use_spack_env=False),
                                                                 pjoin(self.dest_dir,"spack_bootstrap"))
        res = sexe(bstrp_cmd, echo=True)

@becker33
Copy link
Member

becker33 commented Jul 9, 2025

I think @cyrush 's suggestion is probably better -- you could still technically create a situation that required cleaning the bootstrap, but by far the most likely reason is two different versions of Spack trying to use the same bootstrap store.

@white238
Copy link
Member

white238 commented Jul 9, 2025

We might hit a parallelism problem cleaning out the bootstrapping... I think the changing the bootstrap location is probably better.

@cyrush
Copy link
Member Author

cyrush commented Jul 9, 2025

Sounds good, I'll get this in soon.

I am already using it on a branch so I am confident it helps.

@cyrush
Copy link
Member Author

cyrush commented Jul 9, 2025

spoke too soon ... hitting a new error

@cyrush
Copy link
Member Author

cyrush commented Jul 9, 2025

[exe: /Users/harrison37/Work/github/alpine-dav/ascent_co3/ascent/uberenv_libs/spack/bin/spack bootstrap status]
Spack v0.23.1 - [email protected]

[PASS] Core Functionalities

[FAIL] Binary packages
  [B] MISSING "gpg2": required to sign/verify buildcaches



@cyrush
Copy link
Member Author

cyrush commented Jul 9, 2025

bootstrap dir isn't enough, spack user cache dir needs to be controlled via SPACK_USER_CACHE_PATH, or hacked out.

In my test branch, I am updating the spack source to hard code the user cache path to be in a spack_cache dir under dest dir.
I think this actually may also solve the bootstrap issue, but I am not confident -- so I am keeping the bootstrap path set command in.

@cyrush
Copy link
Member Author

cyrush commented Jul 9, 2025

the other issue I had:

spack bootstrap now

fails to fully bootstrap

[exe: /Users/harrison37/Work/github/alpine-dav/ascent_co3/ascent/uberenv_libs/spack/bin/spack bootstrap status]
Spack v0.23.1 - [email protected]

[PASS] Core Functionalities

[FAIL] Binary packages
  [B] MISSING "gpg2": required to sign/verify buildcaches

It says that [B] things will be fixed by spack, but the command still fails and causes uberenv to exit.

But if I skip setting up clingo all together, things work.
~/.spack does not exist on my machine as a directory, so I don't think clingo can be hiding there.

Based on this, it seems that the install process will get clingo setup.

All of this said, there could be more surprises in the sprawl.

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.

4 participants