https://bugzilla.redhat.com/show_bug.cgi?id=1428551



--- Comment #4 from Fabio Valentini <[email protected]> ---
This doesn't seem to work, because if installing code to both import prefixes,
I get the following error:

+ go test -compiler gc -ldflags '' bitbucket.org/kardianos/osext
can't load package: package bitbucket.org/kardianos/osext: code in directory
/builddir/build/BUILDROOT/golang-bitbucket-kardianos-osext-0-0.15.git9b883c5.fc25.x86_64/usr/share/gocode/src/bitbucket.org/kardianos/osext
expects import "github.com/kardianos/osext"

If I disable tests for the old import prefix, the package builds fine (and the
built packages look good). But I suspect this doesn't only affect tests that
use the old import prefix, but compilation of dependent packages (that expect
the old import prefix), too ...

You can see the adapted .spec file at
https://decathorpe.fedorapeople.org/packages/golang-bitbucket-kardianos-osext.spec

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component
_______________________________________________
package-review mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to