From: "Thomas Deutschmann" <whissi@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/nio4r/
Date: Wed, 3 Feb 2021 23:55:31 +0000 (UTC) [thread overview]
Message-ID: <1612396363.b35007ef773262e4cd3db19296f7d18927accab0.whissi@gentoo> (raw)
commit: b35007ef773262e4cd3db19296f7d18927accab0
Author: Thomas Deutschmann <whissi <AT> gentoo <DOT> org>
AuthorDate: Wed Feb 3 23:52:43 2021 +0000
Commit: Thomas Deutschmann <whissi <AT> gentoo <DOT> org>
CommitDate: Wed Feb 3 23:52:43 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b35007ef
dev-ruby/nio4r: x86 stable (bug #768432)
Package-Manager: Portage-3.0.14, Repoman-3.0.2
Signed-off-by: Thomas Deutschmann <whissi <AT> gentoo.org>
dev-ruby/nio4r/nio4r-2.5.4.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-ruby/nio4r/nio4r-2.5.4.ebuild b/dev-ruby/nio4r/nio4r-2.5.4.ebuild
index 635dfac5b37..45d18e60724 100644
--- a/dev-ruby/nio4r/nio4r-2.5.4.ebuild
+++ b/dev-ruby/nio4r/nio4r-2.5.4.ebuild
@@ -17,7 +17,7 @@ HOMEPAGE="https://github.com/socketry/nio4r"
LICENSE="MIT || ( BSD GPL-2 )"
SLOT="2"
-KEYWORDS="~amd64 ~arm ~arm64 ~hppa ~ppc ~ppc64 ~sparc ~x86 ~ppc-macos ~x64-macos ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
+KEYWORDS="~amd64 ~arm ~arm64 ~hppa ~ppc ~ppc64 ~sparc x86 ~ppc-macos ~x64-macos ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
IUSE=""
# Note that nio4r bundles a patched copy of libev, and without these
next reply other threads:[~2021-02-03 23:55 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-03 23:55 Thomas Deutschmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-30 6:17 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/nio4r/ Hans de Graaff
2024-10-29 6:25 Hans de Graaff
2024-10-29 6:25 Hans de Graaff
2024-10-06 13:30 Jakov Smolić
2024-10-06 11:18 Sam James
2024-07-15 8:33 Hans de Graaff
2024-03-21 6:42 Hans de Graaff
2024-02-29 0:50 Sam James
2023-12-31 14:36 Hans de Graaff
2023-12-31 14:36 Hans de Graaff
2023-12-01 6:18 Hans de Graaff
2023-11-21 6:40 Hans de Graaff
2023-11-17 7:46 Hans de Graaff
2023-11-17 7:46 Hans de Graaff
2023-04-03 0:47 Sam James
2023-04-03 0:47 Sam James
2022-12-03 7:43 Hans de Graaff
2022-04-02 8:03 Agostino Sarubbo
2022-03-31 12:33 Jakov Smolić
2022-03-31 6:15 Hans de Graaff
2021-11-08 2:51 Yixun Lan
2021-10-28 5:27 Hans de Graaff
2021-08-04 6:41 Hans de Graaff
2021-05-10 4:35 Hans de Graaff
2021-03-04 6:55 Hans de Graaff
2021-02-13 7:55 Hans de Graaff
2021-02-06 6:59 Hans de Graaff
2021-02-04 7:58 Agostino Sarubbo
2021-02-03 6:45 Hans de Graaff
2020-09-16 5:55 Hans de Graaff
2020-09-11 5:14 Hans de Graaff
2020-09-08 5:48 Hans de Graaff
2020-09-05 8:01 Hans de Graaff
2020-05-31 8:19 Sergei Trofimovich
2020-04-25 12:44 Sergei Trofimovich
2020-04-15 21:49 Sergei Trofimovich
2020-04-14 21:06 Sergei Trofimovich
2020-02-29 6:00 Hans de Graaff
2020-02-29 6:00 Hans de Graaff
2019-09-25 6:11 Hans de Graaff
2019-08-29 5:24 Hans de Graaff
2019-08-29 5:24 Hans de Graaff
2019-08-28 5:15 Hans de Graaff
2019-07-24 23:16 Aaron Bauman
2019-07-08 4:24 Hans de Graaff
2019-01-31 7:35 Hans de Graaff
2019-01-31 7:35 Hans de Graaff
2018-05-03 4:48 Hans de Graaff
2018-04-19 19:37 Hans de Graaff
2018-04-19 19:37 Hans de Graaff
2018-03-25 17:58 Sergei Trofimovich
2018-03-18 6:25 Hans de Graaff
2018-02-07 5:52 Thomas Deutschmann
2017-12-28 6:34 Hans de Graaff
2017-09-12 8:18 Sergei Trofimovich
2017-08-26 8:27 Hans de Graaff
2017-08-26 8:27 Hans de Graaff
2017-06-21 7:27 Hans de Graaff
2017-05-29 4:31 Hans de Graaff
2017-04-16 6:40 Hans de Graaff
2017-01-31 7:05 Hans de Graaff
2016-07-21 17:36 Hans de Graaff
2016-03-22 21:58 Manuel Rüger
2016-02-02 6:25 Hans de Graaff
2015-12-24 6:37 Hans de Graaff
2015-12-24 6:37 Hans de Graaff
2015-12-06 7:05 Hans de Graaff
2015-12-05 13:01 Markus Meier
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=1612396363.b35007ef773262e4cd3db19296f7d18927accab0.whissi@gentoo \
--to=whissi@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