-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Build fails because of transitive dependency: go-md2man #861
Comments
@lszucs you mention a build failing, can you provide an example of it failing on CI? |
Hm, I think it can cause issues with go versions older than 1.12, because I'm not sure if this change really works: 3a41d6d There is a hash calculation mismatch between go 1.11 and and 1.12 which might cause problems. I tried to reproduce the issue within the latest golang:1.12.8 container, but it seems to work fine:
We could still vendor the dependencies in, but I'm not sure if this is a nice solution for this kind of project. |
@lynncyrin Sorry for not being explicit about it: I receive the same kind of error as in the referenced issue.
Go version is Note the paths! We're using
|
Ah, this looks like it may be the same issue as #866? |
@lszucs would be you able to create a sandbox github repo that reproduces this issue on CI? |
@lynncyrin sure https://github.com/bitrise-io/bitrise you must checkout revision and simply run You should see the output mentioned above. |
Yeah If we disable go modules, then it surely needs the dependency. We could vendor the dependency in, WDYT @lynncyrin @AudriusButkevicius ? |
It seems this issue should be raised with md2man, as there is not really much we can do if that does not correctly specify the version of the dependency? Or perhaps we can fix it in our go mod? |
I would prefer we not vendor dependencies - and instead figure out how to fix this using go modules. |
I'm not sure if we can fix this without vendoring... |
So it works if you enable go module support, that's what we use for our package management. The fact that someone tries to build it without go module support is somewhat a Henny Youngman problem, as essentially go modules is the thing that solves the problem they are having, The fact that they use dep or whatever other dependency manager is completely irrelevant to us. |
Recently added dependency
go-md2man
(maybe in 40d4a25#diff-2a0cb88ddd9482c046c169b7b242d36c ) causes compile time errors.For some reason, the vendor folder is missing from the dependency. If I clone
go-md2man
I can build it fine. If I copy thevendor
folder under our projectsvendor
, everything works as expected.This is only an issue if depending on
master
branch (rev: 693af58),v1.21.0
is cool.Issue filed in
go-md2man
repo: cpuguy83/go-md2man#48The text was updated successfully, but these errors were encountered: