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 version cannot find "Matrix";? see below.
Secondarily, the version of R that R-Forge tried to use earlier today
was 3.5.3 -- NOT the current version.


  ????? Assuming you recommend migrating to GitHub, do you have a
preferred procedure?? I found
"https://gist.github.com/friendly/7269490".? This says it was "Last
active 2 years ago" but seems to be the most current advice I can find
on this right now.? That looks complicated, but I assume it preserves
the edit history on R-Forge. ???

On 26 Jun 2019, at 17:25, Duncan Murdoch <murdoch.duncan at gmail.com> 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 (but haven't tried to do this) that migration now is as simple as doing a Github fork to your own Github account, and then basically forgetting about the R-forge stuff, or deleting it (and I don't know how to do that).

On 26 Jun 2019, at 17:25, Duncan Murdoch <murdoch.duncan at gmail.com> 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 (but haven't tried to do this) that migration now is as simple as doing a Github fork to your own Github account, and then basically forgetting about the R-forge stuff, or deleting it (and I don't know how to do that).

I think it's better to avoid the Fork button in this case, because forks are
treated specially in the Github UI. In this case you'll want your repo to
appear as a main repo, and not a fork. AFAIK the only way to unfork a repo
is to ask the Github staff to do it.

So instead of forking, use the "+" button on github.com and select
"Import a repository". This supports both git and svn repos.

Best,
Lionel

On 26 Jun 2019, at 18:58, Spencer Graves <spencer.graves at prodsyse.com> wrote:

      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 mirrored onto "https://github.com/rforge/ecdat" sometime in the next 24 hours or so?  Is there something easy I can do to force that update?


            2.  Is there a way to make this GitHub version the master?  It currently says it is a 'Read-only mirror of "ecdat" from r-forge SVN.'  I can probably change "r-forge.r-project.org/projects/ecdat" so I'm the only one authorized to make changes there and then stop committing changes there.  However, before I do that, I'd want to make sure I can commit directly to the GitHub version, etc.


            3.  How can I make myself the owner and a contributor for the GitHub version?  I'm a "Project Admin" on the R-Forge version, but currently no one can make any changes to the GitHub version except via R-Forge.  There must be a recommended migration process.


      I could create a separate version of this package on GitHub, but all the history would be lost.


      Thanks again,
      Spencer Graves


On 2019-06-26 10:35, Lionel Henry wrote:

On 26 Jun 2019, at 17:25, Duncan Murdoch <murdoch.duncan at gmail.com> 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 (but haven't tried to do this) that migration now is as simple as doing a Github fork to your own Github account, and then basically forgetting about the R-forge stuff, or deleting it (and I don't know how to do that).

I think it's better to avoid the Fork button in this case, because forks are
treated specially in the Github UI. In this case you'll want your repo to
appear as a main repo, and not a fork. AFAIK the only way to unfork a repo
is to ask the Github staff to do it.

So instead of forking, use the "+" button on github.com and select
"Import a repository". This supports both git and svn repos.

Best,
Lionel

I think all 3 issues are solved by:

1. Use the "+" button on github.com <http://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 <spencer.graves at prodsyse.com 
<mailto:spencer.graves at prodsyse.com>> wrote:

????? 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 
mirrored onto "https://github.com/rforge/ecdat" sometime in the next 
24 hours or so?? Is there something easy I can do to force that update?


??? ?? ???? 2.? Is there a way to make this GitHub version the 
master?? It currently says it is a 'Read-only mirror of "ecdat" from 
r-forge SVN.'? I can probably change 
"r-forge.r-project.org/projects/ecdat 
<http://r-forge.r-project.org/projects/ecdat>" so I'm the only one 
authorized to make changes there and then stop committing changes 
there.? However, before I do that, I'd want to make sure I can commit 
directly to the GitHub version, etc.


??? ?? ???? 3.? How can I make myself the owner and a contributor for 
the GitHub version?? I'm a "Project Admin" on the R-Forge version, 
but currently no one can make any changes to the GitHub version 
except via R-Forge.? There must be a recommended migration process.


????? I could create a separate version of this package on GitHub, 
but all the history would be lost.


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


On 2019-06-26 10:35, Lionel Henry wrote:

