Paul Ferrell
Paul Ferrell
Much better. I am getting this error though: ``` lib/spack/spack/error.py:54 ==> [2022-08-09-06:33:20.936530] Error: Package 'base' not found. Traceback (most recent call last): File "/storage/spack/spack/lib/spack/spack/repo.py", line 1306, in get_pkg_class module =...
Ok, I think this one's a winner. After a couple minutes we're already up to the letter 'G' without any issues.
I was checking on a different problem (more on that later) and ran into this when mirroring a single package: I was running `spack --debug mirror create -n all gromacs`...
The other problem I ran into is throttling from gitlab.com. I think it will be fine over multiple runs, as the packages that got missed should just get picked up...
Do we really have to concretize all these specs? The computational load is huge. Even with a 10x speedup, we're looking at hours and hours to do this.
The big question for me is: Are there any patches, sources, etc that would need to be pulled down that they aren't available from the class (or an instance of...
Accidentally closed it...
Not currently, but I can make that true. Some of my recent changes have made it possible at least.
Here's the problem. When we provide Spack built packages via Spack created modulefiles with 'autoload: direct' (or anything other than autoload: none) - it works pretty well. That is, until...
Oh, and the `extends(python)` bit - we have to disable that for any package we build multiple versions of. It causes view conflicts (for obvious reasons). I'd like to be...