The singularity-ce incompatible upgrade has now been pushed to stable.
This is the final announcement prescribed by the EPEL Incompatible Upgrades Policy:
Cheers,
DT
On 9 Feb 2024, at 10:45, David Trudgian <dtrudg(a)sylabs.io> wrote:
After approval in the last EPEL meeting [1], I have submitted an incompatible upgrade of
singularity-ce to testing for EPEL 7, 8 & 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-cbd86d2020
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-f299fbc570
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-05e20edbbf
These updates upgrade singularity-ce from v3.11.5 to v4.1.1.
The following incompatibilities should be noted by users:
1) Some functionality previously provided by the `singularity remote` command is split
into new `singularity registry` and `singularity keyserver` commands.
2) The `singularity remote add` command now sets a newly added remote as the default
(unless suppressed). Previously the user had to set the default remote manually.
3) The deprecated and unmaintained `—vm` flag to start singularity inside a Virtual
Machine has been removed.
4) Bind mounts are now performed in the order in which they are specified. Previously,
image based bind mounts were performed before others.
5) Current working directory on the host is now created in the container, restoring a
behaviour from Singularity <3.6.0 unless suppressed.
6) If the current directory paths on the container and host contains symlinks to
different locations, the current working directory is not mounted.
Changes 1,2,3 are expected to have minimal impact, and 4,5,6 are likely to be considered
bug fixes by many users.
No changes are required to existing configuration files for this update.
A complete description of changes and additions between v3.11 and v4.1.1 is available in
the upstream documentation at
https://sylabs.io/docs/
In the absence of any issues, the updates will be pushed to stable after a one week
testing period has passed, with a follow-up notification here.
Cheers,
David Trudgian
[1]
https://pagure.io/epel/issue/265#comment-894790
--
_______________________________________________
epel-announce mailing list -- epel-announce(a)lists.fedoraproject.org
To unsubscribe send an email to epel-announce-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/epel-announce@lists.fedorap...
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue