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.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
On Wed, Jan 29, 2014 at 10:46:56AM -0500, Rodney L. Mercer wrote:
fatal: git-http-push failed
The Internetz pointed me to a Stack Overflow article[0] that says to do a 'git gc' and then a push. I haven't read up on what 'git gc' does but maybe this will be an answer for you?
[0] https://stackoverflow.com/questions/13868155/git-http-push-failed
- -- Eric
- -------------------------------------------------- Eric "Sparks" Christensen Red Hat, Inc - Product Security Team
sparks@redhat.com - sparks@fedoraproject.org 097C 82C3 52DF C64A 50C2 E3A3 8076 ABDE 024B B3D1 - --------------------------------------------------
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@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@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@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 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 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@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@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.
+ <title>So, you wanna be a developer?</title> + <para>Welcome! Making changes to the project requires posting a patch to the mailing list, so that it can be vetted. Once there, another commit-level project member must issue acknowledgement (“ACK”) to accept it, and then it can be pushed. Assuming another project member has not issued a NACK in protest first, that is! The following instructions assume familiarity with git and git-send-email, but project members are happy to provide tips if you encounter any roadblocks.</para> + <para>To properly join the project you must first establish a few required accounts: + <simplelist> + <member>Join the <ulink url="https://fedorahosted.org/mailman/listinfo/scap-security-guide">mailing list</ulink>, it's how developers and users communicate.</member> + <member>Create your <ulink url="https://admin.fedoraproject.org/accounts/">FedoraHosted account</ulink>. It formally registers you as a developer, and allows you to upload your public SSH key (required for commits).</member> + <member>Once your FedoraHosted account is created, <ulink url="https://admin.fedoraproject.org/accounts/group/view/gitscap-security-guide">request membership to the SCAP Security Guide project</ulink>.</member> + <member>Lastly, review a few coding standards: How to Create a New Guidance Item in XCCDF and How to Create a New Compliance Check in OVAL</member> + </simplelist> + </para> + </section>
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@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@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
On Wed, 2014-01-29 at 22:41 -0500, Shawn Wells wrote:
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@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@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@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide
Yay. the push finally took. Thanks Shawn. Now that Ensure All Files Are Owned by a User is updated, I need to work on Ensure All Files Are Owned by a Group as it suffers from the same affliction.
Rodney.
scap-security-guide@lists.fedorahosted.org