Closed michaelwnelson closed 10 years ago
@michaelwnelson - apologies for the late response.
I had a look on CentOS and it did work for me - could you please let me know which version of git you have installed? I'll try and build a docker image that matches the environment.
@Gazler
Not a problem! My git version is 1.7.1
@michaelwnelson - it looks like git ls-remote --tags -q .
instead of git ls-remote --tags -q
works, I'll try it out properly in a bit.
Hmm, git ls-remote --tags -q .
didn't seem to work for me.
However, the following does seem to work:
$ git ls-remote --tags ./.
6767e8a0df0cf9980fd789cd2ff9e77de42353e1 refs/tags/tag_to_be_pushed
Found that from git ls-remote --help
under Examples. Sorry I didn't think to look around for that sooner.
@michaelwnelson I have just checked and come to the same conclusion. It looks like everything works without the -q
flag.
Could you just confirm git ls-remote --tags .
works? It did inside my docker image.
@Gazler yes, git ls-remote --tags .
does work.
I'm on CentOS 6.4 and installed git-all, ruby, and rubygems with yum. On level 15, I provided the proper solution 'git push origin --tags', however when attempting to solve the level githug returns the following:
I noticed in levels/push_tags.rb the solution runs the following command:
I'm not sure why the command doesn't resolve correctly on CentOS, but I know it works fine on my Ubuntu box.
On my Ubuntu box on level 15, just running git ls-remote returns:
Obviously on the CentOS box git ls-remote fails, but I do see a directory under /tmp/d20131126-24127-sdkraf
Maybe on the CentOS box githug is having trouble finding or reading that directory?
If there is any other information I can provide to be helpful please let me know.