From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Tue, 20 Feb 2024 11:13:43 +0100 Received: from metis.whiteo.stw.pengutronix.de ([2a0a:edc0:2:b01:1d::104]) by lore.white.stw.pengutronix.de with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1rcN8B-00FuM5-1M for lore@lore.pengutronix.de; Tue, 20 Feb 2024 11:13:43 +0100 Received: from localhost ([127.0.0.1] helo=metis.whiteo.stw.pengutronix.de) by metis.whiteo.stw.pengutronix.de with esmtp (Exim 4.92) (envelope-from ) id 1rcN8A-0002S8-TM; Tue, 20 Feb 2024 11:13:42 +0100 Received: from mail.thorsis.com ([92.198.35.195]) by metis.whiteo.stw.pengutronix.de with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1rcN7t-0002Rk-AU for ptxdist@pengutronix.de; Tue, 20 Feb 2024 11:13:26 +0100 Date: Tue, 20 Feb 2024 11:13:25 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=thorsis.com; s=default; t=1708424004; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:content-type:content-type:in-reply-to:in-reply-to: references:references; bh=v2v32oFsPGRj+rUrQKaGAA3JdVzP4egaVLuiFoJx97Y=; b=ZBKtnnQ+8jdtYxrqNhmCKn9qJCmB2c7gk2rTGXMM4HGUL661/rYEHukJP6tAt7bk6lAevS uUukQKRp1NE4r3Y3TKoDlUUClG7Jl1DnkPP2WDL952MLoS2WGa/5KZJ/3JPhXgYjXZmOQw S41Y2OEfYkg7uHuSIlxyTLLh6HEoO4wr+wsdtd1QLAetFvvQ5B38/qxtXyBDC0z/SMCEbQ zTHW7+YiCZ/1MI759OOEhTei6PoTMc0Mga2YXkS5fxTUxLyy31aOjinWM0k7Q5c1A37bBN ZbrZ8VpaSMqP7U29ByjQEeE+j40nlKiOqW3FSheLVGfdw+dJQ54mQkK/UuzBXw== From: Alexander Dahl To: ptxdist@pengutronix.de Message-ID: <20240220-imagines-immobile-5b3cdc5bd95b@thorsis.com> Mail-Followup-To: ptxdist@pengutronix.de References: <20240220-observant-huff-d4e2b8d4ccd4@thorsis.com> Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on metis.whiteo.stw.pengutronix.de X-Spam-Level: X-Spam-Status: No, score=-2.8 required=4.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.2 Subject: Re: [ptxdist] setting from localsetup differing from setup not honoured X-BeenThere: ptxdist@pengutronix.de X-Mailman-Version: 2.1.29 Precedence: list List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: ptxdist@pengutronix.de Sender: "ptxdist" X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Mail-From: ptxdist-bounces@pengutronix.de X-SA-Exim-Scanned: No (on metis.whiteo.stw.pengutronix.de); SAEximRunCond expanded to false Hello Michael, Am Tue, Feb 20, 2024 at 09:55:39AM +0100 schrieb Michael Olbrich: > Hi, > > On Tue, Feb 20, 2024 at 09:14:58AM +0100, Alexander Dahl wrote: > > currently tinkering with bootloaders and wondered why at91bootstrap 4 > > _always_ printed '2020-08-01 00:00:00' as build time, although I had set > > PTXCONF_SETUP_DISABLE_REPRODUCIBLE with `ptxdist localsetup`? > > > > Turns out PTXDIST_BUILD_TIMESTAMP is set correctly if > > PTXCONF_SETUP_DISABLE_REPRODUCIBLE is set through `ptxdist setup` but > > not if it is set through `ptxdist localsetup`. If set through > > localsetup `ptxdist print PTXCONF_SETUP_DISABLE_REPRODUCIBLE` gives > > 'undefined' while it gives 'y' when set through 'setup'. > > > > BSP is layered, two layers actually. ptxdist version is still > > 2023.05.0, but I could not find any significant changes to that > > mechanism after that. I'm afraid I am currently not able to provide a > > solution for that problem, but I wanted to let you know. > > I cannot reproduce this on master. Tried in another BSP now which already has ptxdist-2023.12.0. Same result, also with other variables like PTXCONF_SETUP_DEPRECATED_FATAL, see output from a BSP on top of DistroKit master: % cat .ptxdistrc.diff 5ff908847d27f19d31c328b51f205bf0 PTXCONF_SETUP_DEPRECATED_FATAL=y PTXCONF_SETUP_DISABLE_REPRODUCIBLE=y % p print PTXCONF_SETUP_DISABLE_REPRODUCIBLE PTXCONF_SETUP_DISABLE_REPRODUCIBLE undefined % p version 2023.12.0 > Are you running `ptxdist localsetup` and > `ptxdist print` in the same layer? The localsetup config is only used from > the toplevel layer, not stacked across all layers. So only > ${PTXDIST_WORKSPACE}/.ptxdistrc.diff is used. Yes, running from the top layer only. Host system is Debian GNU/Linux 12 (bookworm) and my shell is zsh (no difference from bash though). Greets Alex