From @pencer@gr@ve@ @end|ng |rom prod@y@e@com  Thu Jul  4 06:30:38 2019
From: @pencer@gr@ve@ @end|ng |rom prod@y@e@com (Spencer Graves)
Date: Wed, 3 Jul 2019 23:30:38 -0500
Subject: [Rd] R-Forge > GitHub?
In-Reply-To: <CAMMJQ0a0ONoBnZnnn9wq3a4ey336t24CTLrf_RZS99u_hMKrjA@mail.gmail.com>
References: <71f66de5-e1aa-5649-b07a-6cf79f9b07bc@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>
 <CAMMJQ0a7ZtndwL8YYas6+k3BRDtAFizAuaacONQ6i6HmrQMTeA@mail.gmail.com>
 <3f01d7bc-ed20-1a39-25bc-ce7d34e22398@prodsyse.com>
 <CAFDcVCR9=WMJRmT3RVZxaQaWxQ4EciojC5ct4K=PrSjuJKtKNw@mail.gmail.com>
 <c9f1e823-9384-1f9f-0d70-e6ccbe8e9075@prodsyse.com>
 <CAPPM_gQ6Ef0+FYz0NrywwiPyW9O2Wwcms8sbmQATp-jcgyYhBA@mail.gmail.com>
 <CAPPM_gQm4JEDZnqg1xPN8U7j2y76=bBNsmxB0dAm0Z7ujmrXzQ@mail.gmail.com>
 <593d5e40-611e-3fcc-c131-6fb7de1130b9@prodsyse.com>
 <CAMMJQ0a0ONoBnZnnn9wq3a4ey336t24CTLrf_RZS99u_hMKrjA@mail.gmail.com>
Message-ID: <a896f66e-6727-cb45-9cd6-60c7ffdc2d9f@prodsyse.com>

 ????? Thanks so much for your help.


 ????? Now your "git push -u origin master" was "![rejected]", after 
creating a new SSH and after your "git clone" and other "git remote 
rename ..." commands seemed to work:


$ git clone git at github.com:joshuaulrich/tmp-ecfun.git Ecdat
# Cloning into 'Ecdat'...<snip> done.

$ cd Ecdat/
$ git remote rename origin tmp
$ git remote add origin https://github.com/sbgraves237/Ecdat
$ git push -u origin master
#[Username & password OK]
To https://github.com/sbgraves237/Ecdat
 ?! [rejected]??????? master -> master (fetch first)
