Created attachment 589688 [details] new ebuild The singularity ebuild hasn't been updated in over a year. I made my own updated version, and test it on my machine, and it seems to work. It has the following bug fixes over the previous ebuild: - it actually works with the newer versions of singularity that are written mostly in Go and no-longer use autotools - the /var directories are now preserved in the package (see also #692836) - the package now warns when you are missing the required SQUASHFS kernel option - a variety of dependencies that are required for version 3.4 are added (some of which were needed for 2.6.1, but I didn't bother to test which)
Having an updated singularity package is now critical, because "singularity exec" from version 2.6.2 has problems mounting squashfs layers with last kernel versions: https://bugzilla.redhat.com/show_bug.cgi?id=1781863 https://lkml.org/lkml/2019/12/10/1780
Created attachment 614610 [details] sys-cluster/singularity-3.5.3.ebuild I have taken Robert's ebuild, and I have tweaked it in order to support Singularity 3.5.3
I was about to invoke maintainer time-out and have this added but unfortunately, there are some issues to address in the ebuild. Most of the clean-up is simple enough but I would very much clarify why there is dev-python in DEPEND. Is it really necessary, seeing as there seem to be no build-time invocations of python in 3.5.3 source code? If it IS necessary, the ebuild should use python-any-r1.eclass instead. Come to think of it, some other dependencies - wget for instance - look suspicious as well and I would appreciate if you could help verify them, as it will save me the trouble of manually testing all of this on a minimal build image.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e5faf5a00819f65078cbd18aa6c51f8ddfed55fa commit e5faf5a00819f65078cbd18aa6c51f8ddfed55fa Author: Marek Szuba <marecki@gentoo.org> AuthorDate: 2020-04-16 16:08:40 +0000 Commit: Marek Szuba <marecki@gentoo.org> CommitDate: 2020-04-16 16:35:23 +0000 sys-cluster/singularity: bump to 3.5.3 Invoking maintainer time-out on this one, on the one hand we have been LONG overdue for a bump to major version 3 and on the other 2.6.2 has apparently got problems with squashfs on newer kernels. Discussion of dependencies, given some of them are not obvious and official "install from source" documentation seems to include packages which are not in fact needed: - sys-libs/libseccomp - looked for by mconfig, moreover at least on my system singularity binaries end up linked *dynamically* against it; - virtual/pkgconfig - used by mconfig while looking for libseccomp; - go-1.13+ - this version number is requested in mconfig; - app-crypt/gpgme - NOT looked for by mconfig but Singularity does use gpgme bindings for Go; - dev-libs/openssl - looked for by mconfig; - sys-apps/util-linux - libuuid and its header files looked for by mconfig; - sys-fs/cryptsetup - looked for by mconfig; - sys-fs/squashfs-tools - various tools from this package (e.g. unsquash) are invoked at run time, that said I have experimentally confirmed that Singularity builds fine without it. Closes: https://bugs.gentoo.org/694048 Signed-off-by: Marek Szuba <marecki@gentoo.org> sys-cluster/singularity/Manifest | 1 + sys-cluster/singularity/metadata.xml | 6 ++- sys-cluster/singularity/singularity-3.5.3.ebuild | 59 ++++++++++++++++++++++++ 3 files changed, 65 insertions(+), 1 deletion(-)
