Open marcindulak opened 7 years ago
golang-github-cheggaaa-pb
should be extended with the new import path prefix instead of creating a new package.
You mean something like providing the link gopkg.in/cheggaaa/pb.v1
to github.com/cheggaaa/pb
under /usr/share/gocode/src/?
rpm -qf /usr/share/gocode/src/gopkg.in
file /usr/share/gocode/src/gopkg.in is not owned by any package
What will happen when gopkg.in/cheggaaa/pb.v2
is released, and we still want to keep gopkg.in/cheggaaa/pb.v1
?
You can check spec file at [1] to see how it handles both v1 and v2 versions.
[1] http://pkgs.fedoraproject.org/cgit/rpms/golang-gopkg-yaml.git/tree/golang-gopkg-yaml.spec#n41
The release of
cheggaaa/pb
required by minishift is https://github.com/cheggaaa/pb/releases/tag/v1.0.7 (see https://github.com/minishift/minishift/blob/a0a53180478ec02b3b4811560f2fc0168c298298/glide.lock)while Fedora 25 currently provides:
go test
fails:Suggested solution requires either:
1A. use
github.com/cheggaaa/pb
instead ofgopkg.in/cheggaaa/pb.v1
in minishift 1B. update golang-github-cheggaaa-pb in Fedora/EPEL7 to version at least 1.0.7 (preferably the latest available)or:
2A. package
gopkg.in/cheggaaa/pb.v1
in Fedora in addition togithub.com/cheggaaa/pb