From debbugs-submit-bounces@debbugs.gnu.org Thu Nov 03 06:04:46 2022 Received: (at 47949) by debbugs.gnu.org; 3 Nov 2022 10:04:46 +0000 Received: from localhost ([127.0.0.1]:48040 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oqX5Z-00021y-UP for submit@debbugs.gnu.org; Thu, 03 Nov 2022 06:04:46 -0400 Received: from mail-wr1-f44.google.com ([209.85.221.44]:43687) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oqX5Y-00021c-CF for 47949@debbugs.gnu.org; Thu, 03 Nov 2022 06:04:44 -0400 Received: by mail-wr1-f44.google.com with SMTP id g12so1849628wrs.10 for <47949@debbugs.gnu.org>; Thu, 03 Nov 2022 03:04:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:mime-version:message-id:date:references :in-reply-to:subject:cc:to:from:from:to:cc:subject:date:message-id :reply-to; bh=+Vz3dYuVti2BcgasJtDDOxC6cEf6Q88yWbXMx2/OEbE=; b=W3p8aJOGBufQg4sz2Pj+0iOQzIg3I8W8FioTCXVjPGDYyyoW6D0ax6a6vt4L2QfbYd xPdV4bK1DlbKwskvi9E0IFIELkT0noht+0keEBXx11SMZvuPCDj/JGCCpx5+dU/w5oaJ 8QXykW5ZwbLbfIng26ONJHsDNfhFShS5q7j++odHQmt6Xs4t28wop1Bv4oEuFNqGC9nh 9hZPtp4EaoH9Vo//bPCYCISzaPs1CM4klnDeDRAr0Wgs/W8N2F3Q+UPAhf80yg+7I/tg HV2WX8OupRhgs4z4BcesKZ7OeM78S8aDKJdQUAoujYsRDirIplvYqB1Ke4RFZmW736eG pp+Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:message-id:date:references :in-reply-to:subject:cc:to:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=+Vz3dYuVti2BcgasJtDDOxC6cEf6Q88yWbXMx2/OEbE=; b=0ff0ds8SjpWZZi0052ASEDGTHaAAHImoHrTRr6MLr3xqR1sd+PcXbhVdWsDEf1jibd JZmSAMzS8t2rf+AabahL3MRqainUyK1YlYXiH6m0vcQ09hiMlw9viyKs3J88b524Ms20 Uje8bUIuuY3f+Fj9ytPaPbWOlwCxfwlotBkiiGaBxU2uGJJZDs+UFPiUTdEVxadhupmG u1XULWGwPE4I8NqPjVMvlYwGPGYi0ZB1ttj6IITenMpZdEFpa5QGy7T+CxJSq0VwnNkP WFSFaizl0uetyvxmI6mxLWlId5FlzuDRLH09cYaBrSnY+H/D6PjuDQ8of5ieDaK2Wn9h c65Q== X-Gm-Message-State: ACrzQf1jPbF9Rqrek1B1gGnA+MGaafIjrTyxyoJ1CZjpGg8PDmQ2D+Lh jmLY4eIrQ6lzDn6xExesNSTdQWD1T8U= X-Google-Smtp-Source: AMsMyM5xrIIRLLtm/KmuN3bWjNy/xGgCdseuDScX9xv8pHOsvlk2p5RkopuzT9j0ClYi9KLaUPmdHA== X-Received: by 2002:a05:6000:1b01:b0:236:6ea5:1569 with SMTP id f1-20020a0560001b0100b002366ea51569mr17612531wrz.245.1667469878196; Thu, 03 Nov 2022 03:04:38 -0700 (PDT) Received: from lili ([2a01:e0a:59b:9120:65d2:2476:f637:db1e]) by smtp.gmail.com with ESMTPSA id bg36-20020a05600c3ca400b003cf774c31a0sm5383707wmb.16.2022.11.03.03.04.37 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 03 Nov 2022 03:04:37 -0700 (PDT) From: zimoun To: Vagrant Cascadian , Ludovic =?utf-8?Q?Court=C3=A8s?= , Roel Janssen Subject: Re: bug#47949: Failed to produce output path for guix-package-cache In-Reply-To: <87sfj1ci97.fsf@contorta> References: <86b58d34-b9ae-b4bb-f64c-9250e2c109cd@gnu.org> <87h7jqozsv.fsf@gnu.org> <26aef3de604e17d9199edff5f4b6eff170df8a1c.camel@gnu.org> <87zgxhmslv.fsf@gnu.org> <87fsfbznrk.fsf@contorta> <86fsfb0zvj.fsf@gmail.com> <87eduule00.fsf@contorta> <86o7tybbmq.fsf@gmail.com> <878rl2kw0l.fsf@contorta> <87zgdfd7ee.fsf@contorta> <87iljxhb5a.fsf@gmail.com> <87sfj1ci97.fsf@contorta> Date: Thu, 03 Nov 2022 09:48:21 +0100 Message-ID: <861qqke84q.fsf@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 47949 Cc: 47949@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) Hi Vagrant, On Wed, 02 Nov 2022 at 11:40, Vagrant Cascadian wrote: >> I do not know if =E2=80=9Cgit clean -dfx=E2=80=9D would help because her= e the error is >> probably between the repositories src/guix and src/guix-master and Guix >> manages them under 2 unrelated directory checkouts. > > I had the impression that it uses git to copy the branches (rather than > cp -r or something), otherwise the --branch=3Dmaster argument would be > meaningless (e.g. --branch=3Dmaster does not mean whatever happens to be > in the working directory), so I would assume the state of the local > working directory wouldn't matter, only what's in the specified branch > as git sees it. From my understanding, this guix pull --url=3D/home/vagrant/src/guix --branch=3Dmaster creates one directory under ~/.cache/guix/checkouts/ and then this, guix pull --url=3D/home/vagrant/src/guix-master --branch=3Dmaster creates another directory under ~/.cache/guix/checkouts/ and these both directory does not have the same name because their url is different. IIUC, you were at generation 139 (using a clone of /home/vagrant/src/guix living under say ~/.cache/guix/checkouts/maboosgggz6g6va54rikfxrsdsxhe363jri7g5dhcqb57odwkla= a) --8<---------------cut here---------------start------------->8--- # First version where I noticed failures: Generation 139 Oct 22 2022 13:07:08 guix bb2701b repository URL: /home/vagrant/src/guix branch: master commit: bb2701b9111a3d82a82ceaaf2b22b51ecd8ac21f # Failed to pull from 139, successfully pulled from 138: Generation 140 Oct 24 2022 13:19:21 guix 8663be6 repository URL: /home/vagrant/src/guix-master branch: master commit: 8663be6da7f13a8eeea71dc1f493f7adc5b7672a --8<---------------cut here---------------end--------------->8--- and then you had difficulties, but note that =E2=80=9Cguix pull=E2=80=9D ge= nerating 140 created another clone from /home/vagrant/src/guix-master living under ~/.cache/guix/checkouts/ie7tn3i564wpt5i2dqqm7ixzqfxwpp2ns6rqkyqn4z55d4kquju= q. Generation 140 did not updated the checkout used by generation 139. Somehow, the state of ~/.cache/guix/checkouts/maboosgggz6g6va54rikfxrsdsxhe363jri7g5dhcqb57odwklaa and the state of ~/.cache/guix/checkouts/ie7tn3i564wpt5i2dqqm7ixzqfxwpp2ns6rqkyqn4z55d4kqujuq require some compatibility, no? Well, I have lost the topic of the initial bug report. :-) BTW, I agree that =E2=80=9Cguix pull=E2=80=9D and =E2=80=9Cguix time-machin= e=E2=80=9D are requiring too much resource (especially bandwidth) when we could imagine more resource shares between various accounts and root. Well, I do no know if guile-git provides the git-worktree feature. Or we could also imagine a more automated workflow using only one local clone as you are doing. Cheers, simon