From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-gfx/librecad/
Date: Sat, 2 Feb 2019 21:07:24 +0000 (UTC) [thread overview]
Message-ID: <1549141600.acfb6de0edf1e89d6258b73c7836afcfa9d36902.slyfox@gentoo> (raw)
commit: acfb6de0edf1e89d6258b73c7836afcfa9d36902
Author: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Sat Feb 2 21:06:40 2019 +0000
Commit: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Sat Feb 2 21:06:40 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=acfb6de0
media-gfx/librecad: keyworded 2.1.3-r4 for ppc64, bug #676870
Package-Manager: Portage-2.3.59, Repoman-2.3.12
RepoMan-Options: --include-arches="ppc64"
Signed-off-by: Sergei Trofimovich <slyfox <AT> gentoo.org>
media-gfx/librecad/librecad-2.1.3-r4.ebuild | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/media-gfx/librecad/librecad-2.1.3-r4.ebuild b/media-gfx/librecad/librecad-2.1.3-r4.ebuild
index 874bb483159..f5656b76120 100644
--- a/media-gfx/librecad/librecad-2.1.3-r4.ebuild
+++ b/media-gfx/librecad/librecad-2.1.3-r4.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2018 Gentoo Foundation
+# Copyright 1999-2019 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
EAPI=6
@@ -11,7 +11,7 @@ SRC_URI="https://github.com/LibreCAD/LibreCAD/archive/${PV/_/}.tar.gz -> ${P}.ta
LICENSE="GPL-2"
SLOT="0"
-KEYWORDS="amd64 x86 ~amd64-linux ~x86-linux"
+KEYWORDS="amd64 ~ppc64 x86 ~amd64-linux ~x86-linux"
IUSE="3d debug doc tools"
next reply other threads:[~2019-02-02 21:07 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-02 21:07 Sergei Trofimovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-25 7:31 [gentoo-commits] repo/gentoo:master commit in: media-gfx/librecad/ Yixun Lan
2024-09-22 7:20 Sam James
2024-09-22 7:20 Sam James
2024-06-30 0:00 Conrad Kostecki
2023-03-17 18:26 Sam James
2023-03-17 17:22 Sam James
2023-02-05 9:13 Joonas Niilola
2023-01-25 4:29 John Helmert III
2022-11-28 7:05 Joonas Niilola
2022-01-22 8:41 Yixun Lan
2021-05-09 19:12 Andreas Sturmlechner
2020-06-05 9:43 Andreas Sturmlechner
2020-05-29 7:39 Agostino Sarubbo
2020-05-20 12:25 Andreas Sturmlechner
2020-05-20 12:25 Andreas Sturmlechner
2019-08-15 19:47 Slawek Lis
2018-12-16 23:53 Andreas Sturmlechner
2018-09-09 8:27 Mikle Kolyada
2018-09-02 23:46 Thomas Deutschmann
2018-07-01 0:03 Andreas Sturmlechner
2018-06-03 13:49 Aaron Bauman
2018-01-22 8:40 Jeroen Roovers
2018-01-15 22:01 Andreas Sturmlechner
2018-01-15 22:01 Andreas Sturmlechner
2018-01-15 22:01 Andreas Sturmlechner
2018-01-15 19:03 Tobias Klausmann
2017-11-27 6:50 Slawek Lis
2017-11-18 13:08 Jeroen Roovers
2017-10-31 18:07 Andreas Hüttel
2017-10-26 18:54 Thomas Deutschmann
2016-11-22 6:37 Slawek Lis
2016-11-22 6:37 Slawek Lis
2016-04-07 20:25 Sergei Trofimovich
2016-01-19 8:34 Patrice Clement
2016-01-19 8:34 Patrice Clement
2016-01-19 8:34 Patrice Clement
2015-09-13 20:27 Anthony G. Basile
2015-09-13 19:24 Slawek Lis
2015-09-08 6:30 Slawek Lis
2015-09-02 5:56 Slawek Lis
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=1549141600.acfb6de0edf1e89d6258b73c7836afcfa9d36902.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