Re: [Rd] R-Forge > GitHub?

On 14 July 2019 at 13:08, Spencer Graves wrote: | for that.  I lost the history in doing so, but I can live without that | history. Well many of us imported svn repos into git repos. And my favourite example is still ESS as it has history back to 1997 (!!) thanks to cvs2svn pre-filling its svn

Re: [Rd] R-Forge > GitHub?

  Thanks to Ott and others, I now have separate GitHub repositories, one for each of the packages combined in the Ecdat R-Forge project.  In case it might help others in the future, I will summarize here key things I did to make this transition:         1.  I first copied the "Ecfun"

Re: [Rd] R-Forge > GitHub?

  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 g...@github.com:joshuaulrich/tmp-ecfun.git Ecdat # Cloning into 'Ecdat

Re: [Rd] R-Forge > GitHub?

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-k

Re: [Rd] R-Forge > GitHub?

On 2019-06-30 06:58, Joshua Ulrich wrote: 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 woul

Re: [Rd] R-Forge > GitHub?

On Sat, Jun 29, 2019 at 9:46 PM Joshua Ulrich wrote: > > On Sat, Jun 29, 2019 at 6:06 PM Spencer Graves > wrote: > > > > Hi, Henrik et al.: > > > > > >What's your favorite documentation on how to make two GitHub > > projects from one containing two packages? > > > > > >Currently,

Re: [Rd] R-Forge > GitHub?

On Sat, Jun 29, 2019 at 6:06 PM Spencer Graves wrote: > > Hi, Henrik et al.: > > >What's your favorite documentation on how to make two GitHub > projects from one containing two packages? > > >Currently, "github.com/sbgraves237/Ecdat" consists primarily of a > directory "pkg" with

Re: [Rd] R-Forge > GitHub?

Hi, Henrik et al.:   What's your favorite documentation on how to make two GitHub projects from one containing two packages?   Currently, "github.com/sbgraves237/Ecdat" consists primarily of a directory "pkg" with subdirectories "Ecdat" and "Ecfun" containing the two packages.  I n

Re: [Rd] R-Forge > GitHub?

On Sat, Jun 29, 2019 at 9:43 AM Spencer Graves 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 Wickha

Re: [Rd] R-Forge > GitHub?

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

Re: [Rd] R-Forge > GitHub?

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 tho

Re: [Rd] R-Forge > GitHub?

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:mypassw...@github.com/sbgraves237/Ecdat.git   That worked in the sense that I got a local copy.  However, after I rolled the

Re: [Rd] R-Forge > GitHub?

Whereas it is true that one has to contact GitHub to detach a GitHub repository, it really is no problem (or at least was no problem in 2016). I wanted to do so when I took over the maintainer role of LaplacesDemon which only remained on GitHub as a fork on some other person's private account. So I

Re: [Rd] R-Forge > GitHub?

Re your point 3: Because you have managed to create a GitHub version of your repository that is not a fork of https://github.com/rforge/ecdat, but its own independent repository, contacting GitHub support might not be the right way forward. Note that https://github.com/rforge is simply a read-only

Re: [Rd] R-Forge > GitHub?

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 t

Re: [Rd] R-Forge > GitHub?

Spencer, on your point 3. below, we took a different path in migrating several packages. After we migrated to github as the new master copy, we made new commits to the now orphaned R-Forge copies to include a new .onAttach function as so: .onAttach <- function(libname, pkgname) { repo <- "h

Re: [Rd] R-Forge > GitHub?

On Fri, Jun 28, 2019 at 6:01 AM Spencer Graves wrote: [...] > 1. Clone a copy of "https://github.com/sbgraves237/Ecdat"; > to my local computer and confirm that it works. > I suggest you put each package in its own repository, because our R tooling (e.g. Travis CI, etc.) works best

Re: [Rd] R-Forge > GitHub?

Henrik's advice is all good. I would say his idea of the final commit of a README pointer is better than deleting things at R-forge; there is likely old information out there somewhere pointing to R-forge as a location for Ecdat development, and any bug reports or discussion on R-forge will no

Re: [Rd] R-Forge > GitHub?

Hi, Henrik Singmann et al.:   Thanks for the suggestions.  I tried again to pull "https://github.com/sbgraves237/Ecdat"; from R-Forge, with the same "Error 500" as before.  Then I tried pulling from "https://github.com/rforge/ecdat";, which seemed to work ... AND the copy I pulled was at

Re: [Rd] R-Forge > GitHub?

� Thanks.� I'm still having problems: ��� ��� 1.� I went to "github.com" and logged in with my standard GitHub account ��� ��� 2.� Then I clicked "+" in the upper right, just left of my GitHub ID icon, and selected "Import a repository", as Lionel suggested. ��� ��� 3.�

Re: [Rd] R-Forge > GitHub?

  Thanks to Duncan, Lionel and Henrik for their quick replies. I have further questions:        1.  Will GitHub automatically transfer the commits I made to R-Forge in the past couple of days?  R-Forge is now at Rev. 420, and GitHub is still at 418.  Will 419 and 420 be automatically

Re: [Rd] R-Forge > GitHub?

On 26/06/2019 1:38 p.m., Spencer Graves wrote:   Thanks.  I'm still having problems:         1.  I went to "github.com" and logged in with my standard GitHub account         2.  Then I clicked "+" in the upper right, just left of my GitHub ID icon, and selected "Import a rep

Re: [Rd] R-Forge > GitHub?

One thing that needs manual work is making each SVN username mP to a Git (username, email address). This often involved asking contributors what their preferred endless Git address is. The email address is what for instance GitHub uses to associate a commit authorship with a user account. You can

Re: [Rd] R-Forge > GitHub?

I think all 3 issues are solved by: 1. Use the "+" button on github.com and select "Import a repository". 2. Pass the URL of your SVN repo. Lionel > On 26 Jun 2019, at 18:58, Spencer Graves wrote: > > Thanks to Duncan, Lionel and Henrik for their quick replies. I ha

Re: [Rd] R-Forge > GitHub?

> On 26 Jun 2019, at 17:25, Duncan Murdoch wrote: > > R-Forge is mirrored on Github; see https://github.com/rforge/ecdat, for > example. That shows 418 commits in its history; presumably that's the full > R-forge history. I think that's newer than Michael Friendly's gist. > > So I suspect

Re: [Rd] R-Forge > GitHub?

On 26/06/2019 10:34 a.m., Spencer Graves wrote: Hello, All:   What's the status and future plans for R-Forge?   I ask primarily because a problem I reported May 15 and 17 via two different channels has yet to be fixed, and it prevents my development versions of the Ecdat and Ecfun

[Rd] R-Forge > GitHub?

Hello, All:   What's the status and future plans for R-Forge?   I ask primarily because a problem I reported May 15 and 17 via two different channels has yet to be fixed, and it prevents my development versions of the Ecdat and Ecfun packages from building -- because the Windows ve