use github import paths as they always work and mumble.info does not

[HorayNarea]

No description provided.

[ghost]

This could just be fixed by updating mumble.info's HTTPS certificate. In the mean time, you could pass -insecure to go get:

go get -insecure -u mumble.info/grumble/cmd/grumble

[HorayNarea]

I know but why not just use the github paths?
The source is hosted here and mumble.info has no informations about grumble other than "it exists"

also: i personally find it more logical that import-paths point directly to where the source "lives" but thats just my opinion :)

[HorayNarea]

another argument to merge this PR: #4 (comment)

[mkrautz]

Fixed SSL for the apex mumble.info. This should work w/o any changes now.

[HorayNarea]

No it doesn't:

go get -v -u mumble.info/grumble/cmd/grumble       
Fetching https://mumble.info/grumble/cmd/grumble?go-get=1
Parsing meta tags from https://mumble.info/grumble/cmd/grumble?go-get=1 (status code 404)
package mumble.info/grumble/cmd/grumble: unrecognized import path "mumble.info/grumble/cmd/grumble" (parse https://mumble.info/grumble/cmd/grumble?go-get=1: no go-import meta tags)

[mkrautz]

Sorry. When I tested it, I "accidently" did go get mumble.info/grumble first ... which, of course, fetches the repo and makes everything work.

I'll fix it.

[mkrautz]

Should be fixed now, can you confirm?

Also, thank you for taking the time to author the patch! But I'd like to keep the current mumble.info URLs.

[HorayNarea]

Yes it's working, thank you!