Report forwarded
to guix-patches@gnu.org: bug#76962; Package guix-patches.
(Tue, 11 Mar 2025 21:48:02 GMT) (full text, mbox, link).
Acknowledgement sent
to Zacchaeus Scheffer <eikcaz@zacchae.us>:
New bug report received and forwarded. Copy sent to guix-patches@gnu.org.
(Tue, 11 Mar 2025 21:48:02 GMT) (full text, mbox, link).
Subject: [PATCH] gnu: python-anyio: Disable keyboardinterrupt for
aarch64-linux native builds.
Date: Tue, 11 Mar 2025 17:47:47 -0400
From c9cc1e2f14034472ddbf6975301e52edb82eee49 Mon Sep 17 00:00:00 2001
From: Zacchaeus <eikcaz@zacchae.us>
Date: Mon, 10 Mar 2025 17:20:57 -0700
Subject: [PATCH] gnu: python-anyio: Disable keyboardinterrupt for
aarch64-linux native builds.
*gnu/packages/python-xyz.scm: (python-anyio): Disable keyboardinterrupt test
during native aarch64-linux builds.
Change-Id: I21a20262fdf6d538fd2deda5c42441695fa24eea
---
The python-anyio package already disables
`test_keyboardinterrupt_during_test` when cross-compiling to
aarch64-linux. This issue is not specific to cross-compilation and also
fails when natively compiling on aarch64-linux machines (--system=
instead of --target=). This patch adds support for natively building
python-anyio on aarch64-linux by disabling that test in such cases.
eikcaz-
gnu/packages/python-xyz.scm | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/gnu/packages/python-xyz.scm b/gnu/packages/python-xyz.scm
index 4cb7c72a82..887bceb53d 100644
--- a/gnu/packages/python-xyz.scm
+++ b/gnu/packages/python-xyz.scm
@@ -32272,7 +32272,8 @@ (define-public python-anyio
,@(cond
((or (target-aarch64?)
- (target-riscv64?))
+ (target-riscv64?)
+ (string=? "aarch64-linux" (%current-system)))
'(" and not test_keyboardinterrupt_during_test"))
(#t '()))
--
2.48.1
Information forwarded
to guix-patches@gnu.org: bug#76962; Package guix-patches.
(Sat, 15 Mar 2025 02:32:02 GMT) (full text, mbox, link).
I think there is something strange going on here that I don't
understand. I thought my patch fixed the issue, but in reality
python-anyio got substituted. I tried recreating the build failure (by
gc'ing the build and building with --no-substitutes), but then build
failed on one of it's dependencies. How can there be a substitute if
the build fails on my 64GiB ram machine? Regardless, I don't have the
bandwidth to investigate further. I don't know how to cancel/resolve
this issue (or if I have such a privilege), so someone else will have to
do that.
-Zacchae
Reply sent
to Sharlatan Hellseher <sharlatanus@gmail.com>:
You have taken responsibility.
(Wed, 19 Mar 2025 19:06:01 GMT) (full text, mbox, link).
Notification sent
to Zacchaeus Scheffer <eikcaz@zacchae.us>:
bug acknowledged by developer.
(Wed, 19 Mar 2025 19:06:02 GMT) (full text, mbox, link).
Hi,
To close the issue you may send an email with suffix done e.g.
76962-done@debbugs.gnu.org
Closing as not an issue.
VCS: https://github.incerto.xyz/;https://git.sr.ht/~hellseher/
GPG: 9847 81DE 689C 21C2 6418 0867 76D7 27BF F62C D2B5
… наш разум - превосходная объяснительная машина которая способна найти
смысл почти в чем угодно, истолковать любой феномен, но совершенно не в
состоянии принять мысль о непредсказуемости.
Debbugs is free software and licensed under the terms of the
GNU Public License version 2. The current version can be
obtained from https://bugs.debian.org/debbugs-source/.