From: "Wiktor Żelazny" <wz@freeshell.de>
To: help-guix@gnu.org
Subject: Re: guix time-machine, broken hash in an old package definition, a workaround?
Date: Mon, 18 Jan 2021 10:11:58 +0100 [thread overview]
Message-ID: <20210118091158.ksajpiyynyk6ndpm@wzguix> (raw)
In-Reply-To: <20210118085731.b3x6b55riitrotdf@wzguix>
[-- Attachment #1: Type: text/plain, Size: 695 bytes --]
On Mon, Jan 18, 2021 at 09:57:32AM +0100, Wiktor Żelazny wrote:
> $ guix time-machine --commit=d81fb2ae9443994ae5dd1cb5837276fad63f842c --channels=channel-specs.scm -- \
> build --with-source=r-foreign=foreign_0.8-75.tar.gz r-foreign
> /gnu/store/jvh9zyym3xmzy94g37gx5klg8rx72vfj-r-foreign-75
A step forward:
$ guix time-machine --commit=d81fb2ae9443994ae5dd1cb5837276fad63f842c --channels=channel-specs.scm -- \
build --with-source=r-foreign@0.8-75=foreign_0.8-75.tar.gz r-foreign@0.8-75
results in a path with the correct version. However, subsequent `guix
time-machine -- environment` ignores is, downloads the source from CRAN,
and complaints about the hash.
WŻ
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 963 bytes --]
next prev parent reply other threads:[~2021-01-18 9:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-13 13:22 guix time-machine, broken hash in an old package definition, a workaround? Wiktor Żelazny
2021-01-13 16:24 ` zimoun
2021-01-13 19:28 ` Wiktor Żelazny
2021-01-13 18:57 ` Leo Famulari
2021-01-13 19:37 ` Wiktor Żelazny
2021-01-13 20:44 ` Leo Famulari
2021-01-14 8:30 ` Wiktor Żelazny
2021-01-14 9:48 ` zimoun
2021-01-14 19:00 ` Wiktor Żelazny
2021-01-14 20:29 ` zimoun
2021-01-15 20:18 ` Wiktor Żelazny
2021-01-15 20:48 ` zimoun
2021-01-18 8:57 ` Wiktor Żelazny
2021-01-18 9:11 ` Wiktor Żelazny [this message]
2021-01-20 9:35 ` Wiktor Żelazny
2021-01-20 10:15 ` zimoun
2021-01-20 12:26 ` Wiktor Żelazny
2021-01-20 15:03 ` zimoun
2021-01-22 11:36 ` Wiktor Żelazny
2021-01-22 16:29 ` zimoun
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210118091158.ksajpiyynyk6ndpm@wzguix \
--to=wz@freeshell.de \
--cc=help-guix@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).