On 26 Jun 2019, at 17:25, Duncan Murdoch <murdoch.duncan at gmail.com 
<mailto:murdoch.duncan at gmail.com>> 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 (but haven't tried to do this) that migration now is 
as simple as doing a Github fork to your own Github account, and 
then basically forgetting about the R-forge stuff, or deleting it 
(and I don't know how to do that).

I think it's better to avoid the Fork button in this case, because 
forks are
treated specially in the Github UI. In this case you'll want your 
repo to
appear as a main repo, and not a fork. AFAIK the only way to unfork 
a repo
is to ask the Github staff to do it.

So instead of forking, use the "+" button on github.com 
<http://github.com> and select
"Import a repository". This supports both git and svn repos.

Best,
Lionel

 ????? 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.? " Your old repository?s clone URL" = 
"https://r-forge.r-project.org/projects/ecdat/" with "Name" = "Ecdat".


 ??? ?? ?? ??????? ** >> This failed, first giving me a 500 failure 
code, then reporting " Repository creation failed."? When I tried it 
again, I got, "The repository Ecdat already exists on this account."


 ????? What do you suggest I try next?

 ????? Thanks,
 ????? Spencer


On 2019-06-26 12:02, Lionel Henry wrote:

I think all 3 issues are solved by:

1. Use the "+" button on github.com <http://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 <spencer.graves at prodsyse.com 
<mailto:spencer.graves at prodsyse.com>> wrote:

????? 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 
mirrored onto "https://github.com/rforge/ecdat" sometime in the next 
24 hours or so?? Is there something easy I can do to force that update?


??? ?? ???? 2.? Is there a way to make this GitHub version the 
master?? It currently says it is a 'Read-only mirror of "ecdat" from 
r-forge SVN.'? I can probably change 
"r-forge.r-project.org/projects/ecdat 
<http://r-forge.r-project.org/projects/ecdat>" so I'm the only one 
authorized to make changes there and then stop committing changes 
there.? However, before I do that, I'd want to make sure I can commit 
directly to the GitHub version, etc.


??? ?? ???? 3.? How can I make myself the owner and a contributor for 
the GitHub version?? I'm a "Project Admin" on the R-Forge version, 
but currently no one can make any changes to the GitHub version 
except via R-Forge.? There must be a recommended migration process.


????? I could create a separate version of this package on GitHub, 
but all the history would be lost.


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


On 2019-06-26 10:35, Lionel Henry wrote:

On 26 Jun 2019, at 17:25, Duncan Murdoch <murdoch.duncan at gmail.com 
<mailto:murdoch.duncan at gmail.com>> 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 (but haven't tried to do this) that migration now is 
as simple as doing a Github fork to your own Github account, and 
then basically forgetting about the R-forge stuff, or deleting it 
(and I don't know how to do that).

I think it's better to avoid the Fork button in this case, because 
forks are
treated specially in the Github UI. In this case you'll want your 
repo to
appear as a main repo, and not a fork. AFAIK the only way to unfork 
a repo
is to ask the Github staff to do it.

So instead of forking, use the "+" button on github.com 
<http://github.com> and select
"Import a repository". This supports both git and svn repos.

Best,
Lionel

:

On 26 Jun 2019, at 17:25, Duncan Murdoch <murdoch.duncan at gmail.com>

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 (but haven't tried to do this) that migration now is as

simple as doing a Github fork to your own Github account, and then
basically forgetting about the R-forge stuff, or deleting it (and I don't
know how to do that).

I think it's better to avoid the Fork button in this case, because forks
are
treated specially in the Github UI. In this case you'll want your repo to
appear as a main repo, and not a fork. AFAIK the only way to unfork a repo
is to ask the Github staff to do it.

So instead of forking, use the "+" button on github.com and select
"Import a repository". This supports both git and svn repos.

Best,
Lionel

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 forked and then contacted 
GitHub?support?and simply asked them to remove the "forked form" 
reference on my new repository.?They then quickly detached my 
repository.?As you can see, the "forked from" is gone: 
https://github.com/LaplacesDemonR/LaplacesDemon

In their response to my request they used the phrasing "Fork is 
detached." which suggests that this is their preferred term for this 
step.

Best,
Henrik



Am Mi., 26. Juni 2019 um 16:38?Uhr schrieb Lionel Henry 
<lionel at rstudio.com <mailto:lionel at rstudio.com>>:

    > On 26 Jun 2019, at 17:25, Duncan Murdoch

    <murdoch.duncan at gmail.com <mailto:murdoch.duncan at gmail.com>> 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 (but haven't tried to do this) that migration now

    is as simple as doing a Github fork to your own Github account,
    and then basically forgetting about the R-forge stuff, or deleting
    it (and I don't know how to do that).

    I think it's better to avoid the Fork button in this case, because
    forks are
    treated specially in the Github UI. In this case you'll want your
    repo to
    appear as a main repo, and not a fork. AFAIK the only way to
    unfork a repo
    is to ask the Github staff to do it.

    So instead of forking, use the "+" button on github.com
    <http://github.com> and select
    "Import a repository". This supports both git and svn repos.

    Best,
    Lionel

Hi, Henrik Singmann et al.:


      Thanks for the suggestions.  I tried again to pull
"https://github.com/sbgraves237/Ecdat"
<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" <https://github.com/rforge/ecdat>,
which seemed to work ... AND the copy I pulled was at the latest revisions
I had posted to R-Forge (520), so that makes it easier going forward.


      What do you suggest I do next?  I'm thinking of the following:


            1.  Clone a copy of "https://github.com/sbgraves237/Ecdat"
<https://github.com/sbgraves237/Ecdat> to my local computer and confirm
that it works.


            2.  Modify "https://r-forge.r-project.org/projects/ecdat/"
<https://r-forge.r-project.org/projects/ecdat/> to make me the only
remaining project member, if I can.


            3.  Contact GitHub support and ask them if they can delete
"https://github.com/rforge/ecdat" <https://github.com/rforge/ecdat>,
because it is an orphan with 0 contributors, and anyone who might want it
should be referred to "https://github.com/sbgraves237/Ecdat"
<https://github.com/sbgraves237/Ecdat>.


             4.  Email all the previous project members on
"https://r-forge.r-project.org/projects/ecdat/"
<https://r-forge.r-project.org/projects/ecdat/> to tell them what I've
done, in case they want to do anything more with this in the future.


      I believe I know how to do 1, 2, and 4, and I can probably figure
out 3.  However, before I start on this, I felt a need to thank everyone
who contributed to this thread and invite comments, especially if someone
thinks I might be better off doing something different.


      Spencer Graves


On 2019-06-26 16:34, Henrik Singmann wrote:

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 forked and then contacted GitHub support and simply asked them to
remove the "forked form" reference on my new repository. They then quickly
detached my repository. As you can see, the "forked from" is gone:
https://github.com/LaplacesDemonR/LaplacesDemon

In their response to my request they used the phrasing "Fork is detached."
which suggests that this is their preferred term for this step.

Best,
Henrik



Am Mi., 26. Juni 2019 um 16:38 Uhr schrieb Lionel Henry <
lionel at rstudio.com>:

On 26 Jun 2019, at 17:25, Duncan Murdoch <murdoch.duncan at gmail.com>

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 (but haven't tried to do this) that migration now is as

simple as doing a Github fork to your own Github account, and then
basically forgetting about the R-forge stuff, or deleting it (and I don't
know how to do that).

I think it's better to avoid the Fork button in this case, because forks
are
treated specially in the Github UI. In this case you'll want your repo to
appear as a main repo, and not a fork. AFAIK the only way to unfork a repo
is to ask the Github staff to do it.

So instead of forking, use the "+" button on github.com and select
"Import a repository". This supports both git and svn repos.

Best,
Lionel

--
Dr. Henrik Singmann
Assistant Professor, Department of Psychology
University of Warwick, UK
http://singmann.org

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 mirror of the complete R-Forge repository (and at least to 
me it is unclear of whether GitHub itself or some independent party is 
responsible for it, but I would assume it is not GitHub). So the easiest 
way to change something in https://github.com/rforge/ecdat?would be to 
make the corresponding change in your R-forge repository and wait until 
it propagates to GitHub.

So either delete the R-forge repository or make a final commit replacing 
its content with a README pointing towards the new GitHub repo at 
https://github.com/sbgraves237/Ecdat. Together with emailing all  
previous project members this should ensure that interested party will 
know about the new place where your package is being developed/hosted.

You might also want to add a new README to the new GitHub repository 
which replaces the current R-forge one and provides installation 
instructions.

Best,
Henrik



Am Fr., 28. Juni 2019 um 06:01?Uhr schrieb Spencer Graves 
<spencer.graves at prodsyse.com <mailto:spencer.graves at prodsyse.com>>:

    Hi, Henrik Singmann et al.:


     ????? Thanks for the suggestions.? I tried again to pull
    "https://github.com/sbgraves237/Ecdat"
    <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" <https://github.com/rforge/ecdat>,
    which seemed to work ... AND the copy I pulled was at the latest
    revisions I had posted to R-Forge (520), so that makes it easier
    going forward.


     ????? What do you suggest I do next?? I'm thinking of the following:


     ??? ??????? 1.? Clone a copy of
    "https://github.com/sbgraves237/Ecdat"
    <https://github.com/sbgraves237/Ecdat> to my local computer and
    confirm that it works.


     ??? ??????? 2.? Modify
    "https://r-forge.r-project.org/projects/ecdat/"
    <https://r-forge.r-project.org/projects/ecdat/> to make me the only
    remaining project member, if I can.


     ??? ??????? 3.? Contact GitHub support and ask them if they can
    delete "https://github.com/rforge/ecdat"
    <https://github.com/rforge/ecdat>, because it is an orphan with 0
    contributors, and anyone who might want it should be referred to
    "https://github.com/sbgraves237/Ecdat"
    <https://github.com/sbgraves237/Ecdat>.


     ???? ??????? 4.? Email all the previous project members on
    "https://r-forge.r-project.org/projects/ecdat/"
    <https://r-forge.r-project.org/projects/ecdat/> to tell them what
    I've done, in case they want to do anything more with this in the
    future.


     ????? I believe I know how to do 1, 2, and 4, and I can probably
    figure out 3.? However, before I start on this, I felt a need to
    thank everyone who contributed to this thread and invite comments,
    especially if someone thinks I might be better off doing something
    different.


     ????? Spencer Graves


    On 2019-06-26 16:34, Henrik Singmann wrote:

    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 forked and
    then contacted GitHub?support?and simply asked them to remove the
    "forked form" reference on my new repository.?They then quickly
    detached my repository.?As you can see, the "forked from" is gone:
    https://github.com/LaplacesDemonR/LaplacesDemon

    In their response to my request they used the phrasing "Fork is
    detached." which suggests that this is their preferred term for
    this step.

    Best,
    Henrik



    Am Mi., 26. Juni 2019 um 16:38?Uhr schrieb Lionel Henry
    <lionel at rstudio.com <mailto:lionel at rstudio.com>>:

        > On 26 Jun 2019, at 17:25, Duncan Murdoch

        <murdoch.duncan at gmail.com <mailto:murdoch.duncan at gmail.com>>
        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 (but haven't tried to do this) that migration

        now is as simple as doing a Github fork to your own Github
        account, and then basically forgetting about the R-forge
        stuff, or deleting it (and I don't know how to do that).

        I think it's better to avoid the Fork button in this case,
        because forks are
        treated specially in the Github UI. In this case you'll want
        your repo to
        appear as a main repo, and not a fork. AFAIK the only way to
        unfork a repo
        is to ask the Github staff to do it.

        So instead of forking, use the "+" button on github.com
        <http://github.com> and select
        "Import a repository". This supports both git and svn repos.

        Best,
        Lionel

-- 
Dr. Henrik Singmann
Assistant Professor, Department of Psychology
University of Warwick, UK
http://singmann.org

             1.  Clone a copy of "https://github.com/sbgraves237/Ecdat"
to my local computer and confirm that it works.

             3.  Contact GitHub support and ask them if they can delete
"https://github.com/rforge/ecdat", because it is an orphan with 0
contributors, and anyone who might want it should be referred to
"https://github.com/sbgraves237/Ecdat".

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 the latest revisions I had posted to R-Forge (520), so
that makes it easier going forward.


  ????? What do you suggest I do next?? I'm thinking of the following:


  ??? ??????? 1.? Clone a copy of "https://github.com/sbgraves237/Ecdat"
to my local computer and confirm that it works.


  ??? ??????? 2.? Modify "https://r-forge.r-project.org/projects/ecdat/"
to make me the only remaining project member, if I can.


  ??? ??????? 3.? Contact GitHub support and ask them if they can delete
"https://github.com/rforge/ecdat", because it is an orphan with 0
contributors, and anyone who might want it should be referred to
"https://github.com/sbgraves237/Ecdat".


  ???? ??????? 4.? Email all the previous project members on
"https://r-forge.r-project.org/projects/ecdat/" to tell them what I've
done, in case they want to do anything more with this in the future.


  ????? I believe I know how to do 1, 2, and 4, and I can probably figure
out 3.? However, before I start on this, I felt a need to thank everyone
who contributed to this thread and invite comments, especially if
someone thinks I might be better off doing something different.


  ????? Spencer Graves


On 2019-06-26 16:34, Henrik Singmann wrote:

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 forked and then contacted
GitHub?support?and simply asked them to remove the "forked form"
reference on my new repository.?They then quickly detached my
repository.?As you can see, the "forked from" is gone:
https://github.com/LaplacesDemonR/LaplacesDemon

In their response to my request they used the phrasing "Fork is
detached." which suggests that this is their preferred term for this
step.

Best,
Henrik



Am Mi., 26. Juni 2019 um 16:38?Uhr schrieb Lionel Henry
<lionel at rstudio.com <mailto:lionel at rstudio.com>>:

     > On 26 Jun 2019, at 17:25, Duncan Murdoch

     <murdoch.duncan at gmail.com <mailto:murdoch.duncan at gmail.com>> 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 (but haven't tried to do this) that migration now

     is as simple as doing a Github fork to your own Github account,
     and then basically forgetting about the R-forge stuff, or deleting
     it (and I don't know how to do that).

     I think it's better to avoid the Fork button in this case, because
     forks are
     treated specially in the Github UI. In this case you'll want your
     repo to
     appear as a main repo, and not a fork. AFAIK the only way to
     unfork a repo
     is to ask the Github staff to do it.

     So instead of forking, use the "+" button on github.com
     <http://github.com> and select
     "Import a repository". This supports both git and svn repos.

     Best,
     Lionel

	[[alternative HTML version deleted]]

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.

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

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

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

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.

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

        [[alternative HTML version deleted]]

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

         [[alternative HTML version deleted]]

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 need to know how to do the following:


             1.  Extract "github.com/sbgraves237/Ecdat/pkg/Ecfun" to
create  "github.com/sbgraves237/Ecfun".


              2.  Elevate "github.com/sbgraves237/Ecdat/pkg/Ecdat" to
"github.com/sbgraves237/Ecdat", discarding the other files in the
original "github.com/sbgraves237/Ecdat/".


       This sounds like it could be accomplished relatively easily by
someone with sufficient understanding of "git" and GitHub.  I could use
suggestions on how to do this -- or at least on how to find
documentation on how to do this.

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

         [[alternative HTML version deleted]]

On Sat, Jun 29, 2019 at 6:06 PM Spencer Graves
<spencer.graves at prodsyse.com> 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 subdirectories "Ecdat" and "Ecfun" containing the
two packages.  I need to know how to do the following:


             1.  Extract "github.com/sbgraves237/Ecdat/pkg/Ecfun" to
create  "github.com/sbgraves237/Ecfun".


              2.  Elevate "github.com/sbgraves237/Ecdat/pkg/Ecdat" to
"github.com/sbgraves237/Ecdat", discarding the other files in the
original "github.com/sbgraves237/Ecdat/".


       This sounds like it could be accomplished relatively easily by
someone with sufficient understanding of "git" and GitHub.  I could use
suggestions on how to do this -- or at least on how to find
documentation on how to do this.

This is straightforward if the two packages have always been in the
same directory structure.  But it doesn't look like that's the case
for your repository, since Ecfun was added around r125.  So Ecdat's
history is split and would need to be grafted together.  I've done
this for other packages.  So it's possible, but it took me some trial
and error.

I'm giving that a go right now.  I'll report back tomorrow morning, at
the latest.

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

         [[alternative HTML version deleted]]

--
Joshua Ulrich  |  about.me/joshuaulrich
FOSS Trading  |  www.fosstrading.com

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

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

          [[alternative HTML version deleted]]

--
Joshua Ulrich  |  about.me/joshuaulrich
FOSS Trading  |  www.fosstrading.com

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

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

list

          [[alternative HTML version deleted]]

--
Joshua Ulrich  |  about.me/joshuaulrich
FOSS Trading  |  www.fosstrading.com