From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-apps/nix/
Date: Sun, 13 Oct 2019 11:57:31 +0000 (UTC) [thread overview]
Message-ID: <1570967847.e1e6791f142d200b9f4fd79ea1574479a50fc954.slyfox@gentoo> (raw)
commit: e1e6791f142d200b9f4fd79ea1574479a50fc954
Author: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Sun Oct 13 11:56:57 2019 +0000
Commit: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Sun Oct 13 11:57:27 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e1e6791f
sys-apps/nix: add check for USER_NS
nix-daemon uses user namespaces to build derivations
(includeing nix-channel --update).
The error is obwerved and reported by RuZzz.
Package-Manager: Portage-2.3.76, Repoman-2.3.17
Signed-off-by: Sergei Trofimovich <slyfox <AT> gentoo.org>
sys-apps/nix/nix-2.3.1.ebuild | 9 ++++++++-
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/sys-apps/nix/nix-2.3.1.ebuild b/sys-apps/nix/nix-2.3.1.ebuild
index bbfe27eb976..df8590b23b5 100644
--- a/sys-apps/nix/nix-2.3.1.ebuild
+++ b/sys-apps/nix/nix-2.3.1.ebuild
@@ -3,7 +3,7 @@
EAPI=7
-inherit autotools flag-o-matic readme.gentoo-r1 user
+inherit autotools flag-o-matic linux-info readme.gentoo-r1 user
DESCRIPTION="A purely functional package manager"
HOMEPAGE="https://nixos.org/nix"
@@ -65,6 +65,13 @@ Next steps:
nix package manager user manual: http://nixos.org/nix/manual/
"
+pkg_pretend() {
+ # USER_NS is used to run builders in a default setting in linux:
+ # https://nixos.wiki/wiki/Nix#Sandboxing
+ local CONFIG_CHECK="~USER_NS"
+ check_extra_config
+}
+
pkg_setup() {
enewgroup nixbld
for i in {1..10}; do
next reply other threads:[~2019-10-13 11:57 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-13 11:57 Sergei Trofimovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-10-10 22:35 [gentoo-commits] repo/gentoo:master commit in: sys-apps/nix/ Sergei Trofimovich
2019-10-10 22:35 Sergei Trofimovich
2019-09-20 22:44 Sergei Trofimovich
2019-09-07 8:03 Sergei Trofimovich
2019-08-11 11:20 David Seifert
2019-06-30 20:35 Sergei Trofimovich
2019-06-30 20:35 Sergei Trofimovich
2019-05-15 7:21 Sergei Trofimovich
2019-04-26 15:47 Sergei Trofimovich
2019-02-11 23:36 Sergei Trofimovich
2019-01-12 12:59 Sergei Trofimovich
2018-11-04 22:50 Sergei Trofimovich
2018-10-02 21:29 Sergei Trofimovich
2018-10-02 21:29 Sergei Trofimovich
2018-09-19 22:59 Sergei Trofimovich
2018-09-19 22:59 Sergei Trofimovich
2018-09-06 22:37 Sergei Trofimovich
2018-09-06 22:37 Sergei Trofimovich
2018-09-04 8:19 Sergei Trofimovich
2018-06-08 15:31 Sergei Trofimovich
2018-06-08 15:31 Sergei Trofimovich
2018-05-04 22:24 Sergei Trofimovich
2018-04-20 22:16 Sergei Trofimovich
2017-12-21 8:01 Sergei Trofimovich
2017-09-15 20:50 Sergei Trofimovich
2017-09-15 20:50 Sergei Trofimovich
2017-07-18 20:15 Sergei Trofimovich
2017-07-18 20:15 Sergei Trofimovich
2017-07-13 18:42 Sergei Trofimovich
2017-06-19 20:27 Sergei Trofimovich
2017-06-12 21:23 Sergei Trofimovich
2017-05-07 13:10 Michał Górny
2017-05-07 11:22 Sergei Trofimovich
2017-05-07 11:22 Sergei Trofimovich
2017-04-17 17:38 Sergei Trofimovich
2017-02-02 21:18 Sergei Trofimovich
2017-02-01 22:18 Sergei Trofimovich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1570967847.e1e6791f142d200b9f4fd79ea1574479a50fc954.slyfox@gentoo \
--to=slyfox@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox