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-p2p/retroshare/
Date: Thu, 11 Mar 2021 02:35:49 +0000 (UTC)	[thread overview]
Message-ID: <1615430113.bd9a1635716a34958185d553090499e42b084a82.sam@gentoo> (raw)

commit:     bd9a1635716a34958185d553090499e42b084a82
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Thu Mar 11 02:35:13 2021 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Thu Mar 11 02:35:13 2021 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=bd9a1635

net-p2p/retroshare: Stabilize 0.6.5-r2 amd64, #761885

Signed-off-by: Sam James <sam <AT> gentoo.org>

 net-p2p/retroshare/retroshare-0.6.5-r2.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/net-p2p/retroshare/retroshare-0.6.5-r2.ebuild b/net-p2p/retroshare/retroshare-0.6.5-r2.ebuild
index 51d46eb7ff2..595609fef04 100644
--- a/net-p2p/retroshare/retroshare-0.6.5-r2.ebuild
+++ b/net-p2p/retroshare/retroshare-0.6.5-r2.ebuild
@@ -12,7 +12,7 @@ SRC_URI="https://github.com/RetroShare/RetroShare/releases/download/v${PV}/Retro
 # pegmarkdown can also be used with MIT
 LICENSE="AGPL-3 GPL-2 GPL-3 Apache-2.0 LGPL-3"
 SLOT="0"
-KEYWORDS="~amd64 ~x86"
+KEYWORDS="amd64 ~x86"
 IUSE="cli control-socket gnome-keyring +gui +jsonapi service +sqlcipher webui +xapian"
 
 REQUIRED_USE="


             reply	other threads:[~2021-03-11  2:35 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-11  2:35 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-23 11:47 [gentoo-commits] repo/gentoo:master commit in: net-p2p/retroshare/ Arthur Zamarin
2024-10-23 11:47 Arthur Zamarin
2024-09-13  7:42 Joonas Niilola
2024-09-13  7:42 Joonas Niilola
2024-07-04  1:29 Sam James
2024-07-04  1:23 Sam James
2024-07-04  1:23 Sam James
2024-07-04  1:23 Sam James
2024-05-24 13:49 Joonas Niilola
2024-05-24  7:51 Joonas Niilola
2024-05-24  7:51 Joonas Niilola
2024-03-03 20:38 Andreas K. Hüttel
2023-05-18 12:17 Andreas Sturmlechner
2021-12-09 16:24 Agostino Sarubbo
2021-12-07  7:48 Agostino Sarubbo
2021-10-31  8:21 Joonas Niilola
2021-08-07  5:51 Ionen Wolkens
2021-03-12 16:01 Ben Kohler
2021-03-11 13:30 Sam James
2021-02-06 18:04 Ben Kohler
2021-02-06 16:25 Ben Kohler
2021-02-03 18:18 Ben Kohler
2020-05-11 16:49 Agostino Sarubbo
2020-05-08  6:38 Agostino Sarubbo
2020-04-28 17:47 Matt Turner
2020-04-26 11:00 David Seifert
2020-03-20  7:02 Joonas Niilola
2020-03-19 13:48 Joonas Niilola
2020-03-19 13:48 Joonas Niilola
2020-01-12 11:14 David Seifert
2019-05-15 12:48 Andreas Sturmlechner
2019-05-15 12:48 Andreas Sturmlechner
2018-11-07  9:26 Sergey Popov
2018-09-09  8:25 Mikle Kolyada
2018-09-09  1:12 Thomas Deutschmann
2018-08-21  8:27 Andreas Sturmlechner
2018-08-21  8:27 Andreas Sturmlechner
2018-06-09 21:15 Michał Górny
2018-04-23  8:30 Sergey Popov
2018-04-23  8:30 Sergey Popov
2018-04-23  8:30 Sergey Popov
2018-04-23  8:30 Sergey Popov
2018-04-23  8:30 Sergey Popov
2017-08-02  9:28 Sergey Popov
2017-07-28 13:06 Sergey Popov
2017-06-13 16:09 Sergey Popov
2017-06-13 16:09 Sergey Popov
2017-03-27 13:44 Sergey Popov
2017-01-12 13:49 Sergey Popov
2017-01-12 13:49 Sergey Popov
2016-12-15  8:44 Sergey Popov
2016-12-06 12:30 Sergey Popov
2016-12-06 12:30 Sergey Popov
2016-08-17 14:19 Sergey Popov
2016-08-17 14:19 Sergey Popov
2016-07-27 21:00 Sergey Popov
2016-06-18 11:49 Sergey Popov
2016-04-26  9:23 Sergey Popov
2016-03-05 15:50 Mikle Kolyada
2016-02-08 19:00 Sergey Popov
2016-02-08 19:00 Sergey Popov
2015-09-22 10:18 Sergey Popov
2015-09-22 10:18 Sergey Popov
2015-09-21 18:23 Sergey Popov
2015-08-12 10:19 Sergey Popov
2015-08-10  4:28 Robin H. Johnson

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=1615430113.bd9a1635716a34958185d553090499e42b084a82.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