From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-libs/speex/
Date: Tue, 19 Dec 2017 21:48:28 +0000 (UTC) [thread overview]
Message-ID: <1513720103.cb3194ca2d9d215c32fac5fb7276852f6368a6fc.slyfox@gentoo> (raw)
commit: cb3194ca2d9d215c32fac5fb7276852f6368a6fc
Author: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Tue Dec 19 21:47:59 2017 +0000
Commit: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Tue Dec 19 21:48:23 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=cb3194ca
media-libs/speex: stable 1.2.0-r1 for hppa, bug #641504
Package-Manager: Portage-2.3.19, Repoman-2.3.6
RepoMan-Options: --include-arches="hppa"
media-libs/speex/speex-1.2.0-r1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/media-libs/speex/speex-1.2.0-r1.ebuild b/media-libs/speex/speex-1.2.0-r1.ebuild
index d8e39694072..067a6748ea6 100644
--- a/media-libs/speex/speex-1.2.0-r1.ebuild
+++ b/media-libs/speex/speex-1.2.0-r1.ebuild
@@ -13,7 +13,7 @@ SRC_URI="https://downloads.xiph.org/releases/speex/${MY_P}.tar.gz"
LICENSE="BSD"
SLOT="0"
-KEYWORDS="~alpha amd64 ~arm ~arm64 ~hppa ~ia64 ~mips ~ppc ~ppc64 ~sh ~sparc x86 ~amd64-fbsd ~x86-fbsd ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~sparc-solaris ~x86-solaris"
+KEYWORDS="~alpha amd64 ~arm ~arm64 hppa ~ia64 ~mips ~ppc ~ppc64 ~sh ~sparc x86 ~amd64-fbsd ~x86-fbsd ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~sparc-solaris ~x86-solaris"
IUSE="cpu_flags_arm_v4 cpu_flags_arm_v5 cpu_flags_arm_v6 cpu_flags_x86_sse static-libs utils +vbr"
RDEPEND="
next reply other threads:[~2017-12-19 21:48 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-19 21:48 Sergei Trofimovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-13 9:35 [gentoo-commits] repo/gentoo:master commit in: media-libs/speex/ Sam James
2023-06-25 6:56 Miroslav Šulc
2023-06-24 6:48 Jakov Smolić
2023-06-24 6:45 Sam James
2023-06-24 6:45 Sam James
2023-06-24 6:43 Sam James
2023-06-24 6:43 Sam James
2023-06-24 6:43 Sam James
2023-06-24 6:43 Sam James
2023-05-17 7:13 Sam James
2023-05-15 6:47 Sam James
2023-01-23 3:29 Sam James
2022-07-27 5:02 Miroslav Šulc
2022-07-26 15:20 Agostino Sarubbo
2022-07-26 15:19 Agostino Sarubbo
2022-07-26 15:18 Agostino Sarubbo
2022-07-26 15:16 Agostino Sarubbo
2022-07-26 7:05 Sam James
2022-07-26 7:04 Sam James
2022-07-26 7:04 Sam James
2022-06-25 9:17 Miroslav Šulc
2022-05-26 4:45 WANG Xuerui
2021-08-10 18:06 Marek Szuba
2021-01-23 21:13 Andreas Sturmlechner
2021-01-06 14:27 Fabian Groffen
2020-12-21 9:36 Sergei Trofimovich
2020-12-16 11:12 Sam James
2020-12-06 21:38 Sam James
2020-12-06 18:45 Sam James
2020-12-05 11:43 Sergei Trofimovich
2020-12-04 18:37 Sergei Trofimovich
2020-12-03 17:37 Thomas Deutschmann
2020-11-07 19:10 David Seifert
2019-05-14 17:53 Aaron Bauman
2018-03-22 20:48 James Le Cuirot
2018-03-03 12:14 Tobias Klausmann
2018-02-27 22:26 Sergei Trofimovich
2017-12-24 9:59 Sergei Trofimovich
2017-12-20 21:42 Sergei Trofimovich
2017-12-19 15:46 Thomas Deutschmann
2017-12-19 12:08 Jason Zaman
2017-12-17 22:22 Andreas Sturmlechner
2017-08-30 21:29 James Le Cuirot
2017-03-04 22:50 Michael Palimaka
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=1513720103.cb3194ca2d9d215c32fac5fb7276852f6368a6fc.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