From: Lo Peter <peterloleungyau@gmail.com>
To: Luis Felipe <luis.felipe.la@protonmail.com>
Cc: guix-devel@gnu.org
Subject: Re: SSH in git-fetch
Date: Wed, 14 Jul 2021 18:06:53 +0800 [thread overview]
Message-ID: <CAEM+zmgkTnyUKAMr59YimjOb6QfcGEKKAbCjch8Tg4n=RzLJng@mail.gmail.com> (raw)
In-Reply-To: <r00ApPlpIYKLyCkUfL38E5GJuMqhMJ-groP-70ghP2bzgE4uresXQLSjrJ4dYVOwZ1TJfhpRt0HjwS_HkiWad4CBw1qJ5q3tF6wN1FtouOk=@protonmail.com>
Dear Luis,
Thanks for the suggested workaround. I have tried it and can confirm
that it works. Thanks.
Regards,
Peter Lo
On Wed, Jul 14, 2021 at 6:30 AM Luis Felipe
<luis.felipe.la@protonmail.com> wrote:
>
> 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))))
>
>
prev parent reply other threads:[~2021-07-14 10:14 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
2021-07-14 10:06 ` 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+zmgkTnyUKAMr59YimjOb6QfcGEKKAbCjch8Tg4n=RzLJng@mail.gmail.com' \
--to=peterloleungyau@gmail.com \
--cc=guix-devel@gnu.org \
--cc=luis.felipe.la@protonmail.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).