From: "Gábor Boskovits" <boskovits@gmail.com>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Guix master: Lint warnings: inputs which should be native-inputs etc
Date: Tue, 24 Mar 2020 13:38:46 +0100 [thread overview]
Message-ID: <CAE4v=piSO+-SzPhYx5_iJ9UUWxEzk9EBB6i4aaGNvsC_6Og5dA@mail.gmail.com> (raw)
In-Reply-To: <20200323110148.1b533f03@scratchpost.org>
[-- Attachment #1: Type: text/plain, Size: 1426 bytes --]
Hello,
Danny Milosavljevic <dannym@scratchpost.org> ezt írta (időpont: 2020. márc.
23., Hét 11:02):
> Hi,
>
> so I've been using the Guix Data Service and it found a whole load of
> linter
> warnings. 150 warnings for inputs that should probably be native inputs:
>
>
> http://data.guix.gnu.org/revision/d4842a7c478230b7c12e65d04106db1e14c98cac/lint-warnings?package_query=&linter=inputs-should-be-native&message_query=&field=linter&field=message&field=location
This is just a related question: do we have a way to tell the linter that
this should be ignored, and to tell it that this package is affected by
something that the linter can not see.
One example is when something usually is a native input, but for the
package considered it really should be input.
Another example is security fixing. We might fix something by a patch, and
mark the package not affected, and conversely, we might have to carry a
vulnerable patch to a version otherwise not affected. Wdyt?
>
>
> It also found some more:
>
> http://data.guix.gnu.org/revision/d4842a7c478230b7c12e65d04106db1e14c98cac
>
> For example 176 unstable tarballs.
>
> And 7 inputs should not be inputs, all of them python-setuptools, in:
>
> python2-virtualenv
> python-get-version
> python-jaraco-packaging
> python-legacy-api-wrap
> python-sphinx-copybutton
> python-virtualenv
> tensorflow
>
Best regards,
g_bor
>
[-- Attachment #2: Type: text/html, Size: 2589 bytes --]
prev parent reply other threads:[~2020-03-24 12:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 10:01 Guix master: Lint warnings: inputs which should be native-inputs etc Danny Milosavljevic
2020-03-24 12:38 ` Gábor Boskovits [this message]
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='CAE4v=piSO+-SzPhYx5_iJ9UUWxEzk9EBB6i4aaGNvsC_6Og5dA@mail.gmail.com' \
--to=boskovits@gmail.com \
--cc=dannym@scratchpost.org \
--cc=guix-devel@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.