Less restrictive target for gh

[anton-seaice]

Contibutes to #15

---

🚀 The latest prerelease pinentry/pr17-5 at a19608f is here: #17 (comment) 🚀

---

🚀 The latest prerelease gh/pr17-8 at aa771b0 is here: #17 (comment) 🚀

[github-actions]

🚀 Attempted to deploy gh Prerelease pr17-1 with commit 50c22df

🖥️ Gadi Deployment ❌

[anton-seaice]

!redeploy

[github-actions]

🚀 Attempted to deploy gh Prerelease pr17-2 with commit 50c22df

🖥️ Gadi Deployment ❌

[anton-seaice]

This works on normalbw now:

Singularity> module use /g/data/vk83/prerelease/modules
Singularity> module load gh/pr17-2
Singularity> gh
Work seamlessly with GitHub from the command line.

USAGE
  gh <command> <subcommand> [flags]

CORE COMMANDS
...

[github-actions]

The model version in the ncdu/spack.yaml has not been updated.
You can update it manually.
Alternatively, comment the following to have it updated and committed automatically:

• !bump major for feature releases
• !bump minor for bugfixes

[github-actions]

🚀 Attempted to deploy ncdu Prerelease pr17-3 with commit a19608f

🖥️ Gadi Deployment ❌

[github-actions]

The model version in the openssh/spack.yaml has not been updated.
You can update it manually.
Alternatively, comment the following to have it updated and committed automatically:

• !bump major for feature releases
• !bump minor for bugfixes

[github-actions]

🚀 Attempted to deploy openssh Prerelease pr17-4 with commit a19608f

🖥️ Gadi Deployment ❌

[github-actions]

The model version in the pinentry/spack.yaml has not been updated.
You can update it manually.
Alternatively, comment the following to have it updated and committed automatically:

• !bump major for feature releases
• !bump minor for bugfixes

[anton-seaice]

!bump minor

[github-actions]

🚀 Attempted to deploy pinentry Prerelease pr17-4 with commit a19608f

🖥️ Gadi Deployment ❌

[aidanheerdegen]

Not sure the bump commands work in this repo, is that correct @CodeGat?

Can we re-deploy the same versions with a different target @CodeGat?

[github-actions]

🚀 Attempted to deploy ncdu Prerelease pr17-3 with commit a19608f

🖥️ Gadi Deployment ✔️

Usage Instructions

ncdu, defined in ncdu/spack.yaml, will be deployed to Gadi as:

• 1.19 as a Release (when merged).
• pr17-3 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load ncdu/pr17-3

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the ncdu-pr17-3 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

• access-nri/spack on branch 0.22
• access-nri/spack-packages version 2025.06.001
• access-nri/spack-config version 2025.08.000

If the above was not what was expected, commit changes to config/versions.json in this PR.

[CodeGat]

Not sure the bump commands work in this repo, is that correct?

!bump doesn't work with this repo, no. Haven't got around to making it work yet. Manual updates of the version only.

Can we re-deploy the same versions with a different target?

Hmm. I think the spack environment names would clash, unfortunately. Maybe it's worth doing a small version update with these...?

[github-actions]

🚀 Attempted to deploy openssh Prerelease pr17-4 with commit a19608f

🖥️ Gadi Deployment ✔️

Usage Instructions

openssh, defined in openssh/spack.yaml, will be deployed to Gadi as:

• 9.8p1 as a Release (when merged).
• pr17-4 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load openssh/pr17-4

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the openssh-pr17-4 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

• access-nri/spack on branch 0.22
• access-nri/spack-packages version 2025.06.001
• access-nri/spack-config version 2025.08.000

If the above was not what was expected, commit changes to config/versions.json in this PR.

[github-actions]

🚀 Attempted to deploy pinentry Prerelease pr17-5 with commit a19608f

🖥️ Gadi Deployment ✔️

Usage Instructions

pinentry, defined in pinentry/spack.yaml, will be deployed to Gadi as:

• 1.3.0 as a Release (when merged).
• pr17-5 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load pinentry/pr17-5

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the pinentry-pr17-5 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

• access-nri/spack on branch 0.22
• access-nri/spack-packages version 2025.06.001
• access-nri/spack-config version 2025.08.000

If the above was not what was expected, commit changes to config/versions.json in this PR.

[aidanheerdegen]

Maybe it's worth doing a small version update with these...?

As we're still in spack/0.22 there aren't newer versions available for these packages:

