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

older git checkout error #1355

Closed
doutriaux1 opened this Issue May 28, 2015 · 6 comments

Comments

Projects
None yet
3 participants
@doutriaux1
Member

doutriaux1 commented May 28, 2015

remote: Total 8042 (delta 5120), reused 5720 (delta 3157), pack-reused 0
Receiving objects: 100% (8042/8042), 79.33 MiB | 22.41 MiB/s, done.
Resolving deltas: 100% (5120/5120), done.
warning: Remote branch uvcdat-2.2.0 not found in upstream origin, using HEAD instead
error: pathspec 'origin/uvcdat-2.2.0' did not match any file(s) known to git.
make[2]: *** [vistrails-prefix/src/vistrails-stamp/vistrails-install] Error 1
make[1]: *** [CMakeFiles/vistrails.dir/all] Error 2

git used (RedHat 6)

git version 1.7.1

@doutriaux1 doutriaux1 added the Build label May 28, 2015

@doutriaux1 doutriaux1 added this to the 2.3 milestone May 28, 2015

@aashish24

This comment has been minimized.

Contributor

aashish24 commented May 29, 2015

@doutriaux1 what you are trying to do? You can use tag as branch name in git. It works on certain versions on on others it doesn.t

@doutriaux1

This comment has been minimized.

Member

doutriaux1 commented May 29, 2015

@aashish24 I'm not trying to do anything. Checked out "release" ran cmake, got this.

@doutriaux1

This comment has been minimized.

Member

doutriaux1 commented May 29, 2015

@aashish24 I'm not sure what's up with this system. I built w/o any problem on other RH6. I think we fixed this issue for other packages (uvcmetrics ?) before, we probably simply need to tweak this one to make sure it works on all systems as well.

@aashish24

This comment has been minimized.

Contributor

aashish24 commented May 29, 2015

I know the problem. We need to push uvcdat-2.2.0 as branch as well.

@doutriaux1

This comment has been minimized.

Member

doutriaux1 commented May 29, 2015

yes it would be nice, that's why I opened the issue so we don't forget about it

@doutriaux1

This comment has been minimized.

Member

doutriaux1 commented Oct 14, 2015

@mcenerney1 branch fixed this i think, if someone runs into it again feel free to reopen.

@doutriaux1 doutriaux1 closed this Oct 14, 2015

@chaosphere2112 chaosphere2112 added the Bug label Nov 18, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment