Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Repo Not found: Getting EOL Private Config #108

Open
HatemMS2012 opened this issue Feb 23, 2015 · 4 comments
Open

Repo Not found: Getting EOL Private Config #108

HatemMS2012 opened this issue Feb 23, 2015 · 4 comments

Comments

@HatemMS2012
Copy link

Hi,

I am trying to clone the EOL private config (as described in the readme file) using the follwoing command:

rake eol:site_specific repo=git@github.com:mbl-cli/eol-private.git

However, I am getting the follwoing error message:

Checking out files from repository...
.. Creating new git clone:
git clone git@github.com:mbl-cli/eol-private.git C:/Users/localadmin/workspace/eolRoot/eol/vendor/eol_org
Cloning into 'C:/Users/localadmin/workspace/eolRoot/eol/vendor/eol_org'...
Enter passphrase for key '/c/Users/localadmin/.ssh/id_rsa':
ERROR: Repository not found.
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
rake aborted!
Command failed with status (128): [git clone git@github.com:mbl-cli/eol-priva...]
C:/Users/localadmin/workspace/eolRoot/eol/lib/tasks/eol_site_specific.rake:40:in `block (2 levels) in <top (required)>'
Tasks: TOP => eol:site_specific => eol:checkout_repository

I'd appreciate any help.
Thanks,

@JRice
Copy link
Member

JRice commented Feb 23, 2015

As the README says, "Currently this requires you have access to the private
mbl-cli GitHub community." ...Which it doesn't explicitly say, but implies,
is private. ...At the moment, it needs to be, as all of the configuration
of our production servers is in that file.

We will be changing the method we use to configure this over the next month
or so, however.

That said, as the README also says, "We plan to at least make this step
unnecessary to get the tests passing." It's been a while since I've tested
that, but I hope it was true a few months ago and I hope it's still the
case!

On Mon, Feb 23, 2015 at 6:30 AM, HatemMS2012 notifications@github.com
wrote:

Hi,

I am trying to clone the EOL private config (as described in the readme
file) using the follwoing command:

rake eol:site_specific repo=git@github.com:mbl-cli/eol-private.git

However, I am getting the follwoing error message:

Checking out files from repository...
.. Creating new git clone:
git clone git@github.com:mbl-cli/eol-private.git C:/Users/localadmin/workspace/eolRoot/eol/vendor/eol_org
Cloning into 'C:/Users/localadmin/workspace/eolRoot/eol/vendor/eol_org'...
Enter passphrase for key '/c/Users/localadmin/.ssh/id_rsa':
ERROR: Repository not found.
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
rake aborted!
Command failed with status (128): [git clone git@github.com:mbl-cli/eol-priva...]
C:/Users/localadmin/workspace/eolRoot/eol/lib/tasks/eol_site_specific.rake:40:in `block (2 levels) in <top (required)>'
Tasks: TOP => eol:site_specific => eol:checkout_repository

I'd appreciate any help.
Thanks,


Reply to this email directly or view it on GitHub
#108.

@aka001
Copy link
Contributor

aka001 commented Mar 13, 2015

Hi @JRice I would like to fix this issue. Can you please help me in getting started?

@JRice
Copy link
Member

JRice commented Mar 13, 2015

Hi @aka001 ...I don't think this is a particularly good issue to begin with. As I mentioned, we have a plan in place to make this simpler, and we cannot implement it until we move to our new servers, which should be happening within a month, so this will be resolved soon on its own.

Sorry!

@aka001
Copy link
Contributor

aka001 commented Mar 13, 2015

@JRice Okay. Got it. No problem. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants