From: Ricardo Wurmus <rekado@elephly.net>
To: Jack Hill <jackhill@jackhill.us>
Cc: help-guix@gnu.org
Subject: Re: Corrupt/missing store items
Date: Tue, 22 Jun 2021 20:46:18 +0200 [thread overview]
Message-ID: <8735t9ybyd.fsf@elephly.net> (raw)
In-Reply-To: <alpine.DEB.2.21.2106211623530.2109@marsh.hcoop.net>
Jack Hill <jackhill@jackhill.us> writes:
> Given what i know about the problem: substitute operations are
> failing
> because gnutls is not available, I tried:
>
> jackhill@kalessin ~$ guix build
> --substitute-urls=http://ci.guix.gnu.org
> /gnu/store/zkhymfsbrv0s4y7l778g78k6y65nidxd-gnutls-3.6.16.drv
> /gnu/store/2vjql2vd6srqxhr0r9xnhclqgc5kxlh1-gnutls-3.6.16-debug
> /gnu/store/ads39f4czri8s1k43qd0qpxi6dr3w0zn-gnutls-3.6.16-doc
> /gnu/store/jlk67v3nddhv0z963wfvahk8fc8gqcz8-gnutls-3.6.16
> jackhill@kalessin ~$ ls -l
> /gnu/store/jlk67v3nddhv0z963wfvahk8fc8gqcz8-gnutls-3.6.16
> ls: cannot access
> '/gnu/store/jlk67v3nddhv0z963wfvahk8fc8gqcz8-gnutls-3.6.16': No
> such file or directory
What happens if you try “guix build --check --no-grafts
/gnu/store/zkhymfsbrv0s4y7l778g78k6y65nidxd-gnutls-3.6.16.drv” or
similar? The database probably states that
/gnu/store/jlk67v3nddhv0z963wfvahk8fc8gqcz8-gnutls-3.6.16 has
already been built, so with “--check” you might be able to make it
build it again.
> So Guix think's it's sucessfully built gnutls, but it's still
> not
> present in the store. I've also tried copying the store items
> from
> other hosts. No luck so far…
How did that fail?
How could the directory have disappeared? Guix appears to be very
surprised that the directory is missing.
--
Ricardo
next prev parent reply other threads:[~2021-06-22 18:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-21 18:30 Corrupt/missing store items Jack Hill
2021-06-21 20:28 ` Jack Hill
2021-06-22 8:20 ` Christopher Baines
2021-06-22 13:21 ` Jack Hill
2021-06-22 13:45 ` Jack Hill
2021-06-22 18:46 ` Ricardo Wurmus [this message]
2021-06-22 19:29 ` Jack Hill
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=8735t9ybyd.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=help-guix@gnu.org \
--cc=jackhill@jackhill.us \
/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).