From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/libcdio-paranoia/
Date: Fri, 14 Dec 2018 22:50:42 +0000 (UTC) [thread overview]
Message-ID: <1544827836.096b449e7002d65b1714e849490f6d61ac4d16f0.slyfox@gentoo> (raw)
commit: 096b449e7002d65b1714e849490f6d61ac4d16f0
Author: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Fri Dec 14 22:49:43 2018 +0000
Commit: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Fri Dec 14 22:50:36 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=096b449e
dev-libs/libcdio-paranoia: stable 0.94_p2 for ppc64, bug #673074
Package-Manager: Portage-2.3.52, Repoman-2.3.12
RepoMan-Options: --include-arches="ppc64"
Signed-off-by: Sergei Trofimovich <slyfox <AT> gentoo.org>
dev-libs/libcdio-paranoia/libcdio-paranoia-0.94_p2.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-libs/libcdio-paranoia/libcdio-paranoia-0.94_p2.ebuild b/dev-libs/libcdio-paranoia/libcdio-paranoia-0.94_p2.ebuild
index 1f1bfcf5fe8..4170fa3948f 100644
--- a/dev-libs/libcdio-paranoia/libcdio-paranoia-0.94_p2.ebuild
+++ b/dev-libs/libcdio-paranoia/libcdio-paranoia-0.94_p2.ebuild
@@ -16,7 +16,7 @@ SRC_URI="mirror://gnu/${PN%-*}/${MY_P}.tar.gz"
# clause "or later" so we use LGPL-2.1 without +
LICENSE="GPL-3+ GPL-2+ LGPL-2.1"
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="+cxx static-libs test"
RDEPEND="app-eselect/eselect-cdparanoia
next reply other threads:[~2018-12-14 22:50 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-14 22:50 Sergei Trofimovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-20 10:37 [gentoo-commits] repo/gentoo:master commit in: dev-libs/libcdio-paranoia/ WANG Xuerui
2021-08-23 22:59 Marek Szuba
2021-04-19 20:54 Sam James
2021-02-04 23:51 Sam James
2021-01-31 18:48 Sam James
2021-01-27 22:44 Sam James
2021-01-27 9:29 Sam James
2021-01-27 9:28 Sam James
2021-01-27 9:28 Sam James
2021-01-27 5:02 Sam James
2019-12-05 13:27 Lars Wendler
2019-12-05 12:26 Lars Wendler
2019-09-11 20:33 David Seifert
2019-09-11 9:38 Lars Wendler
2019-09-11 9:09 Lars Wendler
2019-04-20 17:57 Mikle Kolyada
2019-04-18 15:25 Lars Wendler
2019-04-18 15:25 Lars Wendler
2019-04-11 15:48 Pacho Ramos
2019-02-12 6:07 Markus Meier
2019-01-03 9:27 Sergei Trofimovich
2018-12-15 22:39 Sergei Trofimovich
2018-12-15 11:46 Mikle Kolyada
2018-12-14 22:48 Sergei Trofimovich
2018-12-14 2:13 Thomas Deutschmann
2017-11-23 14:49 Lars Wendler
2017-05-11 12:44 Michał Górny
2017-04-19 9:38 Lars Wendler
2017-01-31 16:06 Jeroen Roovers
2017-01-29 16:08 Fabian Groffen
2017-01-01 12:43 Agostino Sarubbo
2016-12-30 11:12 Agostino Sarubbo
2016-12-30 9:39 Agostino Sarubbo
2016-12-29 10:45 Agostino Sarubbo
2016-12-21 10:57 Tobias Klausmann
2016-11-16 21:15 Markus Meier
2016-10-26 17:02 Lars Wendler
2016-04-02 6:53 Fabian Groffen
2016-02-28 6:51 Matt Thode
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=1544827836.096b449e7002d65b1714e849490f6d61ac4d16f0.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