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

gitlab downtime broke all the YCM-superbuilds in the world #113

Closed
traversaro opened this issue Feb 1, 2017 · 5 comments
Closed

gitlab downtime broke all the YCM-superbuilds in the world #113

traversaro opened this issue Feb 1, 2017 · 5 comments

Comments

@traversaro
Copy link
Member

Like it happened in #103 .

@traversaro
Copy link
Member Author

Actually is not a change in the URL, is just a downtime in Gitlab due to https://about.gitlab.com/2017/02/01/gitlab-dot-com-database-incident/ . Closing once Gitlab is again up.

@traversaro traversaro changed the title ovito broke again all the YCM-superbuilds in the world gitlab downtime broke all the YCM-superbuilds in the world Feb 1, 2017
@traversaro
Copy link
Member Author

cc @gabrielenava

@traversaro
Copy link
Member Author

To anyone having the same problem: use the offline version of ycm available at https://github.com/robotology/ycm/releases .

@gabrielenava
Copy link

I received the error message in #103 while I was trying to build codyco-superbuild. I circumvented the problem editing this CMakeLists.txt as follows:

ORIGINAL:

    set(_files LICENSE.txt                 8624bcdae55baeef00cd11d5dfcfa60f68710a02
               cmake/FindQCustomPlot.cmake a59dd4d955a5e775270a4f2656a039ae490e03ed)
    set(_ref 8689fcb1fdd2e8dc748e76d54d3b77a3f87d384c)
    set(_dir "${CMAKE_CURRENT_BINARY_DIR}/ovito")

HACKED:

    set(_files LICENSE.txt                 d67fc8b86209db26c338184aaa00e60572045d7d
               cmake/FindQCustomPlot.cmake d67fc8b86209db26c338184aaa00e60572045d7d)
    set(_ref 8689fcb1fdd2e8dc748e76d54d3b77a3f87d384c)
    set(_dir "${CMAKE_CURRENT_BINARY_DIR}/ovito")

@traversaro
Copy link
Member Author

The Gitlab downtime is now solved, closing the issue (even if #105 remains open).

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

2 participants