From otoomet @end|ng |rom gm@||@com  Sat Jun 29 05:25:35 2019
From: otoomet @end|ng |rom gm@||@com (Ott Toomet)
Date: Fri, 28 Jun 2019 20:25:35 -0700
Subject: [Rd] R-Forge > GitHub?
In-Reply-To: <fb319697-6408-17b5-30a1-7a8f9d8da928@prodsyse.com>
References: <71f66de5-e1aa-5649-b07a-6cf79f9b07bc@prodsyse.com>
 <cb4218b1-7fcc-80cb-18ab-361b93a3177e@prodsyse.com>
 <8d6c6dd4-d231-ecc7-c584-6e08f93a81e5@gmail.com>
 <89645BC9-C6BF-4E57-8AA0-9F426BA8AC5E@rstudio.com>
 <CA+rDMK+HXUKnA0j49czOf99M62QBfnyO36Sf1MBEe8a5AO-+XA@mail.gmail.com>
 <06a9569b-5b68-a288-8c4f-1537120a5213@prodsyse.com>
 <CABtg=Km5cdEWyUM55FEiabNdZdHvJoELHZ7RCRMPgQhUg9Gc6w@mail.gmail.com>
 <6d983b3b-62ea-3bb9-724a-01baaff51e70@gmail.com>
 <fb319697-6408-17b5-30a1-7a8f9d8da928@prodsyse.com>
Message-ID: <CAMMJQ0a7ZtndwL8YYas6+k3BRDtAFizAuaacONQ6i6HmrQMTeA@mail.gmail.com>

Apparently your username/password are wrong.  Can you clone/push from other
repos?

You do not need authorization when cloning a public repo, so even incorrect
credentials may work (haven't tested this though).  But for push you have
to have that in order.

I suggest you create ssh keys, upload those to GH, and use ssh
authorization instead of https.

Cheers,
Ott

On Fri, Jun 28, 2019 at 8:18 PM Spencer Graves <spencer.graves at prodsyse.com>
wrote:

> Thanks to Duncan, Henrik and Henrik, Brian, and G?bor:
>
>
>        I created a local copy of the new GitHub version using the
> following:
>
> git clone https://sbgraves237:mypassword at github.com/sbgraves237/Ecdat.git
>
>
>
>        That worked in the sense that I got a local copy.  However, after
> I rolled the version number and did "git commit" on the DESCRIPTION
> files, my "git push" command generated the following:
>
>
> remote: Invalid username or password.
> fatal: Authentication failed for
> 'https://sbgraves237:mypassword at github.com/sbgraves237/Ecdat.git/'
>
>
>        What am I missing?  [Note:  I used my actual GitHub password in
> place of "mypassword" here, and this "Authentication failed" message
> reported the GitHub password I used here.]
>
>
>        Thanks,
>        Spencer
>
>
> p.s.  I'm doing this under macOS Mojave 10.14.5.  Also,  I added
> ".onAttach" functions to the R-Forge versions as Brian G. Peterson
> suggested.  That seemed to work fine.
>
>
> On 2019-06-28 07:13, Duncan Murdoch wrote:
> > On 28/06/2019 6:26 a.m., G?bor Cs?rdi wrote:
> >
> >> Instead, you can do as Duncan suggested, and put a README in your
> >> R-Forge
> >> repository, that points to *your* GitHub repositor(y/ies). Then the
> >> https://github.com/rforge/ecdat read only mirror will pick this up
> >> and will
> >> point there as well.
> >
> > Just for the record:  that was Henrik Singmann's suggestion, I just
> > agreed with it.
> >
> > Duncan Murdoch
> >
>
>
>         [[alternative HTML version deleted]]
>
> ______________________________________________
> R-devel at r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-devel
>

	[[alternative HTML version deleted]]



[Rd] R-Forge > GitHub?
Ott Toomet