unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Palmer Dabbelt <palmer@rivosinc.com>
To: libc-alpha@sourceware.org
Cc: Palmer Dabbelt <palmer@rivosinc.com>
Subject: [PATCH] Don't check signatures in build-many-glibcs.py
Date: Fri, 12 Jan 2024 10:58:46 -0800	[thread overview]
Message-ID: <20240112185846.24483-1-palmer@rivosinc.com> (raw)

I sign commits and have signature verification on in git.  Maybe that's
a bad idea because it trips up a bunch of scripts, but it's pretty easy
to just force skipping signature verification here.

Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>
---
 scripts/build-many-glibcs.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/scripts/build-many-glibcs.py b/scripts/build-many-glibcs.py
index ec2ded6e56..f9cf14c94d 100755
--- a/scripts/build-many-glibcs.py
+++ b/scripts/build-many-glibcs.py
@@ -931,7 +931,7 @@ class Context(object):
             if self.replace_sources:
                 subprocess.run(['git', 'clean', '-dxfq'],
                                cwd=self.component_srcdir(component), check=True)
-            subprocess.run(['git', 'pull', '-q'],
+            subprocess.run(['git', 'pull', '-q', '--no-verify-signatures'],
                            cwd=self.component_srcdir(component), check=True)
         else:
             if self.shallow:
-- 
2.43.0


             reply	other threads:[~2024-01-12 18:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-12 18:58 Palmer Dabbelt [this message]
2024-03-06 10:39 ` [PATCH] Don't check signatures in build-many-glibcs.py Simon Chopin
2024-03-07 20:44   ` Carlos O'Donell
2024-03-13  0:11     ` Palmer Dabbelt

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://www.gnu.org/software/libc/involved.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240112185846.24483-1-palmer@rivosinc.com \
    --to=palmer@rivosinc.com \
    --cc=libc-alpha@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).