public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "WANG Xuerui" <xen0n@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/libaio/
Date: Fri,  6 May 2022 02:44:43 +0000 (UTC)	[thread overview]
Message-ID: <1651804978.0bff66aa557328cb5418ca777703c88e34e811c9.xen0n@gentoo> (raw)

commit:     0bff66aa557328cb5418ca777703c88e34e811c9
Author:     WANG Xuerui <xen0n <AT> gentoo <DOT> org>
AuthorDate: Fri May  6 02:42:56 2022 +0000
Commit:     WANG Xuerui <xen0n <AT> gentoo <DOT> org>
CommitDate: Fri May  6 02:42:58 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0bff66aa

dev-libs/libaio: keyword 0.3.113 for ~loong

This is the first version with out-of-the-box loong support, and the
testcase failing on abi_x86_32 passed on loong. Another test failed on
loong (testcase 5), but the library is working nevertheless.
Keywording because we have no other choice on loong.

Signed-off-by: WANG Xuerui <xen0n <AT> gentoo.org>

 dev-libs/libaio/libaio-0.3.113.ebuild | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/dev-libs/libaio/libaio-0.3.113.ebuild b/dev-libs/libaio/libaio-0.3.113.ebuild
index 1f2cb960692f..c72cf7a83a27 100644
--- a/dev-libs/libaio/libaio-0.3.113.ebuild
+++ b/dev-libs/libaio/libaio-0.3.113.ebuild
@@ -15,7 +15,8 @@ else
 	# Has test failure on abi_x86_32 which needs investigating
 	# https://marc.info/?l=linux-aio&m=164996470108464&w=2
 	# https://pagure.io/libaio/issue/21
-	#KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~m68k ~mips ~ppc ~ppc64 ~riscv ~s390 ~sparc ~x86 ~amd64-linux ~x86-linux"
+	#KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~loong ~m68k ~mips ~ppc ~ppc64 ~riscv ~s390 ~sparc ~x86 ~amd64-linux ~x86-linux"
+	KEYWORDS="~loong"
 fi
 LICENSE="LGPL-2"
 SLOT="0"


             reply	other threads:[~2022-05-06  2:44 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-06  2:44 WANG Xuerui [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-05-30 16:12 [gentoo-commits] repo/gentoo:master commit in: dev-libs/libaio/ Arthur Zamarin
2025-04-13 21:30 Sam James
2024-04-12  6:26 Arthur Zamarin
2024-04-12  6:26 Arthur Zamarin
2024-03-24 11:29 Sam James
2024-03-24 11:29 Sam James
2024-02-20  5:14 Sam James
2022-10-15  3:11 Sam James
2022-09-27  7:10 Agostino Sarubbo
2022-09-26  6:37 Arthur Zamarin
2022-09-26  6:24 Arthur Zamarin
2022-09-26  6:24 Arthur Zamarin
2022-09-25  7:28 Arthur Zamarin
2022-09-25  6:19 Agostino Sarubbo
2022-09-25  4:43 Sam James
2022-09-25  4:37 Sam James
2022-08-24  7:04 Sam James
2022-05-02  2:09 Sam James
2022-04-21 20:25 Sam James
2022-03-26  0:09 Sam James
2022-03-26  0:01 Sam James
2020-09-07  0:53 Sam James
2020-08-29 14:48 Thomas Deutschmann
2020-08-28 22:21 Sergei Trofimovich
2020-08-24 17:33 Sergei Trofimovich
2020-08-23  6:51 Sam James
2020-08-22  5:43 Agostino Sarubbo
2020-08-21 18:20 Agostino Sarubbo
2019-06-04  0:07 Thomas Deutschmann
2019-05-05 20:09 Mikle Kolyada
2019-04-24 22:54 Thomas Deutschmann
2019-04-24 22:39 Göktürk Yüksek
2017-02-23  2:30 Göktürk Yüksek
2016-05-22 17:09 Göktürk Yüksek
2016-04-23 18:13 Patrice Clement
2016-04-23  7:59 Patrice Clement

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=1651804978.0bff66aa557328cb5418ca777703c88e34e811c9.xen0n@gentoo \
    --to=xen0n@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