From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-sound/audacity/
Date: Sat, 25 Aug 2018 18:55:35 +0000 (UTC) [thread overview]
Message-ID: <1535223326.97ac0c6f3de154527d3c490b1e0a96df176786af.slyfox@gentoo> (raw)
commit: 97ac0c6f3de154527d3c490b1e0a96df176786af
Author: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Sat Aug 25 18:47:08 2018 +0000
Commit: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Sat Aug 25 18:55:26 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=97ac0c6f
media-sound/audacity: stable 2.2.2 for ppc64, bug #658644
Package-Manager: Portage-2.3.48, Repoman-2.3.10
RepoMan-Options: --include-arches="ppc64"
media-sound/audacity/audacity-2.2.2.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/media-sound/audacity/audacity-2.2.2.ebuild b/media-sound/audacity/audacity-2.2.2.ebuild
index 7f0a6fabb20..13e4b20853c 100644
--- a/media-sound/audacity/audacity-2.2.2.ebuild
+++ b/media-sound/audacity/audacity-2.2.2.ebuild
@@ -15,7 +15,7 @@ SRC_URI="https://dev.gentoo.org/~polynomial-c/dist/${MY_P}.tar.xz
LICENSE="GPL-2"
SLOT="0"
-KEYWORDS="amd64 ~mips ~ppc ~ppc64 x86"
+KEYWORDS="amd64 ~mips ~ppc ppc64 x86"
IUSE="alsa cpu_flags_x86_sse doc ffmpeg +flac id3tag jack +ladspa +lame libav
+lv2 mad +midi nls +portmixer sbsms +soundtouch twolame vamp +vorbis +vst"
next reply other threads:[~2018-08-25 18:55 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-25 18:55 Sergei Trofimovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-13 14:42 [gentoo-commits] repo/gentoo:master commit in: media-sound/audacity/ Miroslav Šulc
2025-03-11 19:07 Miroslav Šulc
2025-01-25 9:38 Miroslav Šulc
2024-12-29 17:19 Miroslav Šulc
2024-12-29 17:19 Miroslav Šulc
2024-12-24 5:06 Sam James
2024-12-14 5:36 Miroslav Šulc
2024-10-31 19:20 Miroslav Šulc
2024-06-01 3:46 Ionen Wolkens
2024-05-17 18:26 Sam James
2024-04-17 19:20 Ionen Wolkens
2024-03-21 2:52 Sam James
2024-03-05 4:48 Sam James
2024-01-16 3:36 Sam James
2024-01-11 13:03 Sam James
2024-01-11 13:01 Sam James
2023-12-15 12:37 Arthur Zamarin
2023-12-15 3:30 Sam James
2023-12-15 3:26 Ionen Wolkens
2023-12-05 18:25 Ionen Wolkens
2023-12-04 10:20 Sam James
2023-10-03 14:44 Mike Gilbert
2023-10-02 7:02 Miroslav Šulc
2023-06-19 6:47 Miroslav Šulc
2023-06-07 5:19 Miroslav Šulc
2023-06-06 16:55 Arthur Zamarin
2023-05-01 8:32 Miroslav Šulc
2023-05-01 7:35 Arthur Zamarin
2023-03-02 6:43 Miroslav Šulc
2023-01-29 11:12 Miroslav Šulc
2023-01-21 16:18 Arsen Arsenović
2021-09-22 14:30 Yixun Lan
2021-08-16 21:28 Sam James
2020-09-13 8:44 Sergei Trofimovich
2020-09-09 21:59 Sergei Trofimovich
2020-09-07 8:59 Miroslav Šulc
2020-09-07 7:35 Sergei Trofimovich
2020-09-07 7:31 Sergei Trofimovich
2020-08-23 10:39 Miroslav Šulc
2020-08-06 7:33 Miroslav Šulc
2020-08-06 2:35 Sam James
2020-08-04 6:47 Miroslav Šulc
2020-08-03 5:00 Miroslav Šulc
2020-08-02 18:23 Miroslav Šulc
2020-08-02 11:10 Miroslav Šulc
2020-04-25 20:09 Mikle Kolyada
2020-02-12 14:14 Miroslav Šulc
2019-03-11 15:54 Lars Wendler
2018-11-04 22:26 Andreas Sturmlechner
2018-11-04 22:03 Sergei Trofimovich
2018-08-23 2:32 Mikle Kolyada
2018-08-23 1:41 Thomas Deutschmann
2018-08-22 17:07 Andreas Sturmlechner
2018-08-22 17:07 Andreas Sturmlechner
2018-02-21 10:18 Lars Wendler
2018-02-21 10:14 Lars Wendler
2018-02-21 10:14 Lars Wendler
2017-12-07 11:17 Lars Wendler
2017-11-06 11:11 Lars Wendler
2017-11-06 11:09 Lars Wendler
2017-09-11 12:10 Alexis Ballier
2017-06-18 16:42 Alexis Ballier
2017-06-13 12:31 Agostino Sarubbo
2017-06-05 11:05 Agostino Sarubbo
2017-05-11 9:37 Lars Wendler
2017-05-11 9:37 Lars Wendler
2016-03-31 12:22 Lars Wendler
2015-11-08 10:07 Alexis Ballier
2015-11-08 10:07 Alexis Ballier
2015-10-30 15:21 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=1535223326.97ac0c6f3de154527d3c490b1e0a96df176786af.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