From: Michael Trimarchi <michael@amarulasolutions.com>
To: buildroot@buildroot.org
Cc: Michael Trimarchi <michael@amarulasolutions.com>
Subject: [Buildroot] [PATCH 1/2] scripts/cve: Avoid to do a complete clone of cve git repository
Date: Mon, 2 Sep 2024 09:41:08 +0200 [thread overview]
Message-ID: <20240902074109.50173-1-michael@amarulasolutions.com> (raw)
Just a simple clone --depth 1 should be enough to parse the
cve and generate the pkg-stats report. The space now does
not take in account of the full history and only use 2.2Gb
Signed-off-by: Michael Trimarchi <michael@amarulasolutions.com>
---
support/scripts/cve.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/support/scripts/cve.py b/support/scripts/cve.py
index e25825581e..7d115a28b5 100755
--- a/support/scripts/cve.py
+++ b/support/scripts/cve.py
@@ -82,7 +82,7 @@ class CVE:
# happily clones into an empty directory.
os.makedirs(nvd_git_dir)
subprocess.check_call(
- ["git", "clone", NVD_BASE_URL, nvd_git_dir],
+ ["git", "clone", "--depth", "1", NVD_BASE_URL, nvd_git_dir],
stdout=subprocess.DEVNULL,
stderr=subprocess.DEVNULL,
)
--
2.43.0
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2024-09-02 7:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-02 7:41 Michael Trimarchi [this message]
2024-09-02 7:41 ` [Buildroot] [PATCH 2/2] scripts/cve: Restart the clone if the pull generate an exception Michael Trimarchi
2024-09-02 16:41 ` Yann E. MORIN
2024-09-02 16:44 ` Michael Nazzareno Trimarchi
2024-09-02 16:39 ` [Buildroot] [PATCH 1/2] scripts/cve: Avoid to do a complete clone of cve git repository Yann E. MORIN
2024-09-02 16:43 ` Michael Nazzareno Trimarchi
2024-09-02 16:53 ` Michael Nazzareno Trimarchi
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=20240902074109.50173-1-michael@amarulasolutions.com \
--to=michael@amarulasolutions.com \
--cc=buildroot@buildroot.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox