Skip to content
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

Jump to bottom

doc: mention go get ... failure in README #188

Merged
merged 1 commit into from Jul 5, 2019
Merged

doc: mention go get ... failure in README #188

merged 1 commit into from Jul 5, 2019

Conversation

vicamo
Copy link
Contributor

@vicamo vicamo commented Jul 4, 2019

Closes: #186

@vicamo vicamo force-pushed the for-upstream/document-go-get-failure branch from b22e8f3 to 7c6985e Compare July 4, 2019 15:19
@stgraber
Copy link
Member

stgraber commented Jul 4, 2019

Maybe instead use github.com/lxc/distrobuilder/distrobuilder which will avoid the error.

@vicamo vicamo force-pushed the for-upstream/document-go-get-failure branch from 7c6985e to c81e8d1 Compare July 5, 2019 02:13
@vicamo
doc: use inner source folder for go get ...
4e86746 
Retrieving source with project root folder by `go get` may result in
following error:

  # go get -d -v github.com/lxc/distrobuilder
  github.com/lxc/distrobuilder (download)
  created GOPATH=/root/go; see 'go help gopath'
  package github.com/lxc/distrobuilder: no Go files in /root/go/src/github.com/lxc/distrobuilder

Use the distrobuilder/ one level inside works around this.

Closes: lxc#186
Signed-off-by: You-Sheng Yang <vicamo@gmail.com>
@vicamo vicamo force-pushed the for-upstream/document-go-get-failure branch from c81e8d1 to 4e86746 Compare July 5, 2019 02:14
@stgraber stgraber merged commit 7540ba5 into lxc:master Jul 5, 2019
@vicamo vicamo deleted the for-upstream/document-go-get-failure branch August 3, 2019 10:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

go get ... failed with "no Go files in ..."
2 participants
@vicamo @stgraber