-
Notifications
You must be signed in to change notification settings - Fork 0
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
Guess at fixing failing build based on messages from pip. #60
Conversation
This has fixed the build that was failing (for the "example" "pkg_depend" build). However, looks like the same error message then appears in a subsequent build (the "example_pipgit" "pkg_depend" build). Before: After: I haven't looked into the new failure beyond seeing the error message text looked to be the same. I probably won't work more on this PR (and definitely not any more today). |
Yes, repo.continuum.io is now repo.anaconda.com; see https://github.com/pyviz-dev/pyctdev/pull/68/files |
Knowing that the last traces of Continuum are being erased would have been
helpful to know 8 hours ago, thanks 😂
…On Tue, 14 Apr 2020, 20:46 James A. Bednar, ***@***.***> wrote:
Yes, repo.continuum.io is now repo.anaconda.com; see
https://github.com/pyviz-dev/pyctdev/pull/68/files
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#60 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAAPCNNHXZWQISCGUU6IZDRMS4RXANCNFSM4MHFC7JQ>
.
|
The Distribution team was genuinely surprised to hear that anyone was still using repo.continuum.io... |
Ah, there is a redirect of some type - the above wget command works for me. So the joke is on me; I'm presumably not correctly using whatever python lib I use to download the files. (Still, seems like the docs should be updated to the new link? Why have everyone going through the redirect? Not totally sure about the new company name? 😂) |
(noticed in #59)