unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Luis Felipe <luis.felipe.la@protonmail.com>
To: Lo Peter <peterloleungyau@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: SSH in git-fetch
Date: Tue, 13 Jul 2021 22:30:31 +0000	[thread overview]
Message-ID: <r00ApPlpIYKLyCkUfL38E5GJuMqhMJ-groP-70ghP2bzgE4uresXQLSjrJ4dYVOwZ1TJfhpRt0HjwS_HkiWad4CBw1qJ5q3tF6wN1FtouOk=@protonmail.com> (raw)
In-Reply-To: <CAEM+zmjXVqARy5uPS=Hydp49-pXDUJ1dwgF-B5SLcb13=soz3g@mail.gmail.com>

Hi,

On Tuesday, July 13th, 2021 at 2:38 PM, Lo Peter <peterloleungyau@gmail.com> wrote:

> Dear all,
>
> I am experimenting with writing a package definition for an example R
>
> package (https://github.com/jennybc/foofactors) in a PRIVATE channel,
>
> where the R source is also at a PRIVATE github repository.
>
> While the private channel works with proper setup of SSH key (that
>
> needs to be in PEM format due to a bug in libssh2), I am having
>
> trouble with the private git repository for package source.
>
> Is it that git-fetch does not support fetching over SSH?

For what it's worth, I have a private channel that defines packages of my private projects in GitLab. I haven't used the channel for a while, but SSH authentication worked by using "git-checkout" records instead of "origin" records in package "source" fields. For instance:

(source
 (git-checkout
  (url "git@gitlab.com:luis-felipe/guile-lab.git")
  (commit (string-append "v" version))))




  parent reply	other threads:[~2021-07-13 22:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-13 14:38 SSH in git-fetch Lo Peter
2021-07-13 21:47 ` Leo Prikler
2021-07-14 10:05   ` Lo Peter
2021-07-13 22:30 ` Luis Felipe [this message]
2021-07-14 10:06   ` Lo Peter

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='r00ApPlpIYKLyCkUfL38E5GJuMqhMJ-groP-70ghP2bzgE4uresXQLSjrJ4dYVOwZ1TJfhpRt0HjwS_HkiWad4CBw1qJ5q3tF6wN1FtouOk=@protonmail.com' \
    --to=luis.felipe.la@protonmail.com \
    --cc=guix-devel@gnu.org \
    --cc=peterloleungyau@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 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).