all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tanguy Le Carrour <tanguy@bioneland.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Hartmut Goebel <h.goebel@crazy-compilers.com>,
	42390-done@debbugs.gnu.org
Subject: [bug#42390] [PATCH] gnu: Add python-mamba.
Date: Wed, 29 Jul 2020 08:52:16 +0200	[thread overview]
Message-ID: <20200729065216.nqn5zz7ckkpxzq7h@rafflesia> (raw)
In-Reply-To: <87bljzs3qp.fsf@gnu.org>

Hi,

Le 07/28, Ludovic Courtès a écrit :
> Tanguy Le Carrour <tanguy@bioneland.org> skribis:
> 
> > The question is now: is it possible to make the warning go away by
> > marking it as being an "exception" in the package definition?
> > Are comments "part of the code" and be used for that? Can we use a
> > different package name (`python-coverage-propagated`) that would not
> > be in the list?
> 
> We could use a property, similar to how the ‘lint-hidden-cve’ property
> is handled by the ‘cve’ linter.

Sounds great! … unless you expected me to implement it! ^_^'
I guesse `check-inputs-should-be-native` should look a bit like
`check-vulnerabilities`, but I have no idea how to do that! Sorry!

-- 
Tanguy




  reply	other threads:[~2020-07-29  6:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-16 12:25 [bug#42390] [PATCH] gnu: Add python-mamba Tanguy Le Carrour
2020-07-21 16:41 ` bug#42390: " Ludovic Courtès
2020-07-22  7:36   ` [bug#42390] " Tanguy Le Carrour
2020-07-22 10:38     ` Ludovic Courtès
2020-07-23 19:19       ` Hartmut Goebel
2020-07-24  6:36         ` Tanguy Le Carrour
2020-07-24 13:14         ` Ludovic Courtès
2020-07-27  7:47           ` Hartmut Goebel
2020-07-27  8:10             ` Tanguy Le Carrour
2020-07-28 21:56               ` Ludovic Courtès
2020-07-29  6:52                 ` Tanguy Le Carrour [this message]
2020-07-31  6:42 ` Tanguy Le Carrour

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=20200729065216.nqn5zz7ckkpxzq7h@rafflesia \
    --to=tanguy@bioneland.org \
    --cc=42390-done@debbugs.gnu.org \
    --cc=h.goebel@crazy-compilers.com \
    --cc=ludo@gnu.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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.