On Fri, Jun 28, 2019 at 6:01 AM Spencer Graves <spencer.graves at prodsyse.com> 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 if you do that. This is quite easy to do nowadays: https://stackoverflow.com/a/17864475/604364> 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". >You don't need do that. It is unlikely that they would remove *someone else's* repository, anyway, unless the repository has some copyright or license problems. Which it does not, since your packages are GPL. GitHub as a company does not manage https://github.com/rforge. This read only mirror was set up by a fellow GitHub user, and it is best if it is kept as a read-only mirror. 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. Gabor [...] [[alternative HTML version deleted]]
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]]