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

mepo issue with moving fixtures #106

Closed
mathomp4 opened this issue Oct 26, 2020 · 2 comments
Closed

mepo issue with moving fixtures #106

mathomp4 opened this issue Oct 26, 2020 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@mathomp4
Copy link
Member

This was discovered by @rtodling. To wit:

  1. Clone repo to /path/to/GEOSgcm
  2. Move repo to /path/to/GEOSgcm-OLD
  3. Clone new repo to /path/to/GEOSgcm

The issue is that mepo init uses absolute paths during its setup. So if you move things like this, even the GEOSgcm-OLD clone will point to the new clone because one exists at that part of the tree.

@mathomp4 mathomp4 added the bug Something isn't working label Oct 26, 2020
@mathomp4 mathomp4 self-assigned this Oct 26, 2020
@rtodling
Copy link

Just to add that this "renaming" of directories has been common practice among most, if not all, users of the DAS. I will have to ask that we come up w/ a fix for this before releasing the DAS to anyone beyond the small group of individuals presently testing the Git vs CVS migration.

@mathomp4
Copy link
Member Author

I think #107 has a fix for this. I'm doing some more testing to be sure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants