From: "Michael Palimaka" <kensington@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-misc/ddcutil/
Date: Tue, 10 Oct 2017 13:50:47 +0000 (UTC) [thread overview]
Message-ID: <1507643437.bb2b107901f7c30b97f40ffa91923b9fea049473.kensington@gentoo> (raw)
commit: bb2b107901f7c30b97f40ffa91923b9fea049473
Author: Michael Palimaka <kensington <AT> gentoo <DOT> org>
AuthorDate: Tue Oct 10 13:50:24 2017 +0000
Commit: Michael Palimaka <kensington <AT> gentoo <DOT> org>
CommitDate: Tue Oct 10 13:50:37 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=bb2b1079
app-misc/ddcutil: add ~arm keyword
Tested on Raspberry Pi 2.
Bug: https://bugs.gentoo.org/627932
Package-Manager: Portage-2.3.8, Repoman-2.3.3
app-misc/ddcutil/ddcutil-0.8.4.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/app-misc/ddcutil/ddcutil-0.8.4.ebuild b/app-misc/ddcutil/ddcutil-0.8.4.ebuild
index 5942efa23a3..2da92097097 100644
--- a/app-misc/ddcutil/ddcutil-0.8.4.ebuild
+++ b/app-misc/ddcutil/ddcutil-0.8.4.ebuild
@@ -19,7 +19,7 @@ IUSE="usb-monitor user-permissions video_cards_nvidia"
LICENSE="GPL-2"
SLOT="0"
-KEYWORDS="~amd64 ~x86"
+KEYWORDS="~amd64 ~arm ~x86"
RDEPEND="x11-libs/libXrandr
x11-libs/libX11
next reply other threads:[~2017-10-10 13:50 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-10 13:50 Michael Palimaka [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-26 2:18 [gentoo-commits] repo/gentoo:master commit in: app-misc/ddcutil/ Sam James
2025-04-26 2:14 Sam James
2025-04-26 2:14 Sam James
2025-04-26 1:17 Sam James
2025-04-26 1:06 Sam James
2025-02-27 16:04 Sam James
2025-02-27 6:05 Sam James
2025-02-26 4:50 Sam James
2025-01-08 9:37 Nowa Ammerlaan
2024-10-30 19:59 Sam James
2024-10-27 6:50 Arthur Zamarin
2024-10-25 21:25 Sam James
2024-10-25 21:25 Sam James
2024-10-25 21:25 Sam James
2024-02-24 11:32 Andrew Ammerlaan
2024-02-24 11:32 Andrew Ammerlaan
2024-02-17 21:17 Sam James
2024-02-08 9:06 Andrew Ammerlaan
2024-02-08 9:06 Andrew Ammerlaan
2024-02-01 9:41 Andrew Ammerlaan
2024-02-01 9:41 Andrew Ammerlaan
2024-01-22 13:43 Andrew Ammerlaan
2023-12-11 7:31 Andrew Ammerlaan
2023-12-01 18:58 Arthur Zamarin
2023-11-24 9:37 Andrew Ammerlaan
2023-11-24 9:37 Andrew Ammerlaan
2023-06-30 21:14 Sam James
2023-06-30 21:14 Sam James
2023-06-30 21:14 Sam James
2023-06-30 19:30 Sam James
2023-06-30 19:19 Sam James
2022-08-28 5:06 WANG Xuerui
2022-04-15 5:30 Sam James
2022-04-15 5:00 Robin H. Johnson
2022-02-21 19:47 Andrew Ammerlaan
2022-02-21 19:47 Andrew Ammerlaan
2022-01-10 11:47 Andrew Ammerlaan
2022-01-10 11:47 Andrew Ammerlaan
2021-08-18 0:35 Yixun Lan
2021-07-09 22:48 Conrad Kostecki
2021-07-09 22:48 Conrad Kostecki
2021-07-09 22:36 Conrad Kostecki
2021-07-09 22:36 Conrad Kostecki
2020-07-30 23:07 Robin H. Johnson
2020-05-18 22:39 Georgy Yakovlev
2019-07-15 23:16 Manuel Rüger
2019-07-15 23:16 Manuel Rüger
2019-02-26 20:54 Andreas Sturmlechner
2018-08-04 17:48 Jonathan Scruggs
2018-08-04 16:31 Jonathan Scruggs
2018-01-27 17:19 Jonathan Scruggs
2018-01-26 13:03 Jeroen Roovers
2018-01-25 21:35 Jonathan Scruggs
2017-09-23 8:38 David Seifert
2017-08-16 21:00 Michał Górny
2017-08-16 21:00 Michał Górny
2017-01-29 17:09 Michael Palimaka
2017-01-29 17:09 Michael Palimaka
2017-01-15 11:14 David Seifert
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=1507643437.bb2b107901f7c30b97f40ffa91923b9fea049473.kensington@gentoo \
--to=kensington@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