Re: [git-users] git fatal: The remote end hung up unexpectedly
On Tue, 27 Aug 2013 14:26:09 +0400
Konstantin Khomoutov wrote:
[...]
> Another thing you have to understand, that these "named remote
> repositories" (which are managed by the `git remote` command) is just
> a matter of convenience which
> 1) saves you from typing full URL each time you want to access a
>repository;
> 2) keeps "bookmarks" on the state of the branches of each named remote
>repository when you do `git fetch` on them -- in the form of the
>so-called "remote branches" (these "origin/master" etc).
[...]
I failed to mention that these named remote repositories ("remotes",
for short) are just snippets of configuration in your local Git
repository. They contain an URL used to access the repository and some
other bits of relevant data.
The crucial thing about them is that the names of these remotes are
completely arbitrary and have no relation at all to the names of remote
repositories they describe. For instance, by default, when you do
`git clone URL`, Git creates a single remote named "origin", which
predefined name usually has no resemblance with the name (URL) of the
remote repository which has been cloned; rather it signifies that this
remote is the origin of data maintained in the created local repository.
>From this follows, that:
1) When you adding a named remote, you have to give the `git remote add`
command the URL of the repository, which necessarily includes its
name, as understood by the remote machine ("the server").
2) The name of "the remote" you're creating with `git remote add`
is completely arbitrary and Git makes absolutely no connection
between it and the name of the remote repository as recorded in its
URL. So you're free to pick whatever name you pleases, including
"origin", if it does not yet exist.
--
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [git-users] git fatal: The remote end hung up unexpectedly
On Tue, 27 Aug 2013 01:16:49 -0700 (PDT) Володимир Кулик wrote: > parf@parf:~/work$ git push work > FATAL: W any frontend.epass/parfymer parfymer DENIED by fallthru > (or you mis-spelled the reponame) > fatal: The remote end hung up unexpectedly I suspect you're confusing "named remote repositories" (or simply "named remotes") which are objects in the configuration of your local Git repository with remote repositories existing on another machine which hosts them. Your local Git only ever accesses Git repositories on another machine using their URLs; "user@host/path/to/the/repository" is an example of such an URL (implying the SSH transport is used for communicating with that remote machine). Note that the URL you have used, "gitolite@IP_ADDRESS", does not include any name of an actual repository on the remote host, so it has no sense at all. To get a better idea about this, read the "GIT URLS" section of the git-push manual page [1], and you will see that the path to the repository (on the remote machine) is not an optional part of an URL. That's why Git told you your URL did not look like a valid repository URL when you tried to use it in your `git remote add ...` call. Another thing you have to understand, that these "named remote repositories" (which are managed by the `git remote` command) is just a matter of convenience which 1) saves you from typing full URL each time you want to access a repository; 2) keeps "bookmarks" on the state of the branches of each named remote repository when you do `git fetch` on them -- in the form of the so-called "remote branches" (these "origin/master" etc). The final facet of this "puzzle" is that, it appears, Git repositories on your remote machines are managed by a special front-end tool called `gitolite` [2]. It might be set up in a number of different ways but *usually* it makes the repositories it hosts available without specifying actual pathnames to them in their approptiate URLs, that is, a repository "foobar" is usually accessed by the url like "gitolite@hostname/foobar" or "gitolite@hostname/foobar.git". So, I'd try to go like this. First, inspect the list of named remotes you have by running `git remote` or `git remote -v`. If you have a remote named "frontend.epass", call git remote set-url frontend.epass gitolite@hostname/frontend.epass to update the repository's URL. If you do not have this repository yet, call git remote add frontend.epass gitolite@hostname/frontend.epass 1. https://www.kernel.org/pub/software/scm/git/docs/git-push.html 2. https://github.com/sitaramc/gitolite -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [git-users] git fatal: The remote end hung up unexpectedly
On Tue, 27 Aug 2013 00:59:04 -0700 (PDT) Володимир Кулик wrote: > parf@parf:~/work$ git remote add frontend.epass gitolite@172.27.0.221 > fatal: remote frontend.epass already exists. ^^^ This means a record named "frontend.epass" for a remote repository already exists in the configuration of your local repository. Use git remote set-url frontend.epass gitolite@172.27.0.221 if you just want to change the repository's URL. -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [git-users] git fatal: The remote end hung up unexpectedly
parf@parf:~/work$ git push work FATAL: W any frontend.epass/parfymer parfymer DENIED by fallthru (or you mis-spelled the reponame) fatal: The remote end hung up unexpectedly -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [git-users] git fatal: The remote end hung up unexpectedly
> So the SSH part is all right. In this case, you should check gitolite's > logs maybe. > how can i do it? -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [git-users] git fatal: The remote end hung up unexpectedly
So the SSH part is all right. In this case, you should check gitolite's logs maybe. On 27 Aug 2013 10:08, "Володимир Кулик" wrote: > > The second one is obviously from SSH. Can you simply do ssh >> gito...@172.27.0.221 ? >> >>> parf@parf:~/work$ ssh gitolite@172.27.0.221 >>> >>> PTY allocation request failed on channel 0 >>> >>> hello parfymer, this is gitolite@kitech running gitolite3 v3.1-2-g3eefc06 on git 1.7.9.5 >>> >>> R W frontend.epass >>> >>> Connection to 172.27.0.221 closed. >>> >>> >>> -- > You received this message because you are subscribed to the Google Groups > "Git for human beings" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to git-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [git-users] git fatal: The remote end hung up unexpectedly
> The second one is obviously from SSH. Can you simply do ssh > gito...@172.27.0.221 ? > >> parf@parf:~/work$ ssh gitolite@172.27.0.221 >> >> PTY allocation request failed on channel 0 >> >> hello parfymer, this is gitolite@kitech running gitolite3 v3.1-2-g3eefc06 >>> on git 1.7.9.5 >> >> >>> R W frontend.epass >> >> Connection to 172.27.0.221 closed. >> >> >> -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [git-users] git fatal: The remote end hung up unexpectedly
The second one is obviously from SSH. Can you simply do ssh gitolite@172.27.0.221 ? On 27 Aug 2013 09:59, "Володимир Кулик" wrote: > parf@parf:~/work$ git remote add frontend.epass gitolite@172.27.0.221 > fatal: remote frontend.epass already exists. > > fatal: 'gitolite@172.27.0.221' does not appear to be a git repository > fatal: The remote end hung up unexpectedly > > I want push my project to branch parfymer in gitolite@172.27.0.221 > > Thanks for help > > -- > You received this message because you are subscribed to the Google Groups > "Git for human beings" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to git-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
