From: zimoun <zimon.toutoune@gmail.com>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: 31285@debbugs.gnu.org, "Mark H Weaver" <mhw@netris.org>,
"Ludovic Courtès" <ludo@gnu.org>,
"Thompson, David" <dthompson2@worcester.edu>
Subject: [bug#31285] [PATCH 1/1] guix: Add git-fetch/impure.
Date: Tue, 01 Dec 2020 19:06:38 +0100 [thread overview]
Message-ID: <86im9lv1sh.fsf@gmail.com> (raw)
In-Reply-To: <87sh7dcsss.fsf@gmail.com> (Chris Marusich's message of "Sun, 29 Apr 2018 19:49:23 -0700")
Hi,
The bug #31285 is mainly about allow Git over SSH, see:
<http://issues.guix.gnu.org/issue/31285>
and I do not know where the discussion below happened…
On Sun, 29 Apr 2018 at 19:49, Chris Marusich <cmmarusich@gmail.com> wrote:
> Hi Mark, Ludo, and David,
>
> ludo@gnu.org (Ludovic Courtès) writes:
>
>> Hello,
>>
>> Chris Marusich <cmmarusich@gmail.com> skribis:
>>
>>> You've both said that you would prefer not to add git-fetch/impure to
>>> Guix. Can you help me to understand why you feel that way? I really
>>> think it would be nice if Guix could fetch Git repositories over SSH
>>> using public key authentication, so I'm hoping that we can talk about it
>>> and figure out an acceptable way to implement it.
>>
>> One argument against it would be that it encourages people (or at least
>> makes it very easy) to write origins that depend on external state, and
>> thus may be non-reproducible by others, and that Guix itself should
>> provide tools for writing reproducible build definitions.
>
> The impurity bothers me, too. If you don't have the right SSH key
> available or your SSH installation isn't configured in just the right
> way, then an origin defined using git-fetch/impure won't work.
>
> Could we eliminate the impurity by adding a feature to the guix-daemon
> that allows an administrator (i.e., root) to configure an SSH key for
> guix-daemon to use when fetching Git repositories over SSH? If it's
> possible, I think that would be preferable. What do you think of that
> idea?
>
> Also, here's a new version of the patch, which fixes/improves some
> random things I noticed.
…and the question is: is it still relevant? I am not sure to get if the
use-case of the initial motivation is not covered by the current
’git-fetch’. If not, what is the status of this patch: rejected with
which reason or merged?
Thanks,
simon
next prev parent reply other threads:[~2020-12-01 18:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-27 8:15 [bug#31285] [PATCH 0/1] guix: Add git-fetch/impure Chris Marusich
2018-04-27 8:26 ` [bug#31285] [PATCH 1/1] " Chris Marusich
2018-04-30 2:49 ` Chris Marusich
2020-12-01 18:06 ` zimoun [this message]
2020-04-18 15:54 ` [bug#31285] [PATCH 0/1] " sirgazil via Guix-patches via
2020-10-22 0:44 ` Luis Felipe via Guix-patches via
2021-07-14 9:23 ` bug#31285: " Chris Marusich
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=86im9lv1sh.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=31285@debbugs.gnu.org \
--cc=cmmarusich@gmail.com \
--cc=dthompson2@worcester.edu \
--cc=ludo@gnu.org \
--cc=mhw@netris.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).