go: cmd/go: get is broken, old git cannot accept --no-show-signature parameter

What version of Go are you using (go version)?

$ go version
go version go1.11beta2 darwin/amd64

Does this issue reproduce with the latest release?

yes

What operating system and processor architecture are you using (go env)?

$ go env
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/blaz/Library/Caches/go-build"
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/blaz/dev/go"
GOPROXY=""
GORACE=""
GOROOT="/usr/local/go"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/darwin_amd64"
GCCGO="gccgo"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/Users/blaz/src/go/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/2r/wpj58rp17s56swkgt8c2r5nm0000gn/T/go-build234628957=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?

A simple main.go with a dependency to test go mod

package main

import (
	"net/http"

	"github.com/go-chi/chi"
)

func main() {

	r := chi.NewRouter()
	r.Get("/", func(w http.ResponseWriter, r *http.Request) {
		w.Write([]byte("hey"))
	})

	http.ListenAndServe(":9999", r)
}

What did you expect to see?

no error on run

What did you see instead?

$ go run -v main.go
go: finding github.com/go-chi/chi v3.3.2+incompatible
Fetching https://github.com?go-get=1
Parsing meta tags from https://github.com?go-get=1 (status code 200)
go: import "github.com/go-chi/chi": cannot find module providing package github.com/go-chi/chi

thanks

I don’t have this error on linux box

About this issue

  • Original URL
  • State: closed
  • Created 6 years ago
  • Reactions: 1
  • Comments: 15 (9 by maintainers)

Commits related to this issue

Most upvoted comments

I stumbled over the same issue and I found the fact that go doesn’t report anything about a failing command troublesome. I needed to use strace to figure out what’s going on because even with -v nothing was printed about the failing command.

If possible please also extend -v’s output to include for example failing commands to help debugging such issues.

Oh wow. Sorry for this. Was moving across countries. Would have responded sooner otherwise. 😦