unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Arun Isaac <arunisaac@systemreboot.net>
Cc: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: Re: Pulling from guix git repo fails
Date: Thu, 3 Aug 2017 13:45:16 -0400	[thread overview]
Message-ID: <20170803174516.GA26721@jasmine.lan> (raw)
In-Reply-To: <ae1728b8.ADkAAChENWoAAAAAAAAAAAPHPkIAAAACwQwAAAAAAAW9WABZg1fY@mailjet.com>

[-- Attachment #1: Type: text/plain, Size: 937 bytes --]

On Thu, Aug 03, 2017 at 10:35:19PM +0530, Arun Isaac wrote:
> 
> I'm not able to pull from the guix repo. Has some URL changed? I have
> commit access.
> 
> $ git pull
> 
> ssh: connect to host git.sv.gnu.org port 22: Connection timed out
> fatal: Could not read from remote repository.
> 
> Please make sure you have the correct access rights
> and the repository exists.
> 
> $ git remote -v
> 
> origin	ssh://arunisaac@git.sv.gnu.org/srv/git/guix.git (fetch)
> origin	ssh://arunisaac@git.sv.gnu.org/srv/git/guix.git (push)
 
This doesn't answer your question directly, but I pull from the HTTPS
URL:

https://git.savannah.gnu.org/r/guix.git

I never tried pulling over SSH, although I believe Savannah intends to
support it. Before they served Git over HTTPS, pulling over SSH was the
recommended way to pull over an authenticated protocol.

You can set different URLs for push and pull with `git remote`.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2017-08-03 17:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-03 17:05 Pulling from guix git repo fails Arun Isaac
2017-08-03 17:45 ` Leo Famulari [this message]
2017-08-03 18:57   ` Arun Isaac
2017-08-03 18:09 ` Tobias Geerinckx-Rice

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=20170803174516.GA26721@jasmine.lan \
    --to=leo@famulari.name \
    --cc=arunisaac@systemreboot.net \
    --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).