cms-sw / cms-git-tools

CMS Git Helpers
34 stars 26 forks source link

"You don't seem to have a personal repository," when I do have a personal repository #54

Closed TaiSakuma closed 9 years ago

TaiSakuma commented 10 years ago

"git cms-init" gives me the following message.

You don't seem to have a personal repository, or your GitHub username (TaiSakuma) is not correct.
You can work locally, but you will not be able to push your changes to GitHub for inclusion 
in the official CMSSW distribution.

You can correct your GitHub user name via:

    git config --global user.github <your github username>

To create a personal repository:
  - go to https://github.com/ and log in
  - go to https://github.com/cms-sw/cmssw and click on the Fork button
  - select the option to fork the repository under your username (TaiSakuma)

However, I do have a personal repository and my GitHub username (TaiSakuma) is correct.

The problem seems to be "curl" used at https://github.com/cms-sw/cms-git-tools/blob/master/git-cms-init#L273 In a cmsenv, "curl" is installed at $VO_CMS_SW_DIR/osx108_amd64_gcc481/cms/cmssw/CMSSW_7_0_0_pre8/external/osx108_amd64_gcc481/bin/curl

If I manually execute this command without "-q" (quiet) option in a cmsenv as

$ curl -s "https://api.github.com/users/TaiSakuma/repos" | tee /dev/null | grep '"name": *"cmssw"'

nothing will be shown.

However, if I use, for example, "curl" from MacPorts:

$ /opt/local/bin/curl -s "https://api.github.com/users/TaiSakuma/repos" | tee /dev/null | grep '"name": *"cmssw"'
    "name": "cmssw",

Then it prints '"name": "cmssw",'.

TaiSakuma commented 10 years ago

I still receive the same message about the github username on CMSSW_7_1_0_pre2 on osx108_amd64_gcc481.

I am wondering if this can be fixed someday.

juska commented 9 years ago

I am wondering the exact same thing ten months later..

fwyzard commented 9 years ago

First of all, let me suggest you some light readings, that might help you in your future dealings with software developers:

Then, instead of simply stating something that has very little interest for anybody but yourself, like

I am wondering the exact same thing ten months later..

you could provide some useful feedback on how to reproduce the issue you are facing. At the very least:

git config --global user.github

when you run it on the same machine(s) ?

Optionally, you could even spend some time to try and understand yourself why the checks inside git-cms-init are failing for your specific case, while they are apparently working for almost every other CMS developer.

With wishes for a happy new year, .Andrea

juska commented 9 years ago

First of all, let me express my deepest apologies for everyone offended by my tactlessness; my main purpose was to bump up this post as I am experiencing pretty much identical problem as Tai before. By analyzing the history of this bug report, I did not consider it worthwile to put much effort on extensive testing and detailed reporting as Tai had already tried that method a year ago to no avail, apparently.

But now that I managed to draw attention, let's try and tackle this problem!

My username is 'juska' and I am currently working on lxplus0077.cern.ch using release CMSSW_7_3_0_pre1.

'git cms-init' gives:


[juska@lxplus0077 src]$ git cms-init No release tags specified, using current branch from-CMSSW_7_3_0_pre1. You don't seem to have a personal repository, or your GitHub username (juska) is not correct. You can work locally, but you will not be able to push your changes to GitHub for inclusion in the official CMSSW distribution.

You can correct your GitHub user name via:

git config --global user.github <your github username>

To create a personal repository:

You are on branch from-CMSSW_7_3_0_pre1 [juska@lxplus0077 src]$


.. and the second test:


[juska@lxplus0077 src]$ git config --global user.github juska [juska@lxplus0077 src]$


The fact that not every CMS developer is whining about this problem has no causal connection with the fact whether every CMS developer is facing the same problem but disregarding it.

Cheers,

Juska

fwyzard commented 9 years ago

Did you actually try to follow the instructions from git-cms-init itself ?

I.e.

To create a personal repository:

As far as I can see, you do not have a personal repository. At https://github.com/juska?tab=repositories it says

juska doesn’t have any public repositories yet.

Ciao, .Andrea On 30 Dec 2014 15:36, "juska" notifications@github.com wrote:

First of all, let me express my deepest apologies for everyone offended by my tactlessness; my main purpose was to bump up this post as I am experiencing pretty much identical problem as Tai before. By analyzing the history of this bug report, I did not consider it worthwile to put much effort on extensive testing and detailed reporting as Tai had already tried that method a year ago to no avail, apparently.

But now that I managed to draw attention, let's try and tackle this problem!

My username is 'juska' and I am currently working on lxplus0077.cern.ch using release CMSSW_7_3_0_pre1.

'git cms-init' gives:

[juska@lxplus0077 src]$ git cms-init No release tags specified, using current branch from-CMSSW_7_3_0_pre1. You don't seem to have a personal repository, or your GitHub username (juska) is not correct. You can work locally, but you will not be able to push your changes to GitHub for inclusion in the official CMSSW distribution.

You can correct your GitHub user name via:

git config --global user.github

To create a personal repository:

You are on branch from-CMSSW_7_3_0_pre1

[juska@lxplus0077 src]$

.. and the second test:

[juska@lxplus0077 src]$ git config --global user.github juska

[juska@lxplus0077 src]$

The fact that not every CMS developer is whining about this problem has no causal connection with the fact whether every CMS developer is facing the same problem but disregarding it.

Cheers,

Juska

— Reply to this email directly or view it on GitHub https://github.com/cms-sw/cms-git-tools/issues/54#issuecomment-68360839.

juska commented 9 years ago

Oh, I must have omitted that part. Worked like a charm yeehaa! I must admit that immersion in error messages is not my strongest virtue.

Now I learned also that github registration and having a personal repository are not equivalent concepts..

Thank's for the quick help on such a weird time of the year Andrea, and best wishes for the new year!

Juska

TaiSakuma commented 9 years ago

I don't receive the error with CMSSW_7_3_0 in osx108_amd64_gcc481 on OSX 10.9.5, which is not an officially supported combination.

I think that this issue has been fixed.