douyue7408 2018-05-27 07:53
浏览 1256


When running glide install on my project, I get the following error:

[ERROR] Error scanning cannot find package "." in:
[ERROR] Failed to retrieve a list of dependencies: Error resolving imports

When checking protobuf's source code, I can in fact see that there is no such package. I however don't directly use protobuf, so the error must come from one of the dependencies I use.

When running glide tree on my project, there is only one instance of

|--   (/Users/bevernie/Programmation/work/src/
|   |--   (/Users/bevernie/Programmation/work/src/
|   |   |-- (Recursion)   (/Users/bevernie/Programmation/work/src/
|   |--   (/Users/bevernie/Programmation/work/src/
|   |   |-- (Recursion)   (/Users/bevernie/Programmation/work/src/   (glide get
|--   (/Users/bevernie/Programmation/work/src/
|   |--   (/Users/bevernie/Programmation/work/src/
|   |   |--   (/Users/bevernie/Programmation/work/src/
|   |   |   |-- (Recursion)   (/Users/bevernie/Programmation/work/src/
|   |   |-- (Recursion)   (/Users/bevernie/Programmation/work/src/

which doesn't really help me pinpoint the source of the problem.

Do you have any suggestions as of how to fix the issues?

My project was compiling just fine until a week or two ago (I use Docker to deploy in production, so the glide install was run every time and never failed before that, and I haven't added any new dependency recently).

  • 写回答

1条回答 默认 最新

  • doushen9863 2018-05-27 08:33

    Before your own PR (995), there was glide issue 968

    It looks like it's caused by a repository's structure changing, i.e. a sub-package being moved, or removed entirely.

    Workarounds proposed by Elliot Wright (seeruk):

    If the package that has been updated is under your own control, then I've since found it easier to use some of the newer Go features like type aliases to ease the pain from refactoring.
    So, instead of just moving a package, move it and then make aliases to the new location in the old one so that your older code still works.
    Then, gradually move things over. Basically just mark things as deprecated but make sure they're still usable for a little while until you've ported new code over.

    If the package is not in your control, then you can always clone the version you want manually to your vendor folder and make your updates in your code.
    Once you're done, Glide should let you update again.
    If it's much more complex, sometimes it's even easier to revert to using go get until you're done updating packages, and rely on your $GOPATH contents.

    It's far from ideal, but there are ways you can work around it at least.
    In the mean time, I've also made an issue about this on dep.
    I think they're looking into a way of disabling this kind of check if you just want the tool to trust you as the developer.

    So you can check if you have the same issue using godep, or even the bleeding-edge vgo.

    本回答被题主选为最佳回答 , 对您是否有帮助呢?



  • ¥15 我需要全国每个城市的最新小区名字等数据。
  • ¥15 开发一个小区生态的小程序
  • ¥15 MddBootstrapInitialize2失败
  • ¥15 LCD Flicker
  • ¥15 Spring MVC项目,访问不到相应的控制器方法
  • ¥15 esp32在micropython环境下使用ssl/tls连接mqtt服务器出现以下报错Connected on发生意外错误: 5无法连接到 MQTT 代理,如何解决?
  • ¥15 关于#genesiscsheel#的问题,如何解决?
  • ¥15 Android aidl for hal
  • ¥15 STM32CubeIDE下载程序报错
  • ¥15 微信好友如何转变为会员系统?(相关搜索:小程序)