From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp1 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id 4IBKInf9CmB2WwAA0tVLHw (envelope-from ) for ; Fri, 22 Jan 2021 16:29:43 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp1 with LMTPS id MLMSHnf9CmC7HgAAbx9fmQ (envelope-from ) for ; Fri, 22 Jan 2021 16:29:43 +0000 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 055859403E7 for ; Fri, 22 Jan 2021 16:29:42 +0000 (UTC) Received: from localhost ([::1]:32902 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1l2zJc-0000GX-GS for larch@yhetil.org; Fri, 22 Jan 2021 11:29:40 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:52810) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1l2zJN-0000GK-Mb for help-guix@gnu.org; Fri, 22 Jan 2021 11:29:25 -0500 Received: from mail-qt1-x831.google.com ([2607:f8b0:4864:20::831]:36931) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1l2zJK-0000Zr-Uv for help-guix@gnu.org; Fri, 22 Jan 2021 11:29:25 -0500 Received: by mail-qt1-x831.google.com with SMTP id v3so4505743qtw.4 for ; Fri, 22 Jan 2021 08:29:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :content-transfer-encoding; bh=qD34YMxbuWrJgwRwVWUEcejO1/v5D6KzxFOugo5nz3w=; b=DNaM2qP27OlAvumfyOweOtBaMqdokDQFcC1bqKn8YaOuSQ7dLBR7arQJ40yxX23aYP iW0gCpJ7FopB67KSRwwgXdXhOjLRIzfh5YFfi9b2odF7QSfuAzUAvUozf7aqoX4qNFoB kLdIVJWmvC7MFV1ZXbCTBLvfDWPqQfYnsMBd91xNu2zB++QUvphWsPBYa+Sgomud8MFA 8jgE3YaoMyTkm83O7gXl8i+abeMKecxc9eo83EhdVFb29S6JfsR6B44Rq+xYLP6wwCo/ 58FXHoKM2uG+iiufL7JCqefKNZggnFzaM3XKb59IQY3Vx1L4r3ajUwWDjptQmcsX6HJv 437A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:content-transfer-encoding; bh=qD34YMxbuWrJgwRwVWUEcejO1/v5D6KzxFOugo5nz3w=; b=AUub6slxPFoweieD+XcYyJRjgFPSlcZ4YoGvXPQGzG8FL1iw3tom1t8xYyb+lvJK8w ZSMqRbkVX7mgRUL8ulQK1PxPyixYry8MpP35nspZCTpGn8gTPDLgLMrHgZa42nSJMSL0 dcEc8MHAbC2TALgqt+OrNGlR3AvBQOkgHMpxNUdepZN50Gv8vavCK3XAb5haNIVFgbjN e5BbdKkjs90nbeW21NMwN7igEBgkn3gjiPbi98/1VTxRaAxythWksBZ25WHLZLkMPho1 IZibxEPPMJ6Pb+hKbde2vNsw0X7qXU1Pbw+DZyXMbIceyaH8k65FLaGWr3b0tfSa1dQv 8BhQ== X-Gm-Message-State: AOAM532sVG7BGTmmxecFC6934bFJovaZ7uJKEsKLT5s8slJK9Un7zVhK QIRGhO8KkPFiYy6F2qerRumNFKYD7OdOZTrUNGrh44uL/oo= X-Google-Smtp-Source: ABdhPJwRthJNcUPgZxfZWS0M9kRRpKWIdP9qGS4m/HNuZhJ+JXdw2XgRaGsS/fgSVb0ZK719xX5lkQb/SuRz4R0z910= X-Received: by 2002:aed:3629:: with SMTP id e38mr1362775qtb.354.1611332960345; Fri, 22 Jan 2021 08:29:20 -0800 (PST) MIME-Version: 1.0 References: <20210114083000.ak4de227ipfi37pg@wzguix> <86eeinsvbg.fsf@gmail.com> <20210114190030.suymnghk5mhteseu@wzguix> <86r1mnl0sj.fsf@gmail.com> <20210115201859.z4rlqu4xnsphowm4@wzguix> <20210120093514.hwd5ojuvrbzluu6a@wzguix> <86czxz9aoa.fsf@gmail.com> <20210120122602.la6nckvozvdkwfnh@wzguix> <20210122113606.iogodbik5prg5xhm@wzguix> In-Reply-To: <20210122113606.iogodbik5prg5xhm@wzguix> From: zimoun Date: Fri, 22 Jan 2021 17:29:08 +0100 Message-ID: Subject: Re: guix time-machine, broken hash in an old package definition, a workaround? To: help-guix , zimoun Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Received-SPF: pass client-ip=2607:f8b0:4864:20::831; envelope-from=zimon.toutoune@gmail.com; helo=mail-qt1-x831.google.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: help-guix@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+larch=yhetil.org@gnu.org Sender: "Help-Guix" X-Migadu-Flow: FLOW_IN X-Migadu-Spam-Score: -2.05 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20161025 header.b=DNaM2qP2; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (aspmx1.migadu.com: domain of help-guix-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=help-guix-bounces@gnu.org X-Migadu-Queue-Id: 055859403E7 X-Spam-Score: -2.05 X-Migadu-Scanner: scn1.migadu.com X-TUID: jybXrBon9JwS Hi, On Fri, 22 Jan 2021 at 12:36, Wiktor =C5=BBelazny wrote: > Would be cool, however for MRAN you also need the snapshot date. Would > it be feasible to extract it from the commit date? There are dates at Extract date from ~/.cache/guix/checkouts/pj... and author date of the commit provided at the time-machine should the good one to provide to MRAN. > CRAN, but for the archived package versions these are =E2=80=9CLast modif= ied=E2=80=9D. > There is also =E2=80=9CDate/Publication:=E2=80=9D field in the tarball, b= ut you wouldn=E2=80=99t > trust a tarball with a hash mismatch. About trust and mismatch, I would say: it depends. You can still download the new 'r-foreign@0.85' served by CRAN with the mismatch and audit by hand. Well, that's another story. > I cannot check it. This approach works, but for some mysterious reason > it also works when I remove the r-foreign-fixed definition and constrain > the manifest to r. Without the definition, I would expect guix to try > building r-foreign from CRAN. I thought that maybe guix treated > r-foreign@0.8-75 and r-foreign@0.8-75-fixed as exchangeable because of > the same hash, even if the versions and URIs differed, and so did not > try to build r-foreign@0.8-75, but used r-foreign@0.8-75-fixed from the > store. However, with `guix time-machine =E2=80=A6 -- build r-foreign@0.8-= 75`, > I=E2=80=99m getting a different output than for `guix time-machine =E2=80= =A6 -- build > r-foreign@0.8-75-fixed`. I tried `guix gc ` to force the > rebuild, but I got the =E2=80=9Cstill alive=E2=80=9D error, even though I= had exited the > environment. To rebuild, the easiest is the option "build --check". > I will just trust your expertise on that, and keep your solution. I can > always go back to the inferior if it turns out to fail when I encounter > the hash mismatch problem sometime in the future. As I see it, there are 2 options: _ option 1: write the package definition with the new MRAN source (or with the CRAN source but with the new checksum hash), and a manifest file. Then run $ guix time-machine --commit=3Dd81fb2a \ -- environment -m manifest.scm The trick here is to use "--with-input"; somehow the graph has to be rewritten. At the manifest level, it is something with "transform-package-inputs" _ option 2: use another package transformation: "transformation-package-sources". The new API is simpler with "package-with-source", so the manifest could contain... (packages->manifest (cons (package-with-source r-foreign "https://cran.microsoft.com/snapshot/2020-01-27/") (map specification->package (list "r" "r-another-package")))) ...But the issue is that "package-with-source" was not so simple at commit d81fb2a time. And the way is "transformation-package-sources" even if I am not convinced it is simpler than create by hand the correct 'r-foreign' package with option 1. > Have a nice weekend, Have a nice week-end too! :-) All the best, simon