fix homebrew on Travis CI
wibeasley opened this issue · comments
This is the result of recent changes in GitHub and Homebrew.
$ brew install curl
Error:
homebrew-core is a shallow clone.
homebrew-cask is a shallow clone.
To `brew update`, first run:
git -C /usr/local/Homebrew/Library/Taps/homebrew/homebrew-core fetch --unshallow
git -C /usr/local/Homebrew/Library/Taps/homebrew/homebrew-cask fetch --unshallow
This restriction has been made on GitHub's request because updating shallow
clones is an extremely expensive operation due to the tree layout and traffic of
Homebrew/homebrew-core and Homebrew/homebrew-cask. We don't do this for you
automatically to avoid repeatedly performing an expensive unshallow operation in
CI systems (which should instead be fixed to not use shallow clones). Sorry for
the inconvenience!
Warning: You are using macOS 10.13.
We (and Apple) do not provide support for this old version.
You will encounter build failures with some formulae.
Please create pull requests instead of asking for help on Homebrew's GitHub,
Twitter or any other official channels. You are responsible for resolving
any issues you experience while you are running this
old version.
Error: curl: no bottle available!
You can try to install from source with e.g.
brew install --build-from-source curl
Please note building from source is unsupported. You will encounter build
failures with some formulae. If you experience any issues please create pull
requests instead of asking for help on Homebrew's GitHub, Twitter or any other
official channels.
The command "brew install curl" failed and exited with 1 during .
Some discussions
I've tried a few things, and am not seeing solutions posted for the recent changes. I'm going to temporarily disable macOS checks until people have agreed on a stable solution. What I've seen involves writing scripts in the travis config, which I'm not too wild about maintaining.
Everything that's failed for this involves curl and TLS certificates. The dataverse isn't involved.
The current error is
══ Failed tests ════════════════════════════════════════════════════════════════
── Error (tests-dataset_files.R:5:3): download tab from DOI and filename ───────
Error: SSL certificate problem: certificate has expired
Backtrace:
█
1. └─dataverse::get_dataverse("dataverse-client-r") tests-dataset_files.R:5:2
2. ├─dataverse:::dataverse_id(...)
3. └─dataverse:::dataverse_id.character(...)
4. └─dataverse::get_dataverse(x, ..., check = FALSE)
5. └─httr::GET(u, httr::add_headers(`X-Dataverse-key` = key), ...)
6. └─httr:::request_perform(req, hu$handle$handle)
7. ├─httr:::request_fetch(req$output, req$url, handle)
8. └─httr:::request_fetch.write_memory(req$output, req$url, handle)
9. └─curl::curl_fetch_memory(url, handle = handle)
── Error (tests-dataset_metadata.R:5:3): download tab from DOI and filename ────
Error: SSL certificate problem: certificate has expired
Backtrace:
...
https://travis-ci.org/github/IQSS/dataverse-client-r/jobs/752167917#L776
Closing this, as we are no longer using Travis CI.