From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: x11-libs/libfm-qt/
Date: Thu, 27 Jun 2019 07:29:40 +0000 (UTC) [thread overview]
Message-ID: <1561620535.953c8b958beca3dd6b79f2f1e949b4454e4e9aa7.slyfox@gentoo> (raw)
commit: 953c8b958beca3dd6b79f2f1e949b4454e4e9aa7
Author: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Thu Jun 27 07:28:55 2019 +0000
Commit: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Thu Jun 27 07:28:55 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=953c8b95
x11-libs/libfm-qt: keyworded 0.14.1-r2 for ppc64, bug #676874
Package-Manager: Portage-2.3.67, Repoman-2.3.16
RepoMan-Options: --include-arches="ppc64"
Signed-off-by: Sergei Trofimovich <slyfox <AT> gentoo.org>
x11-libs/libfm-qt/libfm-qt-0.14.1-r2.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/x11-libs/libfm-qt/libfm-qt-0.14.1-r2.ebuild b/x11-libs/libfm-qt/libfm-qt-0.14.1-r2.ebuild
index 2305e06f36f..100cff14a7f 100644
--- a/x11-libs/libfm-qt/libfm-qt-0.14.1-r2.ebuild
+++ b/x11-libs/libfm-qt/libfm-qt-0.14.1-r2.ebuild
@@ -13,7 +13,7 @@ if [[ "${PV}" == "9999" ]]; then
EGIT_REPO_URI="https://github.com/lxqt/${PN}.git"
else
SRC_URI="https://downloads.lxqt.org/downloads/${PN}/${PV}/${P}.tar.xz"
- KEYWORDS="amd64 ~arm ~arm64 x86"
+ KEYWORDS="amd64 ~arm ~arm64 ~ppc64 x86"
fi
LICENSE="GPL-2+ LGPL-2.1+"
next reply other threads:[~2019-06-27 7:29 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-27 7:29 Sergei Trofimovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-07 23:12 [gentoo-commits] repo/gentoo:master commit in: x11-libs/libfm-qt/ Jimi Huotari
2024-07-13 10:09 Yixun Lan
2024-07-11 19:44 Arthur Zamarin
2024-06-16 18:30 Jimi Huotari
2024-06-16 18:30 Jimi Huotari
2023-12-27 21:03 Sam James
2023-12-20 1:40 Sam James
2023-12-17 23:55 Ionen Wolkens
2023-11-10 13:59 Arthur Zamarin
2023-11-10 12:26 Arthur Zamarin
2023-11-10 12:26 Arthur Zamarin
2023-11-10 12:01 Arthur Zamarin
2023-11-10 10:07 Yixun Lan
2023-11-09 21:45 Jimi Huotari
2023-06-18 14:53 Andreas Sturmlechner
2023-05-29 21:57 Sam James
2023-05-29 11:05 Arthur Zamarin
2023-05-29 0:10 Sam James
2022-12-17 19:28 Arthur Zamarin
2022-12-16 21:50 Sam James
2022-12-16 20:33 Arthur Zamarin
2022-11-10 12:57 Jimi Huotari
2022-07-26 7:05 Sam James
2022-07-22 17:54 Sam James
2022-07-20 5:36 Sam James
2022-04-15 13:14 Arthur Zamarin
2022-04-15 6:17 Sam James
2021-09-30 17:24 Andreas Sturmlechner
2021-07-11 20:51 Sam James
2021-07-10 0:48 Sam James
2021-01-23 22:55 Sam James
2021-01-21 9:03 Agostino Sarubbo
2020-07-31 16:35 Mikle Kolyada
2020-07-31 16:33 Mikle Kolyada
2019-06-28 1:17 Andreas Sturmlechner
2019-06-26 8:32 Agostino Sarubbo
2019-06-26 6:50 Agostino Sarubbo
2019-06-22 11:44 Andreas Sturmlechner
2019-05-23 12:30 Mikle Kolyada
2019-05-22 7:30 Mikle Kolyada
2019-03-12 19:37 Andreas Sturmlechner
2019-03-12 19:37 Andreas Sturmlechner
2018-12-22 11:43 Andreas Sturmlechner
2018-10-17 14:41 Andreas Sturmlechner
2018-10-17 12:30 Thomas Deutschmann
2018-10-16 13:08 Mikle Kolyada
2018-08-11 10:10 Jonathan Scruggs
2018-01-22 18:29 Markus Meier
2017-12-11 0:45 Anthony G. Basile
2017-07-19 21:32 Alexis Ballier
2016-10-29 13:51 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=1561620535.953c8b958beca3dd6b79f2f1e949b4454e4e9aa7.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