8000 Build Fails Due to Dependency Version Mismatch · Issue #27 · theckman/cronner · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Build Fails Due to Dependency Version Mismatch #27

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.

Sign up for GitHub

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

Jump to bottom
Open
deer8888 opened this issue Feb 21, 2025 · 1 comment
Open

Build Fails Due to Dependency Version Mismatch #27

deer8888 opened this issue Feb 21, 2025 · 1 comment

Comments

@deer8888
Copy link

Description

While rebuilding the project using the latest version of Go, with Go's official recommendation to use gomodule for initialization and building, we found that the build process fails due to mismatched module path.

The following error log was produced during the build process:

......
go: found gopkg.in/check.v1 in gopkg.in/check.v1 v1.0.0-20201130134442-10cb98267c6c
go: github.com/theckman/cronner imports
        github.com/theckman/go-flock: github.com/theckman/go-flock@v0.12.1: parsing go.mod:
        module declares its path as: github.com/gofrs/flock
                but was required as: github.com/theckman/go-flock

Result

The build fails with errors related to mismatched module path.

The error dependency is github.com/theckman/go-flock.

Reason

The error log suggests module path declaration github.com/gofrs/flock in go.mod, which is inconsistent with import path github.com/theckman/go-flock .

Proposed Solution

Solution 1

To resolve this issue, we analyzed the project and identified the correct versions of the required dependencies.

The analysis shows that the correct version for the dependency github.com/theckman/go-flock is v0.0.0-20150830235919-2701705350b9. This version has correct module path declaration.

Consider adopting this suggested version to prevent other developers from encountering build failures when constructing the project.

Solution 2

To resolve this issue, we analyzed the project and identified the correct versions of the required dependencies.

The analysis shows that the correct declaration for the dependency is replace github.com/theckman/go-flock => github.com/gofrs/flock v0.12.1. This version is the latest version of the dependency.

Consider adopting this suggested version to prevent other developers from encountering build failures when constructing the project.

This information can be documented in the README.md file or another relevant location.

Additional Suggestions

To ensure reproducible builds and align with the evolving trends of the Go programming language, it is recommended that the current project be migrated to the Go module mechanism.

Updating to the go module mechanism allows for managing third-party dependency versions through the go.mod file, which provides a centralized and consistent way to specify dependency constraints.

We have generated a go.mod file with the correct versions of the third-party dependencies needed for this project.

The suggested go.mod file is as follows:


require github.com/jessevdk/go-flags v1.5.1-0.20240416121059-9090f1aa2d91

require github.com/tideland/golib v0.0.0-20150724141227-20a336fc1af6

require github.com/theckman/go-flock v0.0.0-20150830235919-2701705350b9

require github.com/PagerDuty/godspeed v0.0.0-20150922080216-6ed0b5188fce

require (
	github.com/codeskyblue/go-uuid v0.0.0-20140208115753-952abbca900b
	gopkg.in/check.v1 v1.0.0-20201130134442-10cb98267c6c
)

require (
	github.com/kr/pretty v0.2.1 // indirect
	github.com/kr/text v0.1.0 // indirect
	golang.org/x/sys v0.0.0-20210320140829-1e4c9ba3b0c4 // indirect
)

Additional Information:

This issue was identified as part of our research project focused on automating the analysis of GOPATH projects to provide accurate dependency versions for seamless migration to Go Modules. We value your feedback and would appreciate any comments or suggestions regarding this approach.
@deer8888
Copy link
Author

Looking forward to your response!

Could we update README.md to help other developers use the Go module to build the projects or submit pull requests with go.mod to apply our suggestions?
@theckman

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@deer8888
0