From: normally_js <normally_js@posteo.net>
To: Tanguy LE CARROUR <tanguy@bioneland.org>, 69867@debbugs.gnu.org
Subject: [bug#69867] [PATCH 1/2] gnu: Add python-noiseprotocol.
Date: Thu, 21 Mar 2024 18:59:15 +0000 [thread overview]
Message-ID: <55c45f96-e664-674c-42c2-0502591eeed0@posteo.net> (raw)
In-Reply-To: <171101047539.12926.16325090825361818580@bioneland.org>
Short answer: I don't know how to disable specific tests within the
python-build-system, but since we already have a solution that works it
likely doesn't matter.
But I'd assume that getting tests to pass is better than being forced to
disable them and python-team should *not* be affected by this addition.
---
normalmente
On 3/21/24 04:41, Tanguy LE CARROUR wrote:
> Hi normalmente,
>
> Quoting normalmente (2024-03-20 19:55:49)
>> * gnu/packages/magic-wormhole.scm (magic-wormhole): Update to 0.13.0.
>> [arguments]: Skip tests. Add gexps.
>>
>> Change-Id: I8502f38d7d0e4bf7a9b03c466c761f5a95157cb2
>> […]
>> * gnu/packages/python-web.scm (python-noiseprotocol): New variable.
>>
>> Change-Id: Id62f22f9fd3f019beded5ce5c0fe9123c34f8bb2
> This looks good to me.
> It might be worth disabling only the one failing test, though!?
>
> Regards,
>
next prev parent reply other threads:[~2024-03-21 19:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-17 20:15 [bug#69867] [PATCH] gnu: magic-wormhole: Update to 0.13.0 normalmente
2024-03-20 14:49 ` Christopher Baines
2024-03-20 18:52 ` [bug#69867] [PATCH 0/2] " normalmente
2024-03-20 18:55 ` [bug#69867] [PATCH 1/2] gnu: Add python-noiseprotocol normalmente
2024-03-21 8:41 ` Tanguy LE CARROUR
2024-03-21 18:59 ` normally_js [this message]
2024-03-22 9:32 ` Tanguy LE CARROUR
2024-03-24 19:43 ` Munyoki Kilyungi
2024-03-20 18:55 ` [bug#69867] [PATCH 2/2] gnu: magic-wormhole: Update to 0.13.0 normalmente
2024-03-23 21:03 ` bug#69867: [PATCH] " Sharlatan Hellseher
2024-04-14 19:42 ` [bug#69867] Close: current Guix already has successor version (0.14.0) of this package Dale Mellor
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55c45f96-e664-674c-42c2-0502591eeed0@posteo.net \
--to=normally_js@posteo.net \
--cc=69867@debbugs.gnu.org \
--cc=tanguy@bioneland.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).