error: failed to push some refs to 'https://github.com/sbgraves237/Ecdat'
hint: Updates were rejected because the remote contains work that you do
hint: not have locally. This is usually caused by another repository pushing
hint: to the same ref. You may want to first integrate the remote changes
hint: (e.g., 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.
SpenceravessMBP:Ecdat sbgraves$


 ????? Suggestions?
 ????? Thanks again,
 ????? Spencer Graves


On 2019-07-01 01:05, Ott Toomet wrote:
> Apparently you created id_rsa key pair with a passphrase. Passphrase 
> is like an additional password protection layer on your ssh key.? I 
> don't know how did you create it.? But you can always create a new one 
> (you should delete the old one before you create a new one) using the 
> shell command 'ssh-keygen'.? It asks for a passphrase, just push enter 
> for an empty passphrase (twice).? You also have to update the ssh 
> public key (id_rsa.pub) on github by supplying the new public key 
> (id_rsa.pub).
>
> There are some implications you should be aware of:
> * if you delete id_rsa*, you cannot use any ssh authorization that 
> relies on this key any more (that's why you have to update on GH).? 
> From the what you write (... created 2 days ago) I guess you do not 
> use these keys elsewhere but I may be wrong.
> * if you supply empty passphrase, you bypass the optional extra 
> security layer.? I think this is OK for open source software 
> development on your personal computer but your preferences/situation 
> may differ.
> * You cannot use the same keys with passphrase if they are created 
> without one.? This is likely not an issue, but if it turns out to be a 
> problem, you can either add passphrase to the default keys, or create 
> another set of keys, passphrase protected.
>
> Cheers,
> Ott
>
>
> On Sun, Jun 30, 2019 at 9:51 PM Spencer Graves 
> <spencer.graves at prodsyse.com <mailto:spencer.graves at prodsyse.com>> wrote:
>
>
>
>     On 2019-06-30 06:58, Joshua Ulrich wrote:
>     <snip>
>
>     > I imported both packages into separate repositories:
>     > https://github.com/joshuaulrich/tmp-ecdat
>     > https://github.com/joshuaulrich/tmp-ecfun
>     >
>     > I changed your email address on your R-Forge commits to match your
>     > GitHub email address, so R-Forge commits would be associated
>     with your
>     > GitHub account.? I also omitted the "move" commit from Ecdat,
>     and the
>     > "obsolete > GitHub" commits from both packages.? I've attached a
>     file
>     > with the commands I used, if anyone is interested.
>     >
>     > You can use my repos by cloning them to your local machine, adding
>     > your repos as new remotes, and pushing to them.? You would need
>     to run
>     > these commands (untested):
>     >
>     > ### clone my GitHub repo to your machine
>     > git clone git at github.com:joshuaulrich/tmp-ecfun.git Ecdat
>
>
>     Thanks so much.? Sadly, I'm still having troubles.? This "git
>     clone ..."
>     generates:
>
>
>     Enter passphrase for key '/Users/sbgraves/.ssh/id_rsa':
>
>
>     ?????? Sadly, I don't know the passphrase it's looking for here,
>     and I
>     don't know how to find what it's looking for.? Under GitHub >
>     Settings >
>     "SSH and GPG keys", I see an SSH key dated two days ago, when I
>     cloned
>     Ecdat from within RStudio.? And in "~.ssh" I see files id_rsa and
>     id_rsa.pub, both created two days ago.
>
>
>     ?????? What do you suggest I try to get past this?
>
>
>     ?????? Thanks again for all your help.
>
>
>     ?????? Spencer Graves
>
>     > cd Ecdat
>     > ### rename my GitHub repo remote from 'origin' to 'tmp'
>     > git remote rename origin tmp
>     > ### add your GitHub repo remote as 'origin'
>     > ### NOTE: this should be a new, clean repo.
>     > ###? ? Rename your existing 'Ecdat' so you don't overwrite it
>     > git remote add origin https://github.com/sbgraves237/Ecdat
>     > ### push to your GitHub repo
>     > git push -u origin master
>     >
>     > Then you need to run similar commands for Ecfun.
>     >
>     > Best,
>     > Josh
>     >
>     >>>? ? ? ? ?Thanks,
>     >>>? ? ? ? ?Spencer
>     >>>
>     >>>
>     >>> On 2019-06-29 14:09, Henrik Bengtsson wrote:
>     >>>> On Sat, Jun 29, 2019 at 9:43 AM Spencer Graves
>     >>>> <spencer.graves at prodsyse.com
>     <mailto:spencer.graves at prodsyse.com>> wrote:
>     >>>>> Hi, Ott et al.:
>     >>>>>
>     >>>>>
>     >>>>>? ? ? ? ? What's the best way to get "Travis CI" to build and
>     test the two
>     >>>>> packages, Ecdat and Ecfun, that have long been combined in
>     the Ecdat
>     >>>>> project?
>     >>>>>
>     >>>>>
>     >>>>>? ? ? ? ? Following Ott's advice and studying studying
>     Wickham's "R
>     >>>>> Packages" (http://r-pkgs.had.co.nz/), I was able to
>     configure RStudio so
>     >>>>> it would sync using git with
>     "GitHub.com/sbgraves237/Ecdat".? However,
>     >>>>> when I tried to configure "Travis CI", it said, "No
>     DESCRIPTION file
>     >>>>> found, user must supply their own install and script steps".
>     >>>>>
>     >>>>>
>     >>>>>? ? ? ? ? Earlier in this thread, I think someone suggested I
>     make the
>     >>>>> Ecdat and Ecfun packages separate projects on GitHub (though
>     I can't
>     >>>>> find that suggestion now).? This would not be an issue if it
>     were all
>     >>>>> local without version control.? With RStudio managing my
>     interface with
>     >>>>> GitHub, it now seems quite tricky.
>     >>>> I'm 99.999% confident that your life will be much much easier
>     if you
>     >>>> keep one R package per repository.? If you don't, you'll
>     probably be
>     >>>> very lonely when it comes to tools etc. There are built-in 'git'
>     >>>> commands, but also git utility tools, for extracting a subset of
>     >>>> folders/files from git repository into new git repositories.?
>     You'll
>     >>>> still preserve the commit history.? I would deal with this in the
>     >>>> terminal, using the 'git' client and possible some extraction
>     tool.
>     >>>>
>     >>>> Also, while you spend time on this, have a look at the commit
>     >>>> authorship that I mentioned previously.? It's nice to have
>     that in
>     >>>> place later.
>     >>>>
>     >>>> After you got the above in place, then .travis.yml and
>     appveyor.yml is
>     >>>> pretty straightforward (might even be a copy'n'paste).
>     >>>>
>     >>>> Finally, I saw you put your credentials in the URL when you
>     cloned.? I
>     >>>> don't think that's safe, your GitHub credentials will be
>     stored in the
>     >>>> ./.git/config file.? Instead, just clone with:
>     >>>>
>     >>>> git clone https://github.com/sbgraves237/Ecdat.git
>     >>>>
>     >>>> You can then configure git to cache your HTTPS credentials for a
>     >>>> certain time, e.g. 120 minutes, so you don't have to enter
>     them each
>     >>>> time you pull/push.? See
>     https://git-scm.com/docs/git-credential-cache
>     >>>> for details.? That's what I tell new-comers to
>     Git(Hub|Lab|...) to
>     >>>> use.? Personally, I add my public SSH key to GitHub and then
>     clone
>     >>>> with the ssh protocol:
>     >>>>
>     >>>> git clone git at github.com:sbgraves237/Ecdat.git
>     >>>>
>     >>>> That way my I never have to worry entering my credentials.
>     >>>>
>     >>>> /Henrik
>     >>>>
>     >>>>>? ? ? ? ? Suggestions?
>     >>>>>? ? ? ? ? Thanks again to all who have offered suggestions so
>     far.? This
>     >>>>> migration from R-Forge to GitHub seems complete except for
>     the automatic
>     >>>>> tests provided via "Travis CI".
>     >>>>>
>     >>>>>
>     >>>>>? ? ? ? ? Spencer
>     >>>>>
>     >>>>>
>     >>>>> On 2019-06-28 22:25, Ott Toomet wrote:
>     >>>>>> 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
>     <mailto:spencer.graves at prodsyse.com>
>     <mailto:spencer.graves at prodsyse.com
>     <mailto: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 <mailto:R-devel at r-project.org>
>     <mailto:R-devel at r-project.org <mailto:R-devel at r-project.org>>
>     mailing list
>     >>>>>> https://stat.ethz.ch/mailman/listinfo/r-devel
>     >>>>>>
>     >>>>>? ? ? ? ? ?[[alternative HTML version deleted]]
>     >>>>>
>     >>>>> ______________________________________________
>     >>>>> R-devel at r-project.org <mailto:R-devel at r-project.org> mailing
>     list
>     >>>>> https://stat.ethz.ch/mailman/listinfo/r-devel
>     >>> ______________________________________________
>     >>> R-devel at r-project.org <mailto:R-devel at r-project.org> mailing list
>     >>> https://stat.ethz.ch/mailman/listinfo/r-devel
>     >>
>     >>
>     >> --
>     >> Joshua Ulrich? | about.me/joshuaulrich
>     <http://about.me/joshuaulrich>
>     >> FOSS Trading? | www.fosstrading.com <http://www.fosstrading.com>
>     >
>     >
>
>     ______________________________________________
>     R-devel at r-project.org <mailto:R-devel at r-project.org> mailing list
>     https://stat.ethz.ch/mailman/listinfo/r-devel
>


	[[alternative HTML version deleted]]



[Rd] R-Forge > GitHub?
Spencer Graves