From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on starla X-Spam-Level: X-Spam-Status: No, score=-1.3 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 Received: from server2.sourceware.org (server2.sourceware.org [IPv6:2620:52:3:1:0:246e:9693:128c]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 976B51F44D for ; Mon, 18 Mar 2024 16:08:34 +0000 (UTC) Authentication-Results: dcvr.yhbt.net; dkim=pass (1024-bit key; unprotected) header.d=redhat.com header.i=@redhat.com header.a=rsa-sha256 header.s=mimecast20190719 header.b=PCQrcLxv; dkim-atps=neutral Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id D65ED385841F for ; Mon, 18 Mar 2024 16:08:33 +0000 (GMT) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by sourceware.org (Postfix) with ESMTPS id 130BE3858D37 for ; Mon, 18 Mar 2024 16:08:05 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 130BE3858D37 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 130BE3858D37 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=170.10.133.124 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1710778095; cv=none; b=NZXCrlHsDNF5Xsa6dU8uJDlReOsrCdfJxFwmYOgzwdHohBAikZPMtzbh67kevXUDku2/hFndbAAcXyFjE9bGfUQUoPTyIOe4dgFVz5l106LRBxNTdYxocENigBoUjb/D0qu17WhigGMzJt8MX42MzJKQJRl5qzNjQ4tYBApQ2F0= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1710778095; c=relaxed/simple; bh=X21NUCppzJLi0HFqZuAb4TKT5twcdACMuFz51kHZh74=; h=DKIM-Signature:MIME-Version:From:Date:Message-ID:Subject:To; b=d5rsNsElq1b3TnCncZxRyKgGQ1TaUGYFcZlcMB0REuxpgPxj557g79nx9r0J3xa+1oXQy+onXsNWNHRVp8HbM7egoVMYEznmzdSFbBE6sJEc9xUwagfPuatzIpxjKoPbfk3wqyIlqW6VyF+Huhk95xu8rJ8tgF8GyIVc5Siqxb8= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1710778084; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=NnjeGNqKgIo9LGPQB7uLbqOBpsX7LV3YlyL/S+KyxPE=; b=PCQrcLxvRvNqCidjMGrfVjmK8Vrcny8f9AQeevtNlcOfkm7iJhDsU7XrPCOQOwJvs0uPES c0B+Tbz9Aia35Ong+rSbQbeizA7L2KalB9LGRIbkwz9EEG27PHIc+O/5tbDzFWhcw9e249 r++mP4XvPli4Hy3wLt4CslrE0ZE1LMQ= Received: from mail-pj1-f69.google.com (mail-pj1-f69.google.com [209.85.216.69]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-46-_pMgTFuNPemIgJ252exptg-1; Mon, 18 Mar 2024 12:08:03 -0400 X-MC-Unique: _pMgTFuNPemIgJ252exptg-1 Received: by mail-pj1-f69.google.com with SMTP id 98e67ed59e1d1-29f96135606so1353358a91.1 for ; Mon, 18 Mar 2024 09:08:02 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1710778082; x=1711382882; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=NnjeGNqKgIo9LGPQB7uLbqOBpsX7LV3YlyL/S+KyxPE=; b=JVDpA2CIUFJz22uUez4gCr7pyyAcyu3LGU6Y8GXREwMcyHXqs9om3xcCpNqQS2PmDw utE4KgiAfRhzdczb0N0spCF+qFDd5xTQjR+U/gNsbGn/z6yKlKyXQMwEJmi0r9T75Jjq vFYkT0EcdrGq/UFeqnIjrGjB11QMUL5UUqiYlfGHN96UCXM1xIBTAen2j+lK1y2iErRi 79Ibw34rwwILpPqHJP35jlDFfw+JK8Xv7a91DJbdSYMCv0rJBxq9oluwpXSV5zF+eMEv 0nSgCUvAwESGwrr0xmJP1YKASwNWb5okCeLqnUNWohchq9X7GTYHL0xl5dG41oLaj9HK HnOQ== X-Forwarded-Encrypted: i=1; AJvYcCVUSrLqsgjYw7dE3mIyanqcMnjHfYCIkV2aYt9yzHxibdpEJiiPx2wklVUEObr/PTSDkj91WIw5nRnNvR+4VP2qiwrhKvlt22+o X-Gm-Message-State: AOJu0Yy0I3DlhUFJZ5Kv7jtJYhnqDim2uSP/jzcdQNNP9IheuVky8eSE 05GAC17JCxQUxQMvx/tAqqFod4UETRY1XPrnqbUnU0OAllQZ8jJC7Ob5B2jGPgMzTIWnddLytuN DVe8H4JLAy3CTWH+z1YD9bf89NrTvyLsKmt0aDAEoMd4zCw5NyXD4qv+c9uFSKmiTyaSKgFMwF3 iV7phdsC4oyHIuBiWFTFbsTgZfgaKyMdT4 X-Received: by 2002:a17:90b:514:b0:29b:bbde:8f19 with SMTP id r20-20020a17090b051400b0029bbbde8f19mr10432641pjz.33.1710778081947; Mon, 18 Mar 2024 09:08:01 -0700 (PDT) X-Google-Smtp-Source: AGHT+IEPDcWKvHSygRfatEdNwbAyOKGfXw+X3MU2MCmzk9P/Y9vC+Lh/Hdd07dOKV1D6aXoPb/lscFsYpvSfdZZ9J9M= X-Received: by 2002:a17:90b:514:b0:29b:bbde:8f19 with SMTP id r20-20020a17090b051400b0029bbbde8f19mr10432617pjz.33.1710778081596; Mon, 18 Mar 2024 09:08:01 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Arjun Shankar Date: Mon, 18 Mar 2024 17:07:50 +0100 Message-ID: Subject: Re: [PATCH v2] build-many-glibcs.py: Avoid loading user/system configurations To: Palmer Dabbelt Cc: simon.chopin@canonical.com, "Carlos O'Donell" , libc-alpha@sourceware.org, schwab@suse.de X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" X-BeenThere: libc-alpha@sourceware.org X-Mailman-Version: 2.1.30 Precedence: list List-Id: Libc-alpha mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: libc-alpha-bounces+e=80x24.org@sourceware.org > On Mon, 18 Mar 2024 06:31:00 PDT (-0700), arjun@redhat.com wrote: > >> I have commit verification turned on by default, which trips up pulling > >> when there is a non-signed commit at HEAD. There's likely a whole class > >> of similar configuration issues that could crop up, so this just ignores > >> user configuration files entirely. > >> > >> Signed-off-by: Palmer Dabbelt > > > > Looks like this unconditionally sets these environment variables? I'm > > wondering if this limits other use cases like e.g., users who set > > these environment variables and expect those values to be used during > > build-many-glibcs (for whatever reason)? > > Ya, I was kind of worried about that too. I've also got a bunch of > insteadOf lines in my configs, and while I don't know of anything that > would trip up build-many-glibcs if they disappeared I wouldn't be > surprised if someone else had a setup that did. That's why the v1 went > the other way and just tried to override the signature verification for > the pulls. > > IIRC there's some sort of global git config to override per-repo-path > settings, maybe the right answer is to just do that for whatever test > paths I have? While I don't know about other alternatives, looking at your suggested patch: will setting/exporting GIT_CONFIG_GLOBAL/GIT_CONFIG_NOSYSTEM before your build_many_glibcs invocation do the trick for you?