8000 Build Fails Due to Dependency Version Mismatch · Issue #111 · karan/joe · GitHub
[go: up one dir, main page]

Skip to content
  • Build Fails Due to Dependency Version Mismatch #111

    Open

    Description

    @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/termie/go-shutil in github.com/termie/go-shutil v0.0.0-20140729215957-bcacb06fecae
    go: github.com/postgres-ai/joe imports
            github.com/codegangsta/cli: github.com/codegangsta/cli@v1.22.15: 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

    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.9. 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:

    
    replace github.com/cpuguy83/go-md2man => github.com/cpuguy83/go-md2man/v2 v2.0.3
    
    replace github.com/codegangsta/cli => github.com/urfave/cli v1.22.9
    
    require (
    	github.com/codegangsta/cli v0.0.0-00010101000000-000000000000
    	github.com/termie/go-shutil v0.0.0-20140729201327-48a7c8a8ba60
    )
    
    require (
    	github.com/cpuguy83/go-md2man/v2 v2.0.0-20190314233015-f79a8a8ca69d // indirect
    	github.com/russross/blackfriday/v2 v2.0.1 // indirect
    	github.com/shurcooL/sanitized_anchor_name v1.0.0 // 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.

    Activity

    1. deer8888 commented on Feb 20, 2025

      @deer8888
      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?
      @munrocape

    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

    Metadata

    Metadata

    Assignees

    No one assigned

      Labels

      No labels
      No labels

      Projects

      No projects

        Milestone

        No milestone

        Relationships

        None yet

        Development

        No branches or pull requests

        Issue actions

        0