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

Fix unversioned module imports to work with GOPROXY. #643

Closed
wants to merge 2 commits into from

Conversation

mhutchinson
Copy link

All of the imports fixed here failed via proxy.golang.org with 'invalid pseudo-version: does not match version-control timestamp'. This change keeps the same versions but updates the timestamp to something the proxy is happy with as per https://tip.golang.org/doc/go1.13#version-validation.

One exception is that the bodyclose dep has been really updated to include timakin/bodyclose#17 as per the comment. The previous fix pointed at PR 16.

@CLAassistant
Copy link

CLAassistant commented Aug 19, 2019

CLA assistant check
All committers have signed the CLA.

@mhutchinson
Copy link
Author

The Travis tests are failing, but the diff fails for me at HEAD too. My guess is that the .svg generation is not hermetic and something else has changed since the last run. Do the control files need updating?

If this PR has changed something functional please let me know, this is unexpected.

@mhutchinson
Copy link
Author

This looks like it's blocked on PR #625, along with the other PRs outstanding at the moment.

@bvwells
Copy link
Contributor

bvwells commented Sep 4, 2019

Might want to add - 1.13.x to the travis CI definition as go proxy is enabled by default in 1.13 and this would test things are working as expected.

All of the imports fixed here failed via proxy.golang.org with 'invalid pseudo-version: does not match version-control timestamp'. This change keeps the same versions but updates the timestamp to something the proxy is happy with as per https://tip.golang.org/doc/go1.13#version-validation.
@jirfag
Copy link
Member

jirfag commented Sep 9, 2019

Hi, thank you! And sorry for the slow response.
But already fixed in master, please, check

@jirfag jirfag closed this Sep 9, 2019
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

Successfully merging this pull request may close these issues.

None yet

5 participants