From: "Wiktor Żelazny" <wz@freeshell.de>
To: help-guix@gnu.org
Subject: guix time-machine, broken hash in an old package definition, a workaround?
Date: Wed, 13 Jan 2021 14:22:23 +0100 [thread overview]
Message-ID: <20210113132223.x4wgnwwph2jwtfb5@wzguix> (raw)
[-- Attachment #1: Type: text/plain, Size: 2287 bytes --]
Hi list,
It appears that the package bundles at CRAN are not stable. The bundle
contents can change, and so its hash. I’ve encountered such a problem
three times, I think, already, so it’s presumably systemic. The latest
(minimal working) example:
$ cat manifest.scm
(specifications->manifest
'("r-foreign"))
$ cat channel-specs.scm
(list (channel
(name 'guix)
(url "https://git.savannah.gnu.org/git/guix.git")
(commit
"d81fb2ae9443994ae5dd1cb5837276fad63f842c")))
$ guix time-machine --commit=d81fb2ae9443994ae5dd1cb5837276fad63f842c --channels=channel-specs.scm -- environment -C --pure --manifest=manifest.scm
Updating channel 'guix' from Git repository at 'https://git.savannah.gnu.org/git/guix.git'...
building /gnu/store/ixqarfdy375cqwkwgvm9z8cadw87f6gg-foreign_0.8-75.tar.gz.drv...
downloading from http://cran.r-project.org/src/contrib/Archive/foreign/foreign_0.8-75.tar.gz...
/sha256 hash mismatch for /gnu/store/z6hkz6r1i5cgzjxc5m883lgh1xvjff8s-foreign_0.8-75.tar.gz:
expected hash: 0g4mi101srjbl17ydb2hl3854m3xj0llj6861lfr30sp08nkqavl
actual hash: 1c888wrn9xf94lp7w9kjw5l8fnarrkv5pi1px5rfnybm1qlysdx5
hash mismatch for store item '/gnu/store/z6hkz6r1i5cgzjxc5m883lgh1xvjff8s-foreign_0.8-75.tar.gz'
build of /gnu/store/ixqarfdy375cqwkwgvm9z8cadw87f6gg-foreign_0.8-75.tar.gz.drv failed
View build log at '/var/log/guix/drvs/ix/qarfdy375cqwkwgvm9z8cadw87f6gg-foreign_0.8-75.tar.gz.drv.bz2'.
cannot build derivation `/gnu/store/vx9187mcdj041sr76bivzbnggr6ajm4q-r-foreign-0.8-75.drv': 1 dependencies couldn't be built
guix environment: error: build of `/gnu/store/vx9187mcdj041sr76bivzbnggr6ajm4q-r-foreign-0.8-75.drv' failed
I tried
. adding another channel with r-foreign redefined in hope that the one in guix
would get masked
. adding --with-input=r-foreign=r-foreign-redefined (the latter defined
in another channel)
. adding -L to the environment (also to time-machine) pointing to a
directory with r-foreign redefined
. an inferior
These attempts were either ignored by guix or resulted in
guix time-machine: error: got unexpected path `Backtrace:' from substituter
Is there a recommended way to deal with such a situation? Thank you for
taking a look.
WŻ
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 963 bytes --]
next reply other threads:[~2021-01-13 13:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-13 13:22 Wiktor Żelazny [this message]
2021-01-13 16:24 ` guix time-machine, broken hash in an old package definition, a workaround? 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
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=20210113132223.x4wgnwwph2jwtfb5@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).