On Thu, 18 Aug 2016, Aaron M. Ucko wrote: > Source: singularity-container > Version: 2.1.2-1 > Severity: important > Justification: fails to build from source
> Builds of singularity-container for architectures other than x86 Linux > have been failing at the configuration stage. The non-Linux builds > complain that various CLONE_* flags, most crucially CLONE_NEWNS, are > unavailable; I presume these platforms are a lost cause. As for Linux > on non-x86, the build system complains that the architecture "is not > supported"; I haven't checked whether that's simply a case of > excessive conservatism. > Could you please take a look and restrict the package's official > Architecture accordingly? I thought that the idea generally is to not restrict by default and possibly to let interested in porting to look at it. Policy 5.6.8 states "Specifying a list of architectures or architecture wildcards other than any is for the minority of cases where a program is not portable or is not useful on some architectures". Theoretically I think singularity could be ported for other architectures (CCing upstream for clarification), not that me or upstream is going to embark on such a voyage ATM ;) If there is somewhere policy/recommendation that I should better drop from any to a restricted list of architectures, please let me know, and I will do so for the next release. Cheers, -- Yaroslav O. Halchenko Center for Open Neuroscience http://centerforopenneuroscience.org Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik
