Package Details: spack 1.1.0-4

Git Clone URL: https://aur.archlinux.org/spack.git (read-only, click to copy)
Package Base: spack
Description: A flexible package manager for supercomputer that supports multiple versions, configurations, platforms, and compilers.
Upstream URL: https://spack.io/
Licenses: MIT
Submitter: gdolle
Maintainer: 0xDoubleDoc
Last Packager: 0xDoubleDoc
Votes: 8
Popularity: 0.32
First Submitted: 2019-10-02 17:46 (UTC)
Last Updated: 2026-01-05 19:39 (UTC)

Latest Comments

1 2 3 Next › Last »

Nestor_013 commented on 2026-01-06 12:57 (UTC)

I'm expert even less than you in packaging :-) Not sure if root:root is enough or not. Since I'll have to restart from scratch anyway, I'll discover it experimentally during this stage. Thanks again for your reactivity.

0xDoubleDoc commented on 2026-01-06 12:24 (UTC) (edited on 2026-01-06 12:26 (UTC) by 0xDoubleDoc)

As far as I know (but I am not expert in packaging), chown can only be run in a post-install script, which is discouraged. Do we need all folders to belong to spack:spack? And all files? I do not use spack in a way that made it an issue on my side, but maybe you have some contrary examples? We can easily change permission of folders/files using the tmpfile.

Nestor_013 commented on 2026-01-06 12:19 (UTC)

Thanks. It compiles now and also installs. I know it's complicated but the sub-trees from /usr/lib/python3.13/site-packages/etc/spack/ still all belongs to root:root.

Any suggestion ?

0xDoubleDoc commented on 2026-01-05 19:38 (UTC)

Good catch. I have updated it! pre/post install scripts are not advised by Arch packaging guidelines for user creation, and instead advise sysusers / tmpfiles.

That this last version requires you to delete /usr/lib/python3.13/site-packages/etc before installation, else it will trigger the error

error: failed to commit transaction (conflicting files)
spack: /usr/lib/python3.13/site-packages/etc exists in filesystem

Nestor_013 commented on 2026-01-05 16:49 (UTC)

Hi, when trying to build the package in a clean environment, it fails at the end with a:

chown: invalid user: ‘spack:spack’

I guess this is due to the fact that my build environment has no spack UID and GID defined. Should this step not be performed in a post_install script, as well as the creation in a pre_install ?

Thanks.

snack commented on 2025-12-01 10:28 (UTC)

Yes I confirm it works as expected now, thank you!

0xDoubleDoc commented on 2025-12-01 10:13 (UTC)

It should be fixed now :).

0xDoubleDoc commented on 2025-12-01 09:41 (UTC)

Thanks, I am updating the package. This is indeed not the expected fix, it should use /opt/spack/environments (e.g. ${SPACK_ROOT}/environments), I am looking at why.

snack commented on 2025-11-30 10:06 (UTC) (edited on 2025-11-30 10:27 (UTC) by snack)

I just started to play with spack using the tutorial on readthedocs, and I got stuck at creating an environment:

$ spack env create testenv
==> Error: [Errno 13] Permission denied: '/usr/lib/python3.13/site-packages/var/spack/environments'

Does this mean that spack must be run in a vrtualenv? Or that my system is misconfigured?

Edit: same error in a virtualenv.

Edit2: I made it work by:

$ sudo mkdir /usr/lib/python3.13/site-packages/var/spack/environments
$ sudo chown spack:spack /usr/lib/python3.13/site-packages/var/spack/environments

but I'm not sure this is the proper way to fix this, so help is still much welcome.

Nestor_013 commented on 2025-07-25 08:00 (UTC)

Indeed, no error anymore. Thanks.

1 2 3 Next › Last »