From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-libs/libcdr/
Date: Sat, 23 Feb 2019 12:55:10 +0000 (UTC) [thread overview]
Message-ID: <1550926499.f3f3038927cd0252c976d3964480d7a9d94745d3.slyfox@gentoo> (raw)
commit: f3f3038927cd0252c976d3964480d7a9d94745d3
Author: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Sat Feb 23 12:00:57 2019 +0000
Commit: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Sat Feb 23 12:54:59 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f3f30389
media-libs/libcdr: stable 0.1.5 for ppc64, bug #676956
Package-Manager: Portage-2.3.62, Repoman-2.3.12
RepoMan-Options: --include-arches="ppc64"
Signed-off-by: Sergei Trofimovich <slyfox <AT> gentoo.org>
media-libs/libcdr/libcdr-0.1.5.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/media-libs/libcdr/libcdr-0.1.5.ebuild b/media-libs/libcdr/libcdr-0.1.5.ebuild
index aeb6e753da5..a6d334edc82 100644
--- a/media-libs/libcdr/libcdr-0.1.5.ebuild
+++ b/media-libs/libcdr/libcdr-0.1.5.ebuild
@@ -10,7 +10,7 @@ if [[ ${PV} = 9999 ]]; then
inherit autotools git-r3
else
SRC_URI="https://dev-www.libreoffice.org/src/libcdr/${P}.tar.xz"
- KEYWORDS="amd64 ~arm ~arm64 ~hppa ~ppc ~ppc64 ~sparc x86"
+ KEYWORDS="amd64 ~arm ~arm64 ~hppa ~ppc ppc64 ~sparc x86"
fi
DESCRIPTION="Library parsing the Corel cdr documents"
next reply other threads:[~2019-02-23 12:55 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-23 12:55 Sergei Trofimovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-01-13 0:25 [gentoo-commits] repo/gentoo:master commit in: media-libs/libcdr/ Sam James
2025-01-13 0:25 Sam James
2025-01-13 0:25 Sam James
2025-01-13 0:25 Sam James
2025-01-13 0:25 Sam James
2024-11-28 22:51 Andreas Sturmlechner
2024-11-28 22:51 Andreas Sturmlechner
2021-08-12 3:10 Yixun Lan
2021-06-01 10:48 Sam James
2021-06-01 9:00 Sam James
2021-05-31 22:38 Sam James
2021-05-31 22:38 Sam James
2021-03-28 13:21 Andreas Sturmlechner
2020-10-31 11:05 David Seifert
2020-05-31 21:09 Andreas Sturmlechner
2020-05-31 16:07 Mikle Kolyada
2020-05-31 15:45 Mikle Kolyada
2020-05-31 15:40 Mikle Kolyada
2020-05-20 13:35 Mikle Kolyada
2020-05-19 19:36 Mikle Kolyada
2020-03-08 18:56 Andreas Sturmlechner
2020-03-08 18:56 Andreas Sturmlechner
2019-07-31 21:11 Aaron Bauman
2019-04-28 21:41 Andreas Sturmlechner
2019-04-28 7:42 Sergei Trofimovich
2019-02-17 17:58 Mikle Kolyada
2019-02-17 15:33 Mikle Kolyada
2018-12-30 20:08 Andreas Sturmlechner
2018-08-29 6:15 Sergei Trofimovich
2018-03-04 22:30 Sergei Trofimovich
2018-02-19 19:42 David Seifert
2017-11-19 23:49 Andreas Sturmlechner
2017-11-14 14:13 Manuel Rüger
2017-11-11 9:27 Sergei Trofimovich
2017-10-08 19:08 Andreas Sturmlechner
2017-08-27 15:34 Michael Palimaka
2017-08-17 17:06 Michał Górny
2017-08-02 6:31 Andreas Sturmlechner
2017-07-30 20:46 Andreas Sturmlechner
2017-07-26 8:20 Sergei Trofimovich
2017-06-28 19:11 Andreas Sturmlechner
2016-12-17 15:57 Andreas Hüttel
2016-08-10 14:59 Lars Wendler
2016-07-03 20:27 Andreas Hüttel
2016-02-18 19:21 Michał Górny
2016-02-18 19:21 Michał Górny
2016-02-16 22:07 Manuel Rüger
2016-01-23 8:00 Jeroen Roovers
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=1550926499.f3f3038927cd0252c976d3964480d7a9d94745d3.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