Build Fails Due to Dependency Version Mismatch

[deer8888]

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 github.com/mitchellh/go-homedir in github.com/mitchellh/go-homedir v1.1.0
go: found github.com/Masterminds/glide/importer in github.com/Masterminds/glide v0.13.3
go: github.com/glide-im/glide imports
        github.com/codegangsta/cli: github.com/codegangsta/[email protected]: parsing go.mod:
        module declares its path as: github.com/urfave/cli
                but was required as: github.com/codegangsta/cli

Result

The build fails with errors related to mismatched module path.

The error dependency is github.com/codegangsta/cli.

Reason

The error log suggests module path declaration github.com/urfave/cli in go.mod, which is inconsistent with import path github.com/codegangsta/cli .

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/codegangsta/cli is v1.19.1. 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/codegangsta/cli => github.com/urfave/cli v1.22.15. 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/mitchellh/go-homedir v0.0.0-20180523094522-3864e76763d9

require github.com/Masterminds/semver v1.5.0

require (
    github.com/Masterminds/vcs v1.13.3
    github.com/codegangsta/cli v1.19.1
    gopkg.in/yaml.v2 v2.4.0
)

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]

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?
@mattfarina