Hey there! Let's break down why you're hitting this issue and how to fix it—this is super common when getting started with Go's dependency system, so you're not alone.

Go's dependency management has evolved a lot over time, and the key thing here is understanding the difference between the old GOPATH mode and the modern Go Modules system (introduced in Go 1.11 and now the default for all new projects).

When you see errors about not finding packages in $GOROOT or $GOPATH, that means Go is falling back to the old GOPATH behavior. In this mode:

• All your project code and dependencies must live under $GOPATH/src
• Go won't automatically download dependencies from GitHub (or any remote repo) for you—you'd have to manually clone them into $GOPATH/src/github.com/wpferg/services yourself

But you're right that Go does support fetching packages directly from GitHub! The catch is that this only works with Go Modules enabled, which handles dependency downloading, versioning, and caching automatically, without tying your project to the GOPATH directory structure.

Assuming you're using Go 1.11 or newer (check with go version), here's how to fix this:

1. Navigate to your cloned repository directory
   Open your terminal and cd into the folder where you cloned the web service repo.

2. Check for an existing go.mod file
   Run ls (or dir on Windows) to see if there's a go.mod and go.sum file in the root of the repo.

   • If these files exist: Just run go mod download—this will fetch all the dependencies listed in go.mod and store them in Go's global module cache (usually $GOPATH/pkg/mod).
   • If these files don't exist: You need to initialize Go Modules for the project. Run:

     go mod init github.com/wpferg/services
     

     This matches the import path you're using (since your imports start with github.com/wpferg/services/...), which is important for Go to resolve the dependencies correctly.

3. Sync your dependencies
   Next, run:

   go mod tidy
   

   This command scans your code to find all imported dependencies, downloads any missing ones, and updates go.mod and go.sum to reflect the exact versions you're using.

4. Run your project
   Now you should be able to run your code without issues:

   go run main.go
   

• Go Modules are enabled by default in Go 1.13+. If you're on an older version (1.11-1.12), you might need to set the GO111MODULE environment variable to on with export GO111MODULE=on (Linux/macOS) or set GO111MODULE=on (Windows) before running the above commands.
• The module cache ($GOPATH/pkg/mod) is shared across all your Go projects, so you won't download the same dependency version multiple times.

内容的提问来源于stack exchange，提问作者hotmeatballsoup