Thanks for reporting back!

On Wed, May 7, 2014 at 11:13 PM, Morgan McKenzie <rmtmcken...@gmail.com> wrote:
> With gitlab support's help I've traced the issue to these lines in my
> .gitconfig
>
> [remote "origin"]
>     receivepack = git receive-pack
>
> I don't actually remember why I had that option, or if maybe another program
> set it for me.... but once removed I had no problem. But if anyone else has
> the same issue, removing that solves the problem...
>
>
> Morgan McKenzie
>
>
>
>
> On Tuesday, 6 May 2014 10:54:53 UTC-7, Morgan McKenzie wrote:
>>
>> Will do, thanks.
>>
>> On Monday, 5 May 2014 14:19:39 UTC-7, Morgan McKenzie wrote:
>>>
>>> Hi,
>>>
>>> I've just signed up for an account with GitLab.com and am trying to
>>> initialize a private repository. I've followed the instructions and am able
>>> to clone the repository, but when I try to push it fails. I was able to push
>>> over https just to test it but that is not an option I can keep using.
>>>
>>> I'm running ubuntu with git version 1.8.3.2, OpenSSH_6.2p2
>>> Ubuntu-6ubuntu0.3, OpenSSL 1.0.1e 11 Feb 2013
>>>
>>> I have a private key and public key set up from the browser - I get the
>>> success message with :
>>> $ ssh -vT git@gitlab
>>>
>>>> debug1: Offering RSA public key: /home/morgan/.ssh/id_gitlab
>>>>
>>>> debug1: Server accepts key: pkalg ssh-rsa blen 279
>>>>
>>>> debug1: Authentication succeeded (publickey).
>>>>
>>>> Authenticated to gitlab.com ([54.243.197.170]:22).
>>>>
>>>> debug1: channel 0: new [client-session]
>>>>
>>>> debug1: Requesting no-more-sessi...@openssh.com
>>>>
>>>> debug1: Entering interactive session.
>>>>
>>>> debug1: Remote: Forced command.
>>>>
>>>> debug1: Remote: Port forwarding disabled.
>>>>
>>>> debug1: Remote: X11 forwarding disabled.
>>>>
>>>> debug1: Remote: Agent forwarding disabled.
>>>>
>>>> debug1: Remote: Pty allocation disabled.
>>>>
>>>> debug1: Remote: Forced command.
>>>>
>>>> debug1: Remote: Port forwarding disabled.
>>>>
>>>> debug1: Remote: X11 forwarding disabled.
>>>>
>>>> debug1: Remote: Agent forwarding disabled.
>>>>
>>>> debug1: Remote: Pty allocation disabled.
>>>>
>>>> debug1: Sending environment.
>>>>
>>>> debug1: Sending env LANG = en_CA.UTF-8
>>>>
>>>> Welcome to GitLab, Morgan McKenzie!
>>>
>>>
>>> And my .git config:
>>>
>>>>
>>>> [core]
>>>>
>>>>   repositoryformatversion = 0
>>>>
>>>>   filemode = true
>>>>
>>>>   bare = false
>>>>
>>>>   logallrefupdates = true
>>>>
>>>> [remote "origin"]
>>>>
>>>>   url = git@gitlab:rmtmckenzie/portfolio-mm.git
>>>>
>>>>   fetch = +refs/heads/*:refs/remotes/origin/*
>>>>
>>>> [branch "master"]
>>>>
>>>> remote = origin
>>>>
>>>> merge = refs/heads/master
>>>
>>>
>>>  When I try pushing I get this error:
>>> fatal: protocol error: bad line length character: Not
>>>
>>>
>>> I've done quite a lot of googling on this and didn't come up with too
>>> much, but did find that someone mentioned trying
>>> $ ssh g...@gitlab.com git-receive-pack rmtmckenzie/portfolio-mm.git
>>>
>>> which results in:
>>>>
>>>>  <52 characters in hex> refs/heads/master report-status delete-refs
>>>> side-band-64k quiet ofs-delta agent=git/1.8.4.1
>>>>
>>>> 0000
>>>
>>> and a prompt which accepts number, but if I type a word (e.g. Not) it
>>> returns the same error as when I try to push.
>>>
>>>
>>> Any help would be much appreciated!
>>>
>>> Morgan McKenzie
>>>
>>>
>>>
>>>
> --
> You received this message because you are subscribed to the Google Groups
> "GitLab" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to gitlabhq+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"GitLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to gitlabhq+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/gitlabhq/CAEG31mMEQe1psqqMJX7QUnoZbgca6b_fW5qzy%3DB030NwNxGKAw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to