From rmercer at harris.com Thu Aug 20 11:36:20 2015
Content-Type: multipart/mixed; boundary="===============2680871010141699399=="
MIME-Version: 1.0
From: Mercer, Rodney <rmercer at harris.com>
To: scap-security-guide at lists.fedorahosted.org
Subject: Re: git push error: no DAV locking support
Date: Wed, 29 Jan 2014 14:34:20 -0500
Message-ID: <1391024060.31569.223.camel@osc145>
In-Reply-To: 1391022981.31569.218.camel@osc145

--===============2680871010141699399==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable



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(a)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(a)wahoo scap-security-guide]# vim .git/config
> > >
> > > [core]
> > >          repositoryformatversion =3D 0
> > >          filemode =3D true
> > >          bare =3D false
> > >          logallrefupdates =3D true
> > > [remote "origin"]
> > >          fetch =3D +refs/heads/*:refs/remotes/origin/*
> > >          url =3D https://git.fedorahosted.org/git/scap-security-guide=
.git
> > =

> > Use ssh for commit. e.g.:
> > =

> > [remote "origin"]
> >          url =3D ssh://git.fedorahosted.org/git/scap-security-guide.git
> >          fetch =3D +refs/heads/*:refs/remotes/origin/*
> > =

> > =

> > > [branch "master"]
> > >          remote =3D origin
> > >          merge =3D 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(a)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(a)wahoo scap-security-guide]# git config --list
> user.name=3DRodney Mercer
> user.email=3Drmercer(a)harris.com
> core.repositoryformatversion=3D0
> core.filemode=3Dtrue
> core.bare=3Dfalse
> core.logallrefupdates=3Dtrue
> remote.origin.fetch=3D+refs/heads/*:refs/remotes/origin/*
> remote.origin.url=3Dssh://git.fedorahosted.org/git/scap-security-guide.git
> branch.master.remote=3Dorigin
> branch.master.merge=3Drefs/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 (=E2=80=9CACK=E2=80=
=9D) 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=3D"https://fedorahosted.org/mailman/listinfo/scap-security-guide">maili=
ng list</ulink>, it's how developers and users communicate.</member>
+ <member>Create your <ulink
url=3D"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=3D"https://admin.fedoraproject.org/accounts/group/view/gitscap-security=
-guide">request membership to the SCAP Security Guide project</ulink>.</mem=
ber>
+ <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>



--===============2680871010141699399==--