From: Maxime Devos <maximedevos@telenet.be>
To: Mehmet Tekman <mtekman89@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Small change request to the manual page "Building from Git"
Date: Mon, 10 Oct 2022 18:25:02 +0200 [thread overview]
Message-ID: <e156510f-f4f9-56c9-252e-76a0645f3cb1@telenet.be> (raw)
In-Reply-To: <CAHHeYz+d8xqCR685m-bAj22wftaJXtMiSAkgKnM031mLGTkkVA@mail.gmail.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 868 bytes --]
On 10-10-2022 18:18, Mehmet Tekman wrote:
> Sorry for the message duplication, it's the default with my email provider.
>
> If "guix shell -D guix --pure" is included in the new version of the
> manual, then I'm more than happy to drop my suggestion.
> Thanks for the extra context, and the general tips!
If you do "guix shell -D guix --pure", you are using --pure, and
consequently "guix git authenticate" and "make authenticate" will fail,
contrary to what you seem to want.
My proposal was:
> I suppose removing --pure (from the manual) might solve this problem.
> However, --pure appears to have been added for a reason
> (commit 43ec98ef3025f67ff4f66b7da0bcb79a6f088042), so I expect the solution is to rephrase things somehow (maybe something about running "guix git authenticate" outside "guix shell -D guix").
Greetings,
Maxime.
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2022-10-10 16:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 13:35 Small change request to the manual page "Building from Git" Mehmet Tekman
2022-10-09 9:08 ` Maxime Devos
2022-10-10 14:18 ` Mehmet Tekman
2022-10-10 15:59 ` Maxime Devos
2022-10-10 16:18 ` Mehmet Tekman
2022-10-10 16:25 ` Maxime Devos [this message]
2022-10-10 16:32 ` Mehmet Tekman
2022-10-10 17:01 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e156510f-f4f9-56c9-252e-76a0645f3cb1@telenet.be \
--to=maximedevos@telenet.be \
--cc=guix-devel@gnu.org \
--cc=mtekman89@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.