public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-im/discord-bin/
Date: Sat, 12 Sep 2020 01:05:46 +0000 (UTC)	[thread overview]
Message-ID: <1599872736.47f6a0a6e1e53b0a9dae028cb65a90ae78168e85.sam@gentoo> (raw)

commit:     47f6a0a6e1e53b0a9dae028cb65a90ae78168e85
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sat Sep 12 01:05:36 2020 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sat Sep 12 01:05:36 2020 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=47f6a0a6

net-im/discord-bin: add CONFIG_USER_NS check

Closes: https://bugs.gentoo.org/711094
Package-Manager: Portage-3.0.4, Repoman-3.0.1
Signed-off-by: Sam James <sam <AT> gentoo.org>

 net-im/discord-bin/discord-bin-0.0.12.ebuild | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/net-im/discord-bin/discord-bin-0.0.12.ebuild b/net-im/discord-bin/discord-bin-0.0.12.ebuild
index cffd5a6de94..03acc4c6903 100644
--- a/net-im/discord-bin/discord-bin-0.0.12.ebuild
+++ b/net-im/discord-bin/discord-bin-0.0.12.ebuild
@@ -6,7 +6,7 @@ EAPI=7
 MY_PN=${PN/-bin/}
 MY_BIN="D${MY_PN/d/}"
 
-inherit desktop pax-utils unpacker xdg
+inherit desktop linux-info pax-utils unpacker xdg
 
 DESCRIPTION="All-in-one voice and text chat for gamers"
 HOMEPAGE="https://discordapp.com"
@@ -63,6 +63,8 @@ QA_PREBUILT="
 	opt/discord/libffmpeg.so
 "
 
+CONFIG_CHECK="USER_NS"
+
 src_prepare() {
 	default
 


             reply	other threads:[~2020-09-12  1:05 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-12  1:05 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-01-14  5:31 [gentoo-commits] repo/gentoo:master commit in: net-im/discord-bin/ Nick Sarnie
2023-01-14  5:29 Nick Sarnie
2023-01-14  1:20 Nick Sarnie
2023-01-13 18:49 Nick Sarnie
2023-01-13 18:30 Nick Sarnie
2023-01-13  0:40 Nick Sarnie
2023-01-13  0:16 Nick Sarnie
2023-01-13  0:12 Nick Sarnie
2022-12-10  3:29 Nick Sarnie
2022-11-07  8:49 Joonas Niilola
2022-11-07  8:49 Joonas Niilola
2022-10-21 23:55 Stefan Strogin
2022-09-15 18:39 Sam James
2022-08-10 20:36 Sam James
2022-07-24  6:08 Joonas Niilola
2022-06-08 18:16 Stefan Strogin
2022-06-08 18:14 Stefan Strogin
2022-05-26 12:58 Joonas Niilola
2022-05-26 12:58 Joonas Niilola
2022-05-20  2:40 Sam James
2022-05-20  1:18 Sam James
2022-05-19  2:03 Sam James
2022-05-19  2:03 Sam James
2022-02-17 20:25 Ionen Wolkens
2022-02-17 20:25 Ionen Wolkens
2022-02-17 20:25 Ionen Wolkens
2021-12-21  2:19 Sam James
2021-12-01 18:34 Sam James
2021-12-01 14:43 Sam James
2021-12-01 14:42 Sam James
2021-11-20 23:05 Ionen Wolkens
2021-10-19  0:55 Ionen Wolkens
2021-10-19  0:55 Ionen Wolkens
2021-10-19  0:55 Ionen Wolkens
2021-09-22 20:22 Stefan Strogin
2021-05-25 14:13 Stefan Strogin
2021-03-24 16:28 Stefan Strogin
2020-12-05 21:10 Stefan Strogin
2020-09-12  3:01 Sam James
2020-09-12  1:05 Sam James
2020-09-12  1:05 Sam James
2020-08-06 20:55 Sam James
2020-08-06 20:55 Sam James
2020-08-06 20:55 Sam James
2020-02-29  9:18 Johannes Huber
2020-02-29  9:18 Johannes Huber
2020-01-12 20:46 Johannes Huber
2020-01-12 13:20 Johannes Huber
2020-01-12 13:20 Johannes Huber
2020-01-12 13:20 Johannes Huber
2020-01-12 13:20 Johannes Huber
2019-12-04 16:06 Aaron Bauman
2019-03-15 22:22 Thomas Deutschmann
2019-03-12 21:32 Thomas Deutschmann
2019-03-12 21:32 Thomas Deutschmann
2019-01-19  5:43 Thomas Deutschmann
2019-01-19  5:43 Thomas Deutschmann
2018-05-01 20:37 Johannes Huber
2018-05-01 20:37 Johannes Huber
2018-01-09 17:36 Johannes Huber
2018-01-09 17:34 Johannes Huber
2017-12-22  8:59 Johannes Huber
2017-12-12  6:15 Johannes Huber
2017-09-13 17:52 Johannes Huber
2017-09-13 17:52 Johannes Huber
2017-09-09  8:00 Johannes Huber
2017-09-09  8:00 Johannes Huber
2017-04-14 12:03 Johannes Huber
2017-01-29 20:21 Johannes Huber

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=1599872736.47f6a0a6e1e53b0a9dae028cb65a90ae78168e85.sam@gentoo \
    --to=sam@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