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

github.com/godbus/dbus/v5: cannot find package in 0.2.1 Beta #325

Open
ywarnier opened this issue Dec 4, 2019 · 0 comments · May be fixed by #326
Open

github.com/godbus/dbus/v5: cannot find package in 0.2.1 Beta #325

ywarnier opened this issue Dec 4, 2019 · 0 comments · May be fixed by #326

Comments

@ywarnier
Copy link

ywarnier commented Dec 4, 2019

Hi,

I believe this might be something of the moment, as I tried it 2 days ago on a very similar setup and it worked, but today when I "make" the 0.2.1 beta (from the .tar.gz) I get this error:

# make
	[RELOCATE]	  
	[GO-GET]	  git.devever.net/hlandau/acmetool
package github.com/godbus/dbus/v5: cannot find package "github.com/godbus/dbus/v5" in any of:
	/usr/lib/go-1.7/src/github.com/godbus/dbus/v5 (from $GOROOT)
	/tmp/acmetool-0.2.1/src/github.com/godbus/dbus/v5 (from $GOPATH)
package math/bits: unrecognized import path "math/bits" (import path does not begin with hostname)
Makefile:76: recipe for target '.gotten' failed
make: *** [.gotten] Error 1

I checked https://github.com/godbus/dbus/v5 and there's a v4 branch but no v5 (and no history of the removal of v5 I can get to), so I suppose this has moved to master for them or something like that?
Either way, acmetool seems to be depending specifically on that v5 but I don't find the specific dependency defined in the raw source, only after a test at "make".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant