Singularity has been adopted by The Linux Foundation and has moved to and been renamed to Apptainer (see http://apptainer.org/ ), thus, new package versions should also reflect such (e.g., sys-cluster/apptainer). It appears that everything that was "singularity" has been renamed to be "apptainer" including SINGULARITY_* and SINGLUARITYENV_* environment variables which have become APPTAINER_* and APPTAINERENV_* respectively. As of this writing Apptainer is a release candidate (e.g., see https://github.com/apptainer/apptainer/releases ) but that will soon change no doubt. Thus, it appears sys-cluster/singularity should become sys-cluster/apptainer once a full release becomes available. Reproducible: Always
Thank you for the report! That said, having found out about this at the time of the last Singularity version bump I have already decided that between the version-number reset and all the internal renaming (upstream says there _will_ be compatibility symlinks, old variable names shall remain to be recognised and the configuration directory will be automatically migrated, that said I can see in RC2 notes that the compatibility layer might not in fact be complete yet) I would rather introduce sys-cluster/apptainer as a new package once 1.0.0 has been released, let the users adapt their workflows before making the switch and eventually last-rite sys-cluster/singularity, rather than rename the latter.
FYI Apptainer has released v1.0 ( https://github.com/apptainer/apptainer/releases/tag/v1.0.0 ) with a number of differences --so it looks like it best to have a new package name to keep things separate. :-)
