From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: Mekeor Melire <mekeor@posteo.de>, jgart <jgart@dismail.de>,
help-guix@gnu.org
Subject: Re: guix build: error: gcry_md_hash_buffer: Function not implemented
Date: Tue, 09 May 2023 20:32:50 -0400 [thread overview]
Message-ID: <87ttwlrpot.fsf@gmail.com> (raw)
In-Reply-To: <87ild15zls.fsf@gmail.com> (Simon Tournier's message of "Tue, 09 May 2023 16:49:35 +0200")
Hi Simon,
Simon Tournier <zimon.toutoune@gmail.com> writes:
> Hi,
>
>> "26a788ae06 doc: Add some information/recommendation regarding
>> --sysconfdir."
>>
>> that I hope rectifies this!
>>
>> Let me know if something can be improved still.
>
> I think the “make install” part means here “./pre-inst-env guix pull”.
> Well, that’s the only case where I had troubles because this value is
> recorded and can be propagated. Consider,
>
> ./bootstrap && ./configure --localstatedir=/var && make
> ./pre-inst-env guix pull
> guix pull --commit=1234abc
>
> and compared to the sequence without ./pre-inst-env:
>
> guix pull
> guix pull -- commit=1234abc
>
> then it does not lead to the exact same Guix.
'sudo -E ./pre-inst-env guix system reconfigure ...' would be another
such incantation that requires --sysconfdir to be set to /etc. Since we
now recommend it to always be used, it is covered should these
"advanced" commands be used, I think.
--
Thanks,
Maxim
next prev parent reply other threads:[~2023-05-10 0:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-06 2:41 guix build: error: gcry_md_hash_buffer: Function not implemented jgart
2023-05-07 10:24 ` Mekeor Melire
2023-05-07 10:31 ` Mekeor Melire
2023-05-07 14:55 ` jgart
2023-05-07 16:17 ` Efraim Flashner
2023-05-07 17:14 ` Mekeor Melire
2023-05-08 1:53 ` Maxim Cournoyer
2023-05-09 14:49 ` Simon Tournier
2023-05-10 0:32 ` Maxim Cournoyer [this message]
2023-05-08 2:08 ` jgart
2023-05-14 14:49 ` jgart
2023-05-15 13:40 ` Maxim Cournoyer
2023-05-07 19:26 ` jgart
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=87ttwlrpot.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=help-guix@gnu.org \
--cc=jgart@dismail.de \
--cc=mekeor@posteo.de \
--cc=zimon.toutoune@gmail.com \
/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).