unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Lo Peter <peterloleungyau@gmail.com>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: How to access private channel
Date: Sat, 10 Jul 2021 05:19:28 +0000	[thread overview]
Message-ID: <CAEM+zmjSMdK1g0mXCH8SotoauBpHrNP_Q9c86n6HeWjsOh0W3A@mail.gmail.com> (raw)
In-Reply-To: <87a6mv6j1w.fsf@gmail.com>

After some googling, I found two related bug reports of libssh2:
https://github.com/libgit2/pygit2/issues/1013
https://github.com/saltstack/salt/issues/57121

I guess Guix uses libssh2 to process private channels over SSH, if so,
I think doing guix pull first would encounter the same problem.

The suggested workaround is to generate a SSH key in the older PEM
format using the "-m PEM" option of ssh-keygen.
I have tried the workaround and it works for me.

Regards,
Peter Lo

On Sat, Jul 10, 2021 at 1:42 AM Chris Marusich <cmmarusich@gmail.com> wrote:
>
> Lo Peter <peterloleungyau@gmail.com> writes:
>
> > Dear all,
> >
> > I am experimenting with setting up a private channel as a private
> > github repository, then I prepared a channels file for testing:
> >
> > (list (channel
> >        (name 'guix)
> >        (url "https://git.savannah.gnu.org/git/guix.git")
> >        (commit "9904a15a4c838362673c1affdbaf1e83d92fe8ff"))
> >       (channel
> >        (name 'my-guix-pkgs)
> >        (url "git@github.com:peterloleungyau/my-guix-pkgs.git")
> >        (commit "b51d236ebbbdd134bafb64e5092342a2d058ec2a")))
> >
> > Then I try it with:
> > $ guix time-machine -C channels.scm --disable-authentication --
> > environment --ad-hoc python-radian
> > Updating channel 'guix' from Git repository at
> > 'https://git.savannah.gnu.org/git/guix.git'...
> > guix time-machine: warning: channel authentication disabled
> > Updating channel 'my-guix-pkgs' from Git repository at
> > 'git@github.com:peterloleungyau/my-guix-pkgs.git'...
> > guix time-machine: error: Git error: Failed to retrieve list of SSH
> > authentication methods: Failed getting response
> >
> >
> > So it seems the guix daemon cannot use the SSH of my user to access
> > the private git repository? How to get around this? Thanks in advance.
>
> Does it work if you don't try using "time-machine"?  For example:
>
>   guix pull -C channels.scm --disable-authentication
>
> Followed by:
>
>   guix environment --ad-hoc python-radian
>
> Does that work?  I wonder if the "time-machine" part doesn't properly
> handle channels fetched over SSH.
>
> --
> Chris


      reply	other threads:[~2021-07-10  5:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-07  5:40 How to access private channel Lo Peter
2021-07-10  1:42 ` Chris Marusich
2021-07-10  5:19   ` Lo Peter [this message]

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=CAEM+zmjSMdK1g0mXCH8SotoauBpHrNP_Q9c86n6HeWjsOh0W3A@mail.gmail.com \
    --to=peterloleungyau@gmail.com \
    --cc=cmmarusich@gmail.com \
    --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).