New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cmd/go: support self-hosted fossil in 'go get' #25811
Comments
The correct command is |
Thanks for your help. It actually still doesn't work for me though.
I don't think it's processing the Go files correctly, as there is a go file in the main branch at the root folder. But it does seem to create a directory, although there is also nothing in it (including the fossil repo):
|
Using raw fossil commands results in errors, is the repo setup correctly and can you clone manually with fossil? |
Sorry, I haven't used fossil before and was using the wrong url. Looks like go get is too. go get is calling |
@schollz, there could be a few thinks going on here. If you have a public URL I can test against, it'd probably be easier. You should set the tag to something like:
or something similar. This is done a little differently depending on if your fossil is before or after the drafts enhancement was implemented. I'd be glad to dig into it, but I need to be able to replicate. For posterity, please report your fossil version as well. We'll get it figured out. |
@ksshannon The URL is public btw, ohh and I tried 2.6 direct download from https://www.fossil-scm.org/xfer/uv/download.html |
@AlexRouSg, I believe it's the head metadata. It works the same with git hosting. |
@ksshannon The metadata error would explain the error with |
|
@AlexRouSg |
@ksshannon Yes it's a 404, but looking at the This is going into undocumented territory ... someone should clarify whether If it's the latter then the issue is |
@AlexRouSg No offense, but I'd like to solve @schollz 's issue first. We can file more issues after if we need to fix fossil support. I'm sure there are issues, but I'm not sure they should fall under this one. |
@ksshannon Thanks for helping too.
The URL (https://fossil.schollz.com/hello-world) is indeed live and a working fossil. You can try it yourself with:
Let me know if I can provide any other information, or if you can point me in the right direction I can try digging too. I'm not so familiar with the Go source yet though. |
@schollz read the docs at: https://golang.org/cmd/go/#hdr-Remote_import_paths And set the meta tag it mentions for you repository. You should be able to add it at: |
@ksshannon Awesome. It works. Here's the header I added:
It is now
Thanks for your help @ksshannon and @AlexRouSg |
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (
go version
)?go version go1.10.3 linux/amd64
Does this issue reproduce with the latest release?
Yes.
What operating system and processor architecture are you using (
go env
)?What did you do?
I am self-hosting fossils using a standalone server. I have a very simple "hello, world" example here: https://fossil.schollz.com/hello-world which I am trying to
go get
. This is a functional fossil, as you can clone and run it:I then tried to
go get
this fossil.What did you expect to see?
I expected to be able to run
which would automatically download
hello-world
as a fossil into my $GOPATH.What did you see instead?
Despite it being run using the canonical
fossil server
command, I am unable togo get
it. Here are the attempts:It seems that the current fossil support only supports
chiselapp.com
- I refer to this change that added support.Is there not yet support for self-hosted fossils?
The text was updated successfully, but these errors were encountered: