From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp11.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms5.migadu.com with LMTPS id SK4PIr6nxGNvFAEAbAwnHQ (envelope-from ) for ; Mon, 16 Jan 2023 02:26:22 +0100 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp11.migadu.com with LMTPS id 4HEOIr6nxGM3NgEA9RJhRA (envelope-from ) for ; Mon, 16 Jan 2023 02:26:22 +0100 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id BDD982F68F for ; Mon, 16 Jan 2023 02:26:21 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pHEGC-0003DU-Ga; Sun, 15 Jan 2023 20:26:04 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pHEGB-0003DC-2M for bug-guix@gnu.org; Sun, 15 Jan 2023 20:26:03 -0500 Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1pHEGA-0003mE-Da for bug-guix@gnu.org; Sun, 15 Jan 2023 20:26:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1pHEG9-0004pJ-UW for bug-guix@gnu.org; Sun, 15 Jan 2023 20:26:01 -0500 X-Loop: help-debbugs@gnu.org Subject: bug#60816: guix pull ("computing Guix derivation") is not reproducible Resent-From: bokr@bokr.com Original-Sender: "Debbugs-submit" Resent-CC: bug-guix@gnu.org Resent-Date: Mon, 16 Jan 2023 01:26:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 60816 X-GNU-PR-Package: guix X-GNU-PR-Keywords: To: Josselin Poiret Cc: Julien Lepiller , 60816-close@debbugs.gnu.org Received: via spool by 60816-done@debbugs.gnu.org id=D60816.167383233518522 (code D ref 60816); Mon, 16 Jan 2023 01:26:01 +0000 Received: (at 60816-close) by debbugs.gnu.org; 16 Jan 2023 01:25:35 +0000 Received: from localhost ([127.0.0.1]:59972 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pHEFi-0004of-NJ for submit@debbugs.gnu.org; Sun, 15 Jan 2023 20:25:35 -0500 Received: from mailout.easymail.ca ([64.68.200.34]:45842) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pHEFg-0004oR-Hk for 60816-close@debbugs.gnu.org; Sun, 15 Jan 2023 20:25:33 -0500 Received: from localhost (localhost [127.0.0.1]) by mailout.easymail.ca (Postfix) with ESMTP id BEBCF67B32; Mon, 16 Jan 2023 01:25:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=bokr.com; s=easymail; t=1673832326; bh=N0Ofiljc7oMhRRrEXuc9Nd1WiEs+xw9z77Q4F0jwuYU=; h=From:Date:To:Cc:Subject:References:In-Reply-To:From; b=ddciJafXe/dKJvmgyPeNvgeVCsz6LnAymso5Vgg1q56Qtiv9HEMPEES7AoP98dtId 8qcCnA+a/mzzweXw4aHdz+pl9bPI+O5vasbU2UeGVCw7PxrgHIvP25GZZFEvnMHUnS 4Ujv1Nf4BqgCA+11bSzxLoG+L0YwOSCcmrxu8/Yv6sEcfUkaPjnaz3k/kAZ+shHjhu QmNMS6dDPqG5Jf0lIChFjTDrWLvnd0LCBhulZS5iVKEHJlRfGVx4Jnl9wvZdvKJGep UnIhWHJDE7FqJoJHQ/pu96YWaDWNdtNBg7cC5XzKZ2sjWazuB9gK2JbKcOV/JRALwQ PZPF7CeqZBztw== X-Virus-Scanned: Debian amavisd-new at emo09-pco.easydns.vpn Received: from mailout.easymail.ca ([127.0.0.1]) by localhost (emo09-pco.easydns.vpn [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1-j_tbWxFzKc; Mon, 16 Jan 2023 01:25:26 +0000 (UTC) Received: from localhost (m90-129-212-28.cust.tele2.se [90.129.212.28]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mailout.easymail.ca (Postfix) with ESMTPSA id 130B967B11; Mon, 16 Jan 2023 01:25:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=bokr.com; s=easymail; t=1673832326; bh=N0Ofiljc7oMhRRrEXuc9Nd1WiEs+xw9z77Q4F0jwuYU=; h=From:Date:To:Cc:Subject:References:In-Reply-To:From; b=ddciJafXe/dKJvmgyPeNvgeVCsz6LnAymso5Vgg1q56Qtiv9HEMPEES7AoP98dtId 8qcCnA+a/mzzweXw4aHdz+pl9bPI+O5vasbU2UeGVCw7PxrgHIvP25GZZFEvnMHUnS 4Ujv1Nf4BqgCA+11bSzxLoG+L0YwOSCcmrxu8/Yv6sEcfUkaPjnaz3k/kAZ+shHjhu QmNMS6dDPqG5Jf0lIChFjTDrWLvnd0LCBhulZS5iVKEHJlRfGVx4Jnl9wvZdvKJGep UnIhWHJDE7FqJoJHQ/pu96YWaDWNdtNBg7cC5XzKZ2sjWazuB9gK2JbKcOV/JRALwQ PZPF7CeqZBztw== From: bokr@bokr.com Date: Mon, 16 Jan 2023 02:25:08 +0100 Message-ID: <20230116012508.GA2776@LionPure> References: <20230114190042.7945f9d7@sybil.lepiller.eu> <875yd857y2.fsf@jpoiret.xyz> <20230115142955.23248bda@sybil.lepiller.eu> <87r0vvkgr0.fsf@jpoiret.xyz> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <87r0vvkgr0.fsf@jpoiret.xyz> User-Agent: Mutt/1.10.1 (2018-07-13) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-guix@gnu.org List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+larch=yhetil.org@gnu.org Sender: bug-guix-bounces+larch=yhetil.org@gnu.org X-Migadu-Country: US X-Migadu-Flow: FLOW_IN ARC-Seal: i=1; s=key1; d=yhetil.org; t=1673832382; a=rsa-sha256; cv=none; b=mYre/Kp8D4sLS/h0HEzIApKU6g9gWJvtsNMu6wZlUbfX3zQnwGjADHPicK4zVP76OXtL2K 94aqGCKpSsedf58PDDHeJe962jE3mtXU84gXFvVnexPVAJ3j7wW4bdjxWCsTQ82dluyrNL 0hz3GzOjcZXy4oeI4lcSXh7UAzG3urLPZO/0gPyQEishNZGl6A/YygszjIGC8m83iY6Kgz C1Qbv2E8zdxZ+/46kpVugugQonzGlfO6kd2BAuj5MXwj2sBXAf2AesgTSooVnwuibmxwpL +4k0omdfF4xdN0FzX+gJ+2+MsyNvTEAAWPJlXcOXZhTuHX+hbutLkJVwjW47ZA== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=fail ("headers rsa verify failed") header.d=bokr.com header.s=easymail header.b=ddciJafX; dkim=fail ("headers rsa verify failed") header.d=bokr.com header.s=easymail header.b=ddciJafX; spf=pass (aspmx1.migadu.com: domain of "bug-guix-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="bug-guix-bounces+larch=yhetil.org@gnu.org"; dmarc=none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1673832382; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:resent-cc:resent-from:resent-sender: resent-message-id:in-reply-to:in-reply-to:references:references: list-id:list-help:list-unsubscribe:list-subscribe:list-post: dkim-signature; bh=/chZea1Hic48U2d8HNvcUi1GGSQZStc8D6ACH+hPsFY=; b=jKlfwTCIq4U4/gN0yqiVRaMBSNi2EQjjqI5uTdlmlScGd6uDtfPe7UMA5j/eh9NBddc41e aNW1GfxzZdVMCh+Q4P6weeRaLGp2ZNzSihe+/jOH785HVJi1v/cDjdRxl+fhwsHpEdJbNs xzBdouND2vaT7IG3Ye8+rnMSOZeIOpxFerL7qJcIAdt9a8SxfzzQjyQ5znziDLluZnJkYF SXbleo9ha0Scw8VxJzlMWPSi6oba3JB9N7YJQk3f5OYOoLTWBlfnTL1QmY1J5NMuqpJZYK RhoonvIjq28rAMHsaC06hdPNkixQln+y23vvY+CwcVE4M9GonKLHAZoVNVcXgg== X-Migadu-Spam-Score: -1.82 X-Spam-Score: -1.82 X-Migadu-Queue-Id: BDD982F68F X-Migadu-Scanner: scn1.migadu.com Authentication-Results: aspmx1.migadu.com; dkim=fail ("headers rsa verify failed") header.d=bokr.com header.s=easymail header.b=ddciJafX; dkim=fail ("headers rsa verify failed") header.d=bokr.com header.s=easymail header.b=ddciJafX; spf=pass (aspmx1.migadu.com: domain of "bug-guix-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="bug-guix-bounces+larch=yhetil.org@gnu.org"; dmarc=none X-TUID: ncvqSNUTqcI5 Hi, On +2023-01-15 15:35:31 +0100, Josselin Poiret via Bug reports for GNU Guix wrote: > Hi again Julien, > > Julien Lepiller writes: > > > it seems that on one machine, my .cache/guix/checkouts got polluted by > > uncommited files. I have no idea why they're there, but cleaning them > > should solve my issue, thanks! > > It's not the first time we've seen this, we could probably consider > adding a git clean after the reset in switch-to-ref. > > Best, > -- > Josselin Poiret Could wrong timestamps on pushed files cause problems? E.g., if you were working offline on a laptop where cat /proc/driver/rtc was significantly wrong at boot time, perhaps due to flaky CMOS battery, or error in init specs? If you didn't connect to the internet and get synced, couldn't you wind up with files with bad time stamps? (I think I can dig up evidence of that, when I didn't connect, though I don't show it here). Could some Makefile action or some date-sensitive find or if [[ file1 -nt file2 ]] then be wrongly triggered and leave mystery files around? IWT synchronizing distributed monotonic time has to have been solved a long ago, but old unnoticed errors do seem to wake up sometimes in new circumstances. I have been having mystery problems with time, which I have yet to diagnose properly. One theory that matches some symptoms is if there is a virtualized /proc/driver/rtc which gets a bogus value temporarily, which gets accessed and stored by whatever stores time as boot time for who -b to see forever (until shutdown) -- but date and other time functions see the virtual /proc/driver/rtc every time, not a cached value, so they get corrected shortly after internet is connected. But what happens to file time stamps if you don't connect to the internet for a long time? BTW,I see the bad time at the top of the screen right after boot but before reaching login, and IIRC it will currect to local without logging in if I plug in the internet dongle. Shown below I just booted from cold power-off, with 99% main battery, about 17:20, so how to explain bogus who -b system boot time of 07:53 this morning? From that timee uptime at 17:20:06 would be: 9hrs 27min 6sec, not "1:14" (1hr 14min)) Well, I guess the 9 hours could be explained by root having a different idea of locale at pre-internet boot time, but the 27min 6 sec? --8<---------------cut here---------------start------------->8--- who -b; uptime;date -Ins;grep rtc /proc/driver/rtc system boot 2023-01-15 07:53 17:20:06 up 1:14, 1 user, load average: 0.00, 0.08, 0.15 2023-01-15T17:20:06,768027575+01:00 rtc_time : 16:20:06 rtc_date : 2023-01-15 --8<---------------cut here---------------end--------------->8--- Also some anomalies in dmesg and journalctl -b, but inconclusive for me ;/ I noticed the bad "who -b" times because whenever my ~/.bash_profile sees a change as I log in, it uses the date to create a new scratch "boot-session" directory and updates a symbolic link to it at ~/bs like stat -c %N ~/bs shows: '/home/bokr/bs' -> '/home/bokr/BS/bs20230115_0753' which is annoyingly wrong. It also makes a link to the previous ~/bs in the new, like '/home/bokr/bs/pbs' -> '../bs20230113_0427' (showing some insomnia ;/ ) but if I cd ~/bs PS1 will display a nice short prompt :) --8<---------------cut here---------------start------------->8--- [01:53 ~/bs]$ cd ~/bs [01:53 ~/bs]$ realpath . /home/bokr/BS/bs20230115_0753 [01:53 ~/bs]$ realpath ~/bs /home/bokr/BS/bs20230115_0753 [01:54 ~/bs]$ --8<---------------cut here---------------end--------------->8--- HTH & SFTN if this is not useful or relevant. -- Regards, Bengt Richter