Small change in EESSI-extend comment to allow redeployment on RISC-V

[bedroge]

The settings in the EESSI-extend module of the RISC-V repo are outdated, because it was never rebuilt after the initial installation. This leads to issues with for instance the CPP search path. Fixing it by forcing a redeploy here. In the future we should just always rebuild it for the RISC-V repo too.

[bedroge]

bot: build repo:dev.eessi.io-riscv-2025.06-001 instance:eessi-bot-riscv for:arch=riscv64/generic

[riscv-eessi-io-bot]

New job on instance eessi-bot-riscv for repository dev.eessi.io-riscv-2025.06-001
Building on: generic
Building for: riscv64/generic
Job dir: /home/eessibot/shared/jobs/2026.05/pr_240/309501

date	job status	comment
May 29 11:13:19 UTC 2026	submitted	job id 309501 awaits release by job manager
May 29 11:14:13 UTC 2026	released	job awaits launch by Slurm scheduler
May 29 11:15:22 UTC 2026	running	job 309501 is running
May 29 11:20:59 UTC 2026	finished	😁 SUCCESS (click triangle for details) Details ✅ job output file slurm-309501.out ✅ no message matching FATAL: ✅ no message matching ERROR: ✅ no message matching FAILED: ✅ no message matching required modules missing: ✅ found message(s) matching No missing installations ✅ found message matching .tar.* created! Artefacts eessi-2025.06-software-linux-riscv64-generic-layer-1780053555.tar.zst size: 0 MiB (22 bytes) entries: 0 modules under 2025.06-001/software/linux/riscv64/generic/modules/all no module files in tarball software under 2025.06-001/software/linux/riscv64/generic/software no software packages in tarball reprod directories under 2025.06-001/software/linux/riscv64/generic/reprod no reprod directories in tarball other under 2025.06-001/software/linux/riscv64/generic no other files in tarball
May 29 11:20:59 UTC 2026	test result	🤷 UNKNOWN (click triangle for detailed information) Job test file _bot_job309501.test does not exist in job directory, or parsing it failed.

[ocaisa]

LGTM

[ocaisa]

@bedroge tarball is entirely empty, not sure why...

[bedroge]

Hmm, the build went fine:

== COMPLETED: Installation ended successfully (took 10 secs)
== Results of the build can be found in the log file(s) 
/cvmfs/dev.eessi.io/riscv/versions/2025.06-001/software/linux/riscv64/generic/software/EESSI-extend/2025.06-easybuild/easybuild/easybuild-EESSI-extend-2025.06-20260529.131835.log
== Build succeeded for 1 out of 1 (total: 10 secs)
== Summary:
   * [SUCCESS] EESSI-extend/2025.06-easybuild

But create_tarball.sh is looking for installations in a weird location:

This EESSI production version only provides a RISC-V compatibility layer,
software installations are provided by the EESSI development repository at /cvmfs/dev.eessi.io/layer.
done
>> Collecting list of files/directories to include in tarball via /tmp/dev.eessi.io/overlay-upper/layer/versions...
done

Not sure how that 'layer` ended up there...

[bedroge]

Hmm, okay, figured it out: the dev build bots set the dev project based on the repo entry in the metadata file, and for builds triggered from software-layer-scripts it's:

repo = EESSI/software-layer-scripts

(for regular builds it's e.g. dev.eessi.io-riscv)

It then sets the dev project name like this: https://github.com/EESSI/dev.eessi.io-scripts/blob/main/bot/bot-build-dev.eessi.io.slurm#L54C1-L54C63
That results in layer.

Doing a rebuild from the RISC-V github repo didn't work either (see EESSI/dev.eessi.io-riscv#124).