public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Agostino Sarubbo" <ago@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-apps/bubblewrap/
Date: Sat,  2 May 2020 18:44:44 +0000 (UTC)	[thread overview]
Message-ID: <1588445078.5a470d14ac92b78e1ffd9fbec6086f393441a78c.ago@gentoo> (raw)

commit:     5a470d14ac92b78e1ffd9fbec6086f393441a78c
Author:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
AuthorDate: Sat May  2 18:44:38 2020 +0000
Commit:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
CommitDate: Sat May  2 18:44:38 2020 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5a470d14

sys-apps/bubblewrap: x86 stable wrt bug #686114

Package-Manager: Portage-2.3.89, Repoman-2.3.20
RepoMan-Options: --include-arches="x86"
Signed-off-by: Agostino Sarubbo <ago <AT> gentoo.org>

 sys-apps/bubblewrap/bubblewrap-0.4.1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/sys-apps/bubblewrap/bubblewrap-0.4.1.ebuild b/sys-apps/bubblewrap/bubblewrap-0.4.1.ebuild
index 47734ec6084..718abee4e09 100644
--- a/sys-apps/bubblewrap/bubblewrap-0.4.1.ebuild
+++ b/sys-apps/bubblewrap/bubblewrap-0.4.1.ebuild
@@ -11,7 +11,7 @@ SRC_URI="https://github.com/containers/${PN}/releases/download/v${PV}/${P}.tar.x
 
 LICENSE="LGPL-2+"
 SLOT="0"
-KEYWORDS="amd64 ~arm ~arm64 ~ppc ~ppc64 ~x86"
+KEYWORDS="amd64 ~arm ~arm64 ~ppc ~ppc64 x86"
 IUSE="selinux +suid"
 
 RDEPEND="


             reply	other threads:[~2020-05-02 18:44 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-02 18:44 Agostino Sarubbo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-09  6:59 [gentoo-commits] repo/gentoo:master commit in: sys-apps/bubblewrap/ Arthur Zamarin
2024-09-29 16:00 Arthur Zamarin
2024-09-29 16:00 Arthur Zamarin
2024-09-29 16:00 Arthur Zamarin
2024-09-29 16:00 Arthur Zamarin
2024-09-29 16:00 Arthur Zamarin
2024-08-17 19:09 Arthur Zamarin
2024-08-11 16:26 Arthur Zamarin
2023-08-09 18:14 Piotr Karbowski
2023-05-17 21:55 Matt Turner
2023-05-03  3:53 Sam James
2023-05-02 19:31 Arthur Zamarin
2023-05-02 18:12 Arthur Zamarin
2023-05-02 17:36 Arthur Zamarin
2023-05-02 17:35 Sam James
2023-05-02 17:35 Sam James
2023-03-01 22:49 Piotr Karbowski
2023-01-03 14:08 Matt Turner
2022-12-13  0:09 Sam James
2022-12-13  0:09 Sam James
2022-12-13  0:09 Sam James
2022-12-13  0:09 Sam James
2022-12-13  0:09 Sam James
2022-12-13  0:09 Sam James
2022-11-11 22:15 Piotr Karbowski
2022-08-15 19:13 Arthur Zamarin
2022-08-15 19:13 Arthur Zamarin
2022-08-15 17:43 Arthur Zamarin
2022-07-29  2:59 Sam James
2022-07-21  2:04 Matt Turner
2022-07-21  0:13 Sam James
2022-07-18 17:44 Sam James
2022-07-02 20:24 Piotr Karbowski
2022-05-31 18:24 Matt Turner
2022-05-31  9:24 Jakov Smolić
2022-05-28  5:05 Sam James
2022-05-26  3:52 WANG Xuerui
2022-05-12  2:14 Matt Turner
2022-02-27 17:59 Piotr Karbowski
2021-11-06  4:09 Sam James
2021-11-06  3:58 Sam James
2021-10-04  1:25 Sam James
2021-10-04  1:24 Sam James
2021-08-23 20:53 Piotr Karbowski
2021-06-02  2:42 Yixun Lan
2021-05-17  3:19 Sam James
2021-02-17  0:06 Sam James
2021-02-08 17:21 Sam James
2020-07-29 19:56 Mart Raudsepp
2020-05-25 21:00 Piotr Karbowski
2020-05-04  6:16 Mart Raudsepp
2020-05-02 18:42 Agostino Sarubbo
2020-05-01 21:42 Piotr Karbowski
2020-05-01 21:29 Piotr Karbowski
2020-04-20 18:16 Agostino Sarubbo
2020-04-20 17:03 Agostino Sarubbo
2019-05-22 21:20 Aaron Bauman
2019-05-10 17:49 Mikle Kolyada
2019-05-08  9:33 Mikle Kolyada
2019-04-11  1:46 Aaron Bauman
2019-02-17 15:56 Mikle Kolyada
2019-02-16 23:34 Mart Raudsepp
2019-02-16 23:34 Mart Raudsepp
2018-12-29 19:39 Thomas Deutschmann
2018-12-19 22:27 Sergei Trofimovich
2018-12-16 11:40 Sergei Trofimovich
2018-11-16 17:13 Gilles Dartiguelongue
2018-10-15 20:58 Remi Cardona
2018-10-15 17:19 Sobhan Mohammadpour

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=1588445078.5a470d14ac92b78e1ffd9fbec6086f393441a78c.ago@gentoo \
    --to=ago@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