unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Phil <phil@beadling.co.uk>
To: Bone Baboon <bone.baboon@disroot.org>
Cc: help-guix@gnu.org
Subject: Re: `guix pull` of an ssh channel fails
Date: Sat, 15 May 2021 08:07:42 +0100	[thread overview]
Message-ID: <87fsyomq4h.fsf@beadling.co.uk> (raw)
In-Reply-To: <87zgwxcp7n.fsf@disroot.org>

Hi

Bone Baboon writes:

> It also looks like there is no problem with Git.  I can clone the
> channel `git clone
> ssh://<user>@<ip-address>:22/absolute/path/to/<git-repo>/`.  Where
> <user> is the user in the output of `ls -l <git-repo>`.

Interesting - I only have one other suggestion - given "git clone" is
working on its own from the same console session as guix is failing.

When you "git clone" and when you "guix pull", I would change the
LogLevel on the ssh config to force verbose logging.  Check that the
same method of authentication is being using in both cases (i.e the
agent and not the id_rsa files).  My theory here is that "git clone" is
using your id_rsa file which is working, and for some reason the
ssh-agent is failing for guix.  This is total speculation on my behalf
of course.

Another cruder way to test this is to move your private key out of your .ssh
directory so ssh doesn't find it by default.  Then manually add it to
your agent.  This should ensure that only the agent will be used by
ssh.  Does the git clone still work?

Apart from this I'm out of ideas I'm afraid.


  reply	other threads:[~2021-05-15  7:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-11 16:32 `guix pull` of an ssh channel fails Bone Baboon
2021-05-12 20:08 ` Bone Baboon
2021-05-13 17:36   ` Phil
2021-05-14 15:25     ` Bone Baboon
2021-05-15  7:07       ` Phil [this message]
2021-05-15  8:29         ` divoplade
2021-05-17 13:39         ` Bone Baboon

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=87fsyomq4h.fsf@beadling.co.uk \
    --to=phil@beadling.co.uk \
    --cc=bone.baboon@disroot.org \
    --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).