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

msgpack/v4 branch no longer exists #77

Closed
jdub opened this issue Jun 9, 2020 · 7 comments · Fixed by #79
Closed

msgpack/v4 branch no longer exists #77

jdub opened this issue Jun 9, 2020 · 7 comments · Fixed by #79
Assignees

Comments

@jdub
Copy link
Contributor

jdub commented Jun 9, 2020

Entertainingly, the v4 branch of msgpack no longer exists, which breaks non-module builds that depend on libhoney-go. I have also reported the issue upstream.

@vmihailenco
Copy link

I've created v4 branch, but I did not delete v4 - it never existed. I believe it was working as long as there was no v5. Which is understandable but still surprising.

@jdub
Copy link
Contributor Author

jdub commented Jun 9, 2020

Thanks @vmihailenco – Vladimir created the v4 branch, so I'll close this issue now.

@jdub
Copy link
Contributor Author

jdub commented Jul 7, 2020

I have created a gopkg.in-based solution to fix libhoney-go's vmihailenco/msgpack v4 dependency for non-modules users.

@lizthegrey
Copy link
Member

This fix introduces another bug :(

#79 (comment)

@lizthegrey
Copy link
Member

lizthegrey commented Jul 17, 2020

We have two paths forward to unbreak things for non-module users on modern golang1.13+:
(1) Get Github's Dependabot team to fix dependabot/gomodules-extracted#5, and then de-support go1.12 (including the module users)
(2) Get @vmihailenco to change the canonical package name of msgpack library to use gopkg.in going forward, which would enable go1.12 module users, go1.13+ module users, and non-module users on any golang version to all be happy at the cost of having to add a replace directive or changing their import paths.

@lizthegrey
Copy link
Member

(2) is not planned, and instead the proposed solution is to default to msgpack v5 branch.

@MikeGoldsmith
Copy link
Contributor

Closing as I believe #127 fixed the issue.

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 a pull request may close this issue.

4 participants