-
Notifications
You must be signed in to change notification settings - Fork 249
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
Error parsing go.mod module declares its path as: github.com/google/gnostic but was required as: github.com/googleapis/gnostic #262
Comments
There isn't a good workaround at the moment for renaming GitHub repositories without breaking Go module users. I suggest rolling back the name change until golang/go#26904 and/or golang/go#30831 is fixed in the Go toolchain, or moving the repository back to its original name and starting a new (separate) repository for the |
Thanks for the answer and the link @bcmills, it's comforting to see that I'm not the only one struggling with this :) |
Stumbled onto this: google/gnostic#262 when running `go get -u .`, so updated packages with `go get` separately and tidy in the end
We cannot update all, because of the gnostic bug: google/gnostic#262, but we can update the k8s deps at least
We cannot update all, because of the gnostic bug: google/gnostic#262, but we can update the k8s deps at least
Any news about fixing this? I've got bitten when trying to upgrade the dependencies of a project and now this repo reshuffle blocks this as an indirect dependency stopping |
The issue goes away when upgrading to go 1.17.3, at least for me. |
Depending on your product build requirements you cannot simply update go just because some module decided to break its import path, and this change has already propagated into other modules depending on it, so projects end up in a dependency hell. This is exactly I was warned of: go modules not being mature and go being not ripe for productivity with lots of complex dependencies. I have to admit: the critics are right on spot here. |
I just thought I would mention it in case someone has the opportunity to upgrade go. If you have to stay on the same golang version, then obviously that solution doesn't help you :( |
Not for me |
Not for me too, is there any other solution ? |
Atleast error went away after adding this to replases: github.com/googleapis/gnostic => github.com/google/gnostic v0.5.7-0.20211028223514-b1b34ea319d3 |
thanks, I add this to replaces : github.com/googleapis/gnostic v0.5.6 => github.com/googleapis/gnostic v0.5.5. |
The error goes away with the but I seem to reach other issues when I roll back the gnostic version
|
if you don't need latest k8s, maybe you can rollback its version too. |
Only works if you also change go.mod go be |
- Add make targets to easily update dependencies - Add replace directive to work around gnostic upgrade issue - See google/gnostic#262
- Add make targets to easily update dependencies - Add replace directive to work around gnostic upgrade issue - See google/gnostic#262
- Add make targets to easily update dependencies - Add replace directive to work around gnostic upgrade issue - See google/gnostic#262
I had the same issue with the package name, after searching a lot I found golang cache coming from golang proxy server, after rewriting |
the background to this change is that we are preparing to update feed to the networking/v1 Ingress API (from the extensions/v1beta1 API that was previously used, and is now deprecated/removed from recent versions of k8s). in order to accomplish this, we need to update the k8s api libraries to more recent versions. this is a good opportunity to rebaseline our dependencies and shed support for a deprecated module (merlin) within feed. the next version of feed (incorporating the API change) will need to be a major version update, so we can batch these changes with the upcoming ones as well. - update go version to 1.18 - compiler 1.18 is required to build the newest `sigs.k8s.io/yaml` module - go.mod format 1.17 is required because of google/gnostic#262 - use `go get -d -u ./...` to pull in the newest version of all dependencies - delete the `merlin` module - its test suite relied on calling `proto.Clone` which does some reflect tricks with private fields that no longer work correctly - anyway, merlin is EOL so we don't need to keep supporting it - update our usage of the k8s apis - pass a context to the functions that demand one - comply with the new update apis (passing a name of the field manager) - write some new deep-equal functions for a type (`LoadBalancerIngress`) that has fields (slices) in it now that are not comparable by simple `==` - update the k8s test suite to match - use autogenerated mocks for the parts that were touched by this update, to make it easier to keep up with future updates - update ginkgo to v2 - this catches an issue in the gorb tests with a misplaced `Before/AfterSuite` invocation
Got following message from @dependabot
|
Hi,
the recent change of the module name (from
googleapis
togoogle
) causes thego get -u ./...
command to fail in our project wheregnostic
is listed as an indirect dependency.#259
Manually changing the name and version in the mod file doesn't help.
Is there a recommended smooth update path?
The text was updated successfully, but these errors were encountered: