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-libs/libnice/
Date: Thu, 21 Jul 2022 00:13:22 +0000 (UTC)	[thread overview]
Message-ID: <1658362378.b9b290cf183d5694ee663ea592c13565603c3a46.sam@gentoo> (raw)

commit:     b9b290cf183d5694ee663ea592c13565603c3a46
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Thu Jul 21 00:12:58 2022 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Thu Jul 21 00:12:58 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b9b290cf

net-libs/libnice: Stabilize 0.1.19 ppc, #853958

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

 net-libs/libnice/libnice-0.1.19.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/net-libs/libnice/libnice-0.1.19.ebuild b/net-libs/libnice/libnice-0.1.19.ebuild
index 2ce8b73a1e54..0fbb4c68460e 100644
--- a/net-libs/libnice/libnice-0.1.19.ebuild
+++ b/net-libs/libnice/libnice-0.1.19.ebuild
@@ -10,7 +10,7 @@ SRC_URI="https://nice.freedesktop.org/releases/${P}.tar.gz"
 
 LICENSE="|| ( MPL-1.1 LGPL-2.1 )"
 SLOT="0"
-KEYWORDS="~alpha amd64 arm arm64 ~hppa ~ia64 ~ppc ppc64 ~riscv sparc x86 ~amd64-linux ~x86-linux ~ppc-macos"
+KEYWORDS="~alpha amd64 arm arm64 ~hppa ~ia64 ppc ppc64 ~riscv sparc x86 ~amd64-linux ~x86-linux ~ppc-macos"
 IUSE="+gnutls gtk-doc +introspection +upnp"
 
 RDEPEND="


             reply	other threads:[~2022-07-21  0:13 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-21  0:13 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-09 19:41 [gentoo-commits] repo/gentoo:master commit in: net-libs/libnice/ Andreas Sturmlechner
2024-10-27  6:50 Arthur Zamarin
2024-10-26  3:49 Sam James
2024-10-25 23:44 Sam James
2024-10-25 22:21 Sam James
2024-09-24  7:08 Sam James
2024-09-17 16:00 Sam James
2024-09-17 16:00 Sam James
2024-09-16 13:52 Petr Vaněk
2024-09-16 13:28 Petr Vaněk
2024-07-05 17:41 Conrad Kostecki
2023-10-10  5:42 Joonas Niilola
2023-10-09  6:18 Sam James
2023-10-09  4:36 Sam James
2023-10-09  4:36 Sam James
2023-05-30 18:05 Sam James
2023-05-13  0:43 Sam James
2023-04-13  8:13 Ulrich Müller
2023-04-13  8:11 Ulrich Müller
2022-11-25  3:08 Matt Turner
2022-10-31 14:28 Matt Turner
2022-07-21  2:04 Matt Turner
2022-07-18 23:41 Sam James
2022-07-18 17:44 Sam James
2022-07-06  1:24 Sam James
2022-07-02 20:47 Sam James
2022-05-31  9:24 Jakov Smolić
2022-05-28  5:45 Sam James
2022-05-28  5:38 Sam James
2022-05-28  5:05 Sam James
2022-05-28  1:27 Sam James
2022-05-28  1:20 Sam James
2022-05-08 19:02 Matt Turner
2022-05-08 19:02 Matt Turner
2022-03-08 13:48 Sam James
2022-03-08 13:48 Sam James
2022-03-08 13:48 Sam James
2022-03-08 13:48 Sam James
2021-05-02 10:16 Mikle Kolyada
2020-02-12 11:46 Mart Raudsepp
2020-01-17 13:05 Agostino Sarubbo
2019-10-09  8:27 Agostino Sarubbo
2019-07-03  7:11 Agostino Sarubbo
2019-06-27 12:35 Agostino Sarubbo
2019-06-17 10:07 Mikle Kolyada
2019-05-23 13:02 Mikle Kolyada
2019-02-14 11:29 Mart Raudsepp
2016-11-13 11:19 Gilles Dartiguelongue
2016-11-13 11:19 Gilles Dartiguelongue

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=1658362378.b9b290cf183d5694ee663ea592c13565603c3a46.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