List Members: Can anyone give advise on overcoming this "git push" problem? [root@wahoo scap-security-guide]# git push -v Pushing to https://git.fedorahosted.org/git/scap-security-guide.git error: no DAV locking support on https://git.fedorahosted.org/git/scap-security-guide.git/ fatal: git-http-push failed Here is my .git/config [root@wahoo scap-security-guide]# vim .git/config [core] repositoryformatversion = 0 filemode = true bare = false logallrefupdates = true [remote "origin"] fetch = +refs/heads/*:refs/remotes/origin/* url = https://git.fedorahosted.org/git/scap-security-guide.git

[branch "master"] remote = origin merge = refs/heads/master TIA, Rodney. _______________________________________________ scap-security-guide mailing list scap-security-guide(a)lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide

On Wed, 2014-01-29 at 12:18 -0500, Shawn Wells wrote: > On 1/29/14, 10:46 AM, Rodney L. Mercer wrote: > > List Members: > > > > Can anyone give advise on overcoming this "git push" problem? > > > > [root@wahoo scap-security-guide]# git push -v > > Pushing to https://git.fedorahosted.org/git/scap-security-guide.git > > error: no DAV locking support on > > https://git.fedorahosted.org/git/scap-security-guide.git/ > > fatal: git-http-push failed > > > > Here is my .git/config > > [root@wahoo scap-security-guide]# vim .git/config > > > > [core] > > repositoryformatversion = 0 > > filemode = true > > bare = false > > logallrefupdates = true > > [remote "origin"] > > fetch = +refs/heads/*:refs/remotes/origin/* > > url = https://git.fedorahosted.org/git/scap-security-guide.git > > Use ssh for commit. e.g.: > > [remote "origin"] > url = ssh://git.fedorahosted.org/git/scap-security-guide.git > fetch = +refs/heads/*:refs/remotes/origin/* > > > > [branch "master"] > > remote = origin > > merge = refs/heads/master > > > > > > TIA, > > > > Rodney. > > > > > > > > _______________________________________________ > > scap-security-guide mailing list > > scap-security-guide(a)lists.fedorahosted.org > > https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide > > Do I need a login account setup on the server side:? Here is what I am now getting on the "git push": [root@wahoo scap-security-guide]# git push -v Pushing to ssh://git.fedorahosted.org/git/scap-security-guide.git Permission denied (publickey). fatal: The remote end hung up unexpectedly Here is my "git config" [root@wahoo scap-security-guide]# git config --list user.name=Rodney Mercer user.email=rmercer(a)harris.com core.repositoryformatversion=0 core.filemode=true core.bare=false core.logallrefupdates=true remote.origin.fetch=+refs/heads/*:refs/remotes/origin/* remote.origin.url=ssh://git.fedorahosted.org/git/scap-security-guide.git branch.master.remote=origin branch.master.merge=refs/heads/master

On 1/29/14, 2:34 PM, Rodney L. Mercer wrote: > On Wed, 2014-01-29 at 14:16 -0500, Rodney L. Mercer wrote: >> > >> >On Wed, 2014-01-29 at 12:18 -0500, Shawn Wells wrote: >>> > >On 1/29/14, 10:46 AM, Rodney L. Mercer wrote: >>>> > > >List Members: >>>> > > > >>>> > > >Can anyone give advise on overcoming this "git push" problem? >>>> > > > >>>> > > >[root@wahoo scap-security-guide]# git push -v >>>> > > >Pushing tohttps://git.fedorahosted.org/git/scap-security-guide.git >>>> > > >error: no DAV locking support on >>>> > > >https://git.fedorahosted.org/git/scap-security-guide.git/ >>>> > > >fatal: git-http-push failed >>>> > > > >>>> > > >Here is my .git/config >>>> > > >[root@wahoo scap-security-guide]# vim .git/config >>>> > > > >>>> > > >[core] >>>> > > > repositoryformatversion = 0 >>>> > > > filemode = true >>>> > > > bare = false >>>> > > > logallrefupdates = true >>>> > > >[remote "origin"] >>>> > > > fetch = +refs/heads/*:refs/remotes/origin/* >>>> > > > url =https://git.fedorahosted.org/git/scap-security-guide.git >>> > > >>> > >Use ssh for commit. e.g.: >>> > > >>> > >[remote "origin"] >>> > > url =ssh://git.fedorahosted.org/git/scap-security-guide.git >>> > > fetch = +refs/heads/*:refs/remotes/origin/* >>> > > >>> > > >>>> > > >[branch "master"] >>>> > > > remote = origin >>>> > > > merge = refs/heads/master >>>> > > > >>>> > > > >>>> > > >TIA, >>>> > > > >>>> > > >Rodney. >>>> > > > >>>> > > > >>>> > > > >>>> > > >_______________________________________________ >>>> > > >scap-security-guide mailing list >>>> > > >scap-security-guide(a)lists.fedorahosted.org >>>> > > >https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide >>> > > >>> > > >> > >> >Do I need a login account setup on the server side:? >> > >> >Here is what I am now getting on the "git push": >> >[root@wahoo scap-security-guide]# git push -v >> >Pushing tossh://git.fedorahosted.org/git/scap-security-guide.git >> >Permission denied (publickey). >> >fatal: The remote end hung up unexpectedly >> > >> >Here is my "git config" >> >[root@wahoo scap-security-guide]# git config --list >> >user.name=Rodney Mercer >> >user.email=rmercer(a)harris.com >> >core.repositoryformatversion=0 >> >core.filemode=true >> >core.bare=false >> >core.logallrefupdates=true >> >remote.origin.fetch=+refs/heads/*:refs/remotes/origin/* >> >remote.origin.url=ssh://git.fedorahosted.org/git/scap-security-guide.git >> >branch.master.remote=origin >> >branch.master.merge=refs/heads/master >> > > Sorry for the noise. > Looking through the Eric's latest commit to > > docs/SCAP_and_STIG_Workshop/en-US/Content_Customization.xml > > I believe that I need to gain commit access. Noticed & approved the request (in actuality, I thought you already had it due to prior patches). Welcome to the commiters club ;) Shawn _______________________________________________ scap-security-guide mailing list scap-security-guide(a)lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide