update: I think I might I found the issue, the bot doesn't seems to follow 
redirections (at least 301 ones).

Thanks to the option "-x" of go get:

go get -x nspeed.app/nspeed@v0.12.0
leads to 
 https://nspeed.app/nspeed?go-get=1
which redirects '301) to the same url but with trailing slash:
 https://nspeed.app/nspeed/?go-get=1 
which has the go-import tag but the bot doesn't seem to follow the 
redirection.

Is this the expected behavior of the bot?
Le mardi 12 novembre 2024 à 10:12:35 UTC+1, JeffG a écrit :

> I have a custom url package nspeed.app/nspeed which redirects to 
> github.com/nspeed-app/nspeed (using a meta tag go-import):
>
> <meta name=go-import content="nspeed.app/nspeed git 
> https://github.com/nspeed-app/nspeed>
>
> It was setup a year ago or so with version v0.11.0 and was working fine.
> Today I updated some code and the github repo tag to v0.12.0
> waited a few days then
>
> go get nspeed.app/nspeed@latest
>
> but it still fetch the old version.
>
> So I tried to force the update as specified here: 
> https://pkg.go.dev/about#adding-a-package
> to update from the pkg web site directly:
> https://pkg.go.dev/nspeed.app/nsp...@v0.12.0 
> <https://pkg.go.dev/nspeed.app/nspeed@v0.12.0>
> first I clicked the "request" button but later the page displays "not 
> found"
>
> then I tried with proxy and 'go get', I get the same error about xml:
> curl https://proxy.golang.org/nspeed.app/nspeed/@v/v0.12.0.info
>
> go: nspeed.app/nsp...@v0.12.0 <http://nspeed.app/nspeed@v0.12.0>: 
> unrecognized import path "nspeed.app/nspeed": parsing nspeed.app/nspeed: 
> XML syntax error on line 1: expected /> in element
>
> I am probably missing something or are go-import meta tags not working 
> anymore may be?
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion visit 
https://groups.google.com/d/msgid/golang-nuts/3ed8d706-4f8e-44ac-a9f2-bfef6351954en%40googlegroups.com.

Reply via email to