From: "Ludovic Courtès" <ludo@gnu.org>
To: Marius Bakke <mbakke@fastmail.com>
Cc: 37838-done@debbugs.gnu.org
Subject: [bug#37838] [PATCH 0/2] Rewrite (guix cve) to read NIST's JSON feed
Date: Fri, 25 Oct 2019 18:18:37 +0200 [thread overview]
Message-ID: <877e4spzmq.fsf@gnu.org> (raw)
In-Reply-To: <871rv3xt38.fsf@devup.no> (Marius Bakke's message of "Wed, 23 Oct 2019 19:35:55 +0200")
Hi Marius,
Marius Bakke <mbakke@fastmail.com> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
>
>> Hello,
>>
>> Ludovic Courtès <ludo@gnu.org> skribis:
>>
>>> cve: Rewrite to read the JSON feed instead of the XML feed.
>>> lint: Re-enable CVE checker.
>>
>> Pushed as 9efa2c28a4f842b7ca1977e084299de441842856.
>>
>> Please let me know if you notice anything fishy with ‘guix lint -c cve’:
>> CVEs not showing up, CVEs showing up that should not, etc.
>
> Here is what I get (on ee42e9f9f):
>
> $ ./pre-inst-env guix lint -c cve ao
> fetching CVE database for 2019...]...
> Backtrace:
> 11 (apply-smob/1 #<catch-closure 7f08d6d9d900>)
> In ice-9/boot-9.scm:
> 705:2 10 (call-with-prompt _ _ #<procedure default-prompt-handler (k proc)>)
> In ice-9/eval.scm:
> 619:8 9 (_ #(#(#<directory (guile-user) 7f08d6a23140>)))
> In guix/ui.scm:
> 1730:12 8 (run-guix-command _ . _)
> In srfi/srfi-1.scm:
> 640:9 7 (for-each #<procedure 7f08d689f3c0 at guix/scripts/lint.scm:168:16 (spec)> ("ao"))
> In guix/scripts/lint.scm:
> 57:4 6 (run-checkers _ _)
> In srfi/srfi-1.scm:
> 640:9 5 (for-each #<procedure 7f08c7706480 at guix/scripts/lint.scm:57:14 (checker)> (#<<lint-checker> name: c…>))
> In guix/scripts/lint.scm:
> 64:17 4 (_ _)
> In guix/lint.scm:
> 999:4 3 (check-vulnerabilities _)
> 994:9 2 (_ _)
> In unknown file:
> 1 (force #<promise #<procedure 7f08d42e7928 at guix/lint.scm:982:16 ()>>)
> In guix/lint.scm:
> 983:24 0 (_)
>
> guix/lint.scm:983:24: Throw to key `srfi-34' with args `(#<condition &message [message: "invalid CVE feed"] 7f08b5a39920>)'.
>
> I tried downloading the .json.gz files manually and they seem fine.
I don’t encounter this problem. Is it reproducible for you?
Thanks,
Ludo’.
next prev parent reply other threads:[~2019-10-25 16:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-20 20:34 [bug#37838] [PATCH 0/2] Rewrite (guix cve) to read NIST's JSON feed Ludovic Courtès
2019-10-20 21:20 ` [bug#37838] [PATCH 1/2] cve: Rewrite to read the JSON feed instead of the XML feed Ludovic Courtès
2019-10-20 21:20 ` [bug#37838] [PATCH 2/2] lint: Re-enable CVE checker Ludovic Courtès
2019-10-23 14:48 ` bug#37838: [PATCH 0/2] Rewrite (guix cve) to read NIST's JSON feed Ludovic Courtès
2019-10-23 16:46 ` [bug#37838] " Efraim Flashner
2019-10-23 17:35 ` Marius Bakke
2019-10-25 16:18 ` Ludovic Courtès [this message]
2019-11-03 17:29 ` Marius Bakke
2019-11-04 17:32 ` Ludovic Courtès
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=877e4spzmq.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=37838-done@debbugs.gnu.org \
--cc=mbakke@fastmail.com \
/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.