https://github.com/ACCESS-NRI/spack/blob/releases/v0.22/var/spack/repos/builtin/packages/gh/package.py#L19

https://github.com/ACCESS-NRI/spack/blob/releases/v0.22/var/spack/repos/builtin/packages/ncdu/package.py#L22

https://github.com/ACCESS-NRI/spack/blob/releases/v0.22/var/spack/repos/builtin/packages/openssh/package.py#L28

https://github.com/ACCESS-NRI/spack/blob/releases/v0.22/var/spack/repos/builtin/packages/pinentry/package.py#L25

[anton-seaice]

We can change the module projections (e.g. append -1 to them) but I don't think that will change the environment names (which must be set by CI ?)

[CodeGat]

Correct, environments are set statically in the CI. This problem won't be the case once we move to build-ci v8 - see ACCESS-NRI/build-cd#332. I expect that to be finished off early next year.
Essentially when we decouple the deployment version from the spec version, you will be able to deploy the same version of the package, just with a different deployment version, if that makes sense. It would look something like: https://github.com/ACCESS-NRI/system-tools/pull/16/files#diff-9c1184741666c054c0455bffdb3e18f2dc7298574e26dabf63b80c1d92ca851b, and would allow something like:

spack:
  definitions:
  - _name: [gh]
  - _version: [2.43.1-1]  # Note the extra `-1`
  specs:
  - gh@2.43.1

[anton-seaice]

Thanks - what can we do in the interim. This fixes a kind of annoying bug in our recomended way of authenticating to git

[aidanheerdegen]

I've a PR to update the spack instance to enable newer versions of gh

ACCESS-NRI/spack#23

As noted in that PR

Looked into updating some of the other SPRs referenced in the PR above, but ncdu had no updates, openssh had already been updated, and pinentry seemed kinda niche, so didn't do anything with that.

So @anton-seaice, once we have the PR above merged can you remove pinentry and ncdu from the PR, bump the versions of gh to 2.49.2 and openssh to 9.9p1, and we should be good to go.

[CodeGat]

The instances of spack have been updated to include the new versions of gh 👍

[github-actions]

🚀 Attempted to deploy gh Prerelease pr17-6 with commit 8639943

🖥️ Gadi Deployment ✔️

Usage Instructions

gh, defined in gh/spack.yaml, will be deployed to Gadi as:

• 2.49.2 as a Release (when merged).
• pr17-6 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load gh/pr17-6

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the gh-pr17-6 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

• access-nri/spack on branch 0.22
• access-nri/spack-packages version 2025.06.001
• access-nri/spack-config version 2025.08.000

If the above was not what was expected, commit changes to config/versions.json in this PR.

[github-actions]

The model version in the ncdu/spack.yaml has not been updated.
You can update it manually.
Alternatively, comment the following to have it updated and committed automatically:

• !bump major for feature releases
• !bump minor for bugfixes

[github-actions]

🚀 Attempted to deploy ncdu Prerelease pr17-7 with commit 8639943

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy openssh Prerelease pr17-7 with commit 8639943

🖥️ Gadi Deployment ✔️

Usage Instructions

openssh, defined in openssh/spack.yaml, will be deployed to Gadi as:

• 9.9p1 as a Release (when merged).
• pr17-7 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load openssh/pr17-7

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the openssh-pr17-7 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

• access-nri/spack on branch 0.22
• access-nri/spack-packages version 2025.06.001
• access-nri/spack-config version 2025.08.000

If the above was not what was expected, commit changes to config/versions.json in this PR.

[github-actions]

The model version in the pinentry/spack.yaml has not been updated.
You can update it manually.
Alternatively, comment the following to have it updated and committed automatically:

• !bump major for feature releases
• !bump minor for bugfixes

[github-actions]

🚀 Attempted to deploy pinentry Prerelease pr17-8 with commit 8639943

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy gh Prerelease pr17-8 with commit aa771b0

🖥️ Gadi Deployment ✔️

Usage Instructions

gh, defined in gh/spack.yaml, will be deployed to Gadi as:

• 2.49.2 as a Release (when merged).
• pr17-8 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load gh/pr17-8

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the gh-pr17-8 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

• access-nri/spack on branch 0.22
• access-nri/spack-packages version 2025.06.001
• access-nri/spack-config version 2025.08.000

If the above was not what was expected, commit changes to config/versions.json in this PR.

[anton-seaice]

I think this is ready @aidanheerdegen

[CodeGat]

I'm no Aidan, but I think this looks good

[aidanheerdegen]

Please squash and merge @anton-seaice.