1596535 : Installing rpm packages on Maxwell

Created: 2026-04-28T09:55:50Z - current status: new

Here’s the anonymized and summarized version of your query:

Summary of the Issue

A user is currently transferring software tarballs to /software on the Maxwell cluster and has packaged their software as RPMs. They are inquiring about: 1. Whether RPM packages can be installed on Maxwell, given that RPM installations typically require root privileges. 2. If there are RPM packaging guidelines for Maxwell, such as defined installation prefixes for executables, libraries, documentation, and licenses. 3. Whether the RPM database is visible across all nodes and if dnf install can be used from the max-display node.

Possible Solutions & Next Steps

Based on the provided context about the Maxwell cluster and its software management tools (e.g., Spack), here are some considerations:

1. RPM Installation on Maxwell

  • Root Privileges: RPM installations typically require root access, which is not available to regular users on Maxwell. The cluster is designed for user-managed software installations in personal or group directories (e.g., /home, /group, /scratch).
  • Alternative: Instead of RPMs, consider:
  • Spack (recommended for Maxwell): A package manager that allows users to install software in their own directories without root privileges. See Spack documentation for Maxwell.
  • Manual Installation: Extract tarballs into a user-owned directory (e.g., /home/[USERNAME]/software) and manage dependencies manually.

2. RPM Packaging Guidelines for Maxwell

  • There are no official RPM packaging guidelines for Maxwell, as RPMs are not the standard method for software deployment on the cluster.
  • If RPMs are required, they should be relocated to a user-owned directory (e.g., /home/[USERNAME]/rpmbuild) and installed with --prefix to avoid conflicts with system paths. Example: bash rpm --relocate /usr=/home/[USERNAME]/software -ivh package.rpm
  • Best Practice: Use Spack or modulefiles to manage software versions and dependencies.

3. RPM Database & dnf install on max-display

  • The RPM database is not globally visible across all nodes, as Maxwell is a shared cluster with distributed file systems.
  • dnf install (or yum) cannot be used on max-display or compute nodes, as these tools require root access and are not configured for user-level package management.
  • Workaround: If RPMs are necessary, install them in a local directory (e.g., /home/[USERNAME]/rpmdb) and manage them manually.
  1. Use Spack for software installation (preferred method on Maxwell).
  2. Example: bash source /software/spack/activate_spack.sh spack install [PACKAGE]
  3. If RPMs are unavoidable:
  4. Install them in a user-owned directory (e.g., /home/[USERNAME]/software).
  5. Use --prefix or --relocate to avoid system paths.

  6. Manage dependencies manually or via Spack.

  7. Avoid dnf/yum on Maxwell, as they require root privileges and are not supported.

Sources Used