From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-libs/libsrtp/
Date: Fri, 20 Jul 2018 22:48:18 +0000 (UTC) [thread overview]
Message-ID: <1532126668.c97d9ee53042a0d716496e39a0602e00d62c1418.slyfox@gentoo> (raw)
commit: c97d9ee53042a0d716496e39a0602e00d62c1418
Author: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Fri Jul 20 22:31:14 2018 +0000
Commit: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Fri Jul 20 22:44:28 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c97d9ee5
net-libs/libsrtp: stable 2.2.0 for ppc64, bug #661288
Bug: https://bugs.gentoo.org/661288
Package-Manager: Portage-2.3.43, Repoman-2.3.10
RepoMan-Options: --include-arches="ppc64"
net-libs/libsrtp/libsrtp-2.2.0.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net-libs/libsrtp/libsrtp-2.2.0.ebuild b/net-libs/libsrtp/libsrtp-2.2.0.ebuild
index 3f5fd3943d4..2a713a4ec24 100644
--- a/net-libs/libsrtp/libsrtp-2.2.0.ebuild
+++ b/net-libs/libsrtp/libsrtp-2.2.0.ebuild
@@ -11,7 +11,7 @@ SRC_URI="https://github.com/cisco/${PN}/archive/v${PV}.tar.gz -> ${P}.tar.gz"
LICENSE="BSD"
SLOT="2/1"
-KEYWORDS="~alpha amd64 ~arm ~hppa ia64 ~ppc ~ppc64 -sparc ~x86 ~x86-fbsd ~ppc-macos ~x64-macos ~x86-macos"
+KEYWORDS="~alpha amd64 ~arm ~hppa ia64 ~ppc ppc64 -sparc ~x86 ~x86-fbsd ~ppc-macos ~x64-macos ~x86-macos"
IUSE="aesicm console debug doc libressl openssl static-libs syslog test"
RDEPEND="
next reply other threads:[~2018-07-20 22:48 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-20 22:48 Sergei Trofimovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-24 5:24 [gentoo-commits] repo/gentoo:master commit in: net-libs/libsrtp/ Matt Jolly
2024-06-06 20:27 Mike Gilbert
2022-10-12 7:24 Stephan Hartmann
2022-10-12 6:50 Agostino Sarubbo
2022-10-12 6:49 Agostino Sarubbo
2022-10-11 18:26 Sam James
2022-10-11 18:26 Sam James
2022-10-11 17:15 Arthur Zamarin
2022-10-11 17:15 Arthur Zamarin
2021-05-31 20:45 David Seifert
2021-05-02 10:16 Mikle Kolyada
2021-03-16 13:01 Joonas Niilola
2021-02-09 23:33 Lars Wendler
2021-02-01 13:30 Sam James
2021-02-01 8:26 Sam James
2021-01-30 14:29 Sam James
2021-01-30 10:04 Sam James
2021-01-30 10:03 Sam James
2021-01-28 17:47 Sam James
2020-01-01 16:03 Andreas Sturmlechner
2019-07-29 20:02 Aaron Bauman
2019-07-28 18:31 Aaron Bauman
2019-07-13 12:08 Sergei Trofimovich
2019-05-23 13:02 Mikle Kolyada
2019-05-15 15:26 Mikle Kolyada
2019-05-15 15:26 Mikle Kolyada
2019-05-12 22:03 Sergei Trofimovich
2019-05-12 21:57 Sergei Trofimovich
2019-05-12 21:48 Sergei Trofimovich
2019-05-08 14:38 Tobias Klausmann
2018-11-23 22:15 Mart Raudsepp
2018-07-31 7:53 Tony Vroon
2018-07-21 16:57 Tobias Klausmann
2018-07-20 23:18 Sergei Trofimovich
2018-07-20 8:08 Sergei Trofimovich
2018-06-18 12:23 Tony Vroon
2018-04-23 14:35 Aaron Bauman
2017-11-12 10:40 Sergei Trofimovich
2017-11-12 10:27 Sergei Trofimovich
2017-11-05 21:29 Thomas Deutschmann
2017-11-02 10:47 Manuel Rüger
2017-11-01 7:25 Sergei Trofimovich
2017-10-31 17:28 Mike Gilbert
2017-08-11 13:21 Michał Górny
2017-08-11 13:21 Michał Górny
2017-08-11 13:21 Michał Górny
2017-06-25 14:42 Alexis Ballier
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=1532126668.c97d9ee53042a0d716496e39a0602e00d62c1418.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