Build Fails Due to Dependency Version Mismatch

[back678]

Description

While rebuilding the project at commit 759f74b using the latest version of Go, with Go's official recommendation to use Go modules 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 golang.org/x/crypto/ssh/terminal in golang.org/x/crypto v0.26.0
go: found github.com/spf13/pflag in github.com/spf13/pflag v1.0.5
go: found github.com/stretchr/testify/assert in github.com/stretchr/testify v1.9.0
go: github.com/bryanwb/kh imports

github.com/Sirupsen/logrus: github.com/Sirupsen/logrus@v1.9.3: parsing go.mod:

module declares its path as: github.com/sirupsen/logrus

but was required as: github.com/Sirupsen/logrus

Result

The build fails with errors related to mismatched module path.

The error dependency is github.com/Sirupsen/logrus.

Reason

The error log suggests module path declaration github.com/sirupsen/logrus in go.mod, which is inconsistent with import path github.com/Sirupsen/logrus .

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/Sirupsen/logrus is v0.11.4. 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 version for the dependency replace github.com/Sirupsen/logrus => github.com/sirupsen/logrus v1.9.3.

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:

module github.com/bryanwb/kh

go 1.25.0

replace github.com/stretchrcom/testify => github.com/stretchr/testify v1.9.1-0.20240709134403-ab114f88b1f1

replace github.com/getsentry/raven-go => github.com/getsentry/raven-go v0.2.1-0.20190409090859-5c2ecc32517a

replace github.com/stretchr/objx => github.com/stretchr/objx v0.0.0-20140120182021-45365c7b5100

replace github.com/spf13/pflag => github.com/spf13/pflag v1.0.10

replace github.com/satori/uuid => github.com/satori/uuid v0.0.0-20150829024907-08f0718b61e9

replace github.com/sirupsen/logrus => github.com/sirupsen/logrus v0.8.0

replace github.com/gofrs/uuid => github.com/gofrs/uuid v3.2.1-0.20190320161447-2593f3d8aa45+incompatible

replace github.com/kardianos/osext => github.com/kardianos/osext v0.0.0-20150410034420-8fef92e41e22

replace github.com/pkg/errors => github.com/pkg/errors v0.8.1-0.20180311214515-816c9085562c

replace github.com/pmezard/go-difflib => github.com/pmezard/go-difflib v0.0.0-20151028094244-d8ed2627bdf0

replace github.com/bugsnag/panicwrap => github.com/bugsnag/panicwrap v1.2.1-0.20170829152406-dd8df9a3778a

replace github.com/stretchr/signature => github.com/stretchr/signature v0.0.0-20140511203316-3024f279a5c0

replace github.com/codegangsta/inject => github.com/codegangsta/inject v0.0.0-20131106015159-01a1370030f9

replace github.com/certifi/gocertifi => github.com/certifi/gocertifi v0.0.0-20140602232852-b5624cb6b7f8

replace github.com/go-martini/martini => github.com/go-martini/martini v0.0.0-20131125001811-15a593848876

replace github.com/Sirupsen/logrus => github.com/Sirupsen/logrus v0.11.4

replace github.com/ogier/pflag => github.com/ogier/pflag v0.0.2-0.20201014131745-9e8f0fbc76fb

replace github.com/dullgiulio/pingo => github.com/dullgiulio/pingo v0.0.0-20150427120856-60fd8065af20

replace github.com/bugsnag/bugsnag-go => github.com/bugsnag/bugsnag-go v1.3.2-0.20180912122408-1e41787c97f5

replace github.com/stretchr/stew => github.com/stretchr/stew v0.0.0-20130812190256-80ef0842b48b

replace github.com/hashicorp/go-multierror => github.com/hashicorp/go-multierror v0.0.0-20161216184304-ed905158d874

replace github.com/davecgh/go-spew => github.com/davecgh/go-spew v1.1.1-0.20180203072859-87df7c60d582

replace github.com/hashicorp/errwrap => github.com/hashicorp/errwrap v1.1.1-0.20241118160026-9218d8eb7691

replace github.com/stretchr/commander => github.com/stretchr/commander v0.0.0-20130925004555-18f86d1c1da1

require github.com/Sirupsen/logrus v0.11.4

require github.com/dullgiulio/pingo v0.0.0-20150427120856-60fd8065af20

require github.com/hashicorp/go-multierror v0.0.0-20161216184304-ed905158d874

require github.com/davecgh/go-spew v1.1.1 // indirect

require github.com/hashicorp/errwrap v1.1.1-0.20241118160026-9218d8eb7691 // indirect

require github.com/spf13/pflag v1.0.10

require github.com/pmezard/go-difflib v1.0.0 // indirect

require (
	github.com/stretchr/testify v1.11.1
	golang.org/x/crypto v0.50.0
)

require (
	golang.org/x/sys v0.43.0 // indirect
	golang.org/x/term v0.42.0 // indirect
	gopkg.in/yaml.v3 v3.0.1 // 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.

[back678]

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