sm-discuss AT lists.ibiblio.org
Subject: Public SourceMage Discussion List
List archive
- From: Vlad Glagolev <stealth AT tiberian.ru>
- To: sm-discuss AT lists.ibiblio.org
- Cc: Eric Sandall <eric AT sandall.us>
- Subject: Re: [SM-Discuss] unable to 'git pull'
- Date: Thu, 16 May 2019 13:13:10 -0700
Not sure how it worked before, but I noticed one detail:
/smgl/grimoire is a directory containing all other grimoires:
- binary.git
- games.git
- grimoire-p4_history.git
- xorg-modular.git
- z-rejected.git
so it doesn't have the repository itself. Instead, grimoire.git should
be used. I double-checked my config:
--[ snip ]--
[remote "origin"]
url = ssh://vlad AT scm.sourcemage.org/smgl/grimoire.git
fetch = +refs/heads/*:refs/remotes/origin/*
--[ snip ]--
On Thu, 16 May 2019 11:43:46 -0700
Eric Sandall via SM-Discuss <sm-discuss AT lists.ibiblio.org> wrote:
> On 2/26/19 06:06, Treeve Jelbert wrote:
> > Has something changed?
> >
> > treeve@Horos:/var/git/smgl$ git pull
> > The authenticity of host 'scm.sourcemage.org (45.77.64.110)' can't be
> > established.
> > ECDSA key fingerprint is
> > SHA256:Rgr4SKm37zevNyugBszf9lDvAov4pLd/zLltfF16Ir4.
> > Are you sure you want to continue connecting (yes/no)? yes
> > Warning: Permanently added 'scm.sourcemage.org,45.77.64.110' (ECDSA)
> > to the list of known hosts.
> > treeve AT scm.sourcemage.org's password:
> > Received disconnect from 45.77.64.110 port 22:2: Too many
> > authentication failures
> > Disconnected from 45.77.64.110 port 22
> > fatal: Could not read from remote repository.
> >
> > Please make sure you have the correct access rights
> > and the repository exists.
>
> I'm still having issues with /git pull/ .
>
> sandalle@tendriculous:~/scm/git/smgl/grimoire$ git pull --verbose
> ssh_exchange_identification: read: Connection reset by peer
> fatal: Could not read from remote repository.
>
> Please make sure you have the correct access rights
> and the repository exists.
> sandalle@tendriculous:~/scm/git/smgl/grimoire$ man git
> sandalle@tendriculous:~/scm/git/smgl/grimoire$ GIT_TRACE=true git pull
> 11:34:09.763329 git.c:418 trace: built-in: git pull
> 11:34:09.775592 run-command.c:643 trace: run_command: git
> fetch --update-head-ok
> 11:34:09.777750 git.c:418 trace: built-in: git fetch
> --update-head-ok
> 11:34:09.789551 run-command.c:643 trace: run_command: unset
> GIT_PREFIX; ssh scm.sourcemage.org 'git-upload-pack
> '\''/smgl/grimoire'\'''
> ssh_exchange_identification: read: Connection reset by peer
> fatal: Could not read from remote repository.
>
> Please make sure you have the correct access rights
> and the repository exists.
>
>
> sandalle@tendriculous:~/scm/git/smgl$ cat grimoire/.git/config
> [core]
> repositoryformatversion = 0
> filemode = true
> bare = false
> logallrefupdates = true
> [remote "origin"]
> url = ssh://scm.sourcemage.org/smgl/grimoire
> fetch = +refs/heads/*:refs/remotes/origin/*
> [branch "master"]
> remote = origin
> merge = refs/heads/master
> [user]
> name = Eric Sandall
> email = sandalle AT sourcemage.org
> [color]
> branch = auto
> status = auto
> diff = auto
> [branch "drupal.stgit"]
> stackformatversion = 2
>
>
> I've cleared out any reference to sourcemage.org from ~/.ssh/known_hosts
> and I the only rule in ~/.ssh/config that I have which would affect this
> is "Protocol 2,1".
>
> Even trying to clone a fresh repo gives me the above:
>
> $ GIT_TRACE=true git clone ^C
> (reverse-i-search)`clone': for repo in archspecs binary castfs
> cauldron games grimoire prometheus quill rdp sorcery z-rejected; do
> git ^Cone ssh://scm.sourcemage.org/smgl/${repo}; done
> sandalle@tendriculous:~$ GIT_TRACE=true git clone
> ssh://scm.sourcemage.org/smgl/grimoire
> 11:37:19.423955 git.c:418 trace: built-in: git clone
> ssh://scm.sourcemage.org/smgl/grimoire
> Cloning into 'grimoire'...
> 11:37:19.426918 run-command.c:643 trace: run_command: unset
> GIT_DIR; ssh scm.sourcemage.org 'git-upload-pack '\''/smgl/grimoire'\'''
> ssh_exchange_identification: read: Connection reset by peer
> fatal: Could not read from remote repository.
>
> Please make sure you have the correct access rights
> and the repository exists.
>
>
> Did I miss a step or get purged, perhaps? ;) Here's my public SSH key,
> if it's needed:
>
> ssh-rsa
>
> AAAAB3NzaC1yc2EAAAABIwAAAIEA3DWkZOByKI7hb40Zd7UsHxkxfbdDS20HK1KS9bQ5CAVcjYLRVnDDgXva5dGxafVZ47/j4AzVWbgT2xcVTFWPJMLQQSncKOCoPrffDPBIX+R8zEtt7VMk1nV+Uvjg+CchTshoCBbAG0A0AwwkgXs7SfJNcxc01rgpIEAWlZMytZ8=
> eric AT sandall.us
>
>
> Also, my @sourcemage.org hasn't worked since the forwarding got turned
> off, so please don't send to that address. ;)
>
> -sandalle
--
Vlad Glagolev <stealth AT tiberian.ru>
Attachment:
pgpZ7KyW718Ik.pgp
Description: PGP signature
-
Re: [SM-Discuss] unable to 'git pull',
Eric Sandall, 05/16/2019
-
Re: [SM-Discuss] unable to 'git pull',
Vlad Glagolev, 05/16/2019
-
Re: [SM-Discuss] unable to 'git pull',
Eric Sandall, 05/16/2019
- Re: [SM-Discuss] unable to 'git pull', Vlad Glagolev, 05/16/2019
-
Re: [SM-Discuss] unable to 'git pull',
Eric Sandall, 05/16/2019
- Re: [SM-Discuss] unable to 'git pull', Eric Sandall, 05/16/2019
-
Re: [SM-Discuss] unable to 'git pull',
Vlad Glagolev, 05/16/2019
Archive powered by MHonArc 2.6.24.