Github messages for voidlinux
 help / color / mirror / Atom feed
From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Go 1.21 breaks 'go get' and 'go mod tidy' downloads
Date: Sat, 26 Aug 2023 21:15:31 +0200	[thread overview]
Message-ID: <20230826191531.O_3sbvKQAsLrX-b-kqlkCG56OYVpwgp0OMNGzbTVXJo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45775@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1207 bytes --]

Closed issue by adrian-bl on void-packages repository

https://github.com/void-linux/void-packages/issues/45775

Description:
### Is this a new report?

Yes

### System Info

Void 6.3.13_1 x86_64 GenuineIntel uptodate rrFFFFF

### Package(s) Affected

go-1.21.0_1

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

Since go-1.21.0_1, downloading modules via `go mod tidy` fails with:

```
        github.com/google/go-cmp/cmp: GOPROXY list is not the empty string, but contains no entries
```

This seems to be due to both `GOPROXY` and `GOSUMDB` being set to an empty value (due to `/usr/lib/go/go.env` not existing?)

```
$ go env|grep -E 'PROXY|SUM'
GONOPROXY=''
GONOSUMDB=''
GOPROXY=''
GOSUMDB=''
```


Upstream-go contains the following go.env file:
https://github.com/golang/go/blob/master/go.env

and setting the same values (either by `export ..` or `go env -w ...`) fixes the issue.

### Expected behaviour

go get and go mod tidy being able to download modules

### Actual behaviour

Fails due to empty GOPROXY setting

### Steps to reproduce

* Upgrade to go1.21
* cd $project
* rm go.*
* go mod init
* go mod tidy # <- fails

      parent reply	other threads:[~2023-08-26 19:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-26  7:27 [ISSUE] Go 1.21 breaks 'go get' downloads adrian-bl
2023-08-26 13:52 ` Go 1.21 breaks 'go get' and 'go mod tidy' downloads sgn
2023-08-26 13:53 ` sgn
2023-08-26 16:28 ` adrian-bl
2023-08-26 19:15 ` Duncaen [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230826191531.O_3sbvKQAsLrX-b-kqlkCG56OYVpwgp0OMNGzbTVXJo@z \
    --to=duncaen@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).