Summary:
gomvpkg should rewrite import comments (https://golang.org/s/go14customimport) next to the package statements (package foo // import "foo")

What version of Go are you using (go version)?
go version go1.4.2 darwin/amd64

What operating system and processor architecture are you using?
OS X 10.10.3

What did you do?
Moved a package using gomvpkg:

mkdir /tmp/foo 
export GOPATH=/tmp/foo
go get -u golang.org/x/net/...
mkdir -p $GOPATH/src/go.corp.company.com/x/golang.org/x
gomvpkg -from golang.org/x/net -to go.corp.company.com/x/golang.org/x/net
cd $GOPATH/src/go.corp.company.com/x/golang.org/x/net
go test -v ./...

What did you expect to see?
All tests passed.

What did you see instead?
Lots of errors like this due to the import comments not being rewritten:

can't load package: package go.corp.company.com/x/golang.org/x/net/context: code in directory /tmp/foo/src/go.corp.company.com/x/golang.org/x/net/context expects import "golang.org/x/net/context"
can't load package: package go.corp.company.com/x/golang.org/x/net/dict: code in directory /tmp/foo/src/go.corp.company.com/x/golang.org/x/net/dict expects import "golang.org/x/net/dict"
can't load package: package go.corp.company.com/x/golang.org/x/net/html: code in directory /tmp/foo/src/go.corp.company.com/x/golang.org/x/net/html expects import "golang.org/x/net/html"

I also added a test in my fork which now fails but I believe should succeed:
https://github.com/dmitris/tools/compare/custom_import_comments

Fixing the issue would make it easier to use gomvpkg for vendoring instead of third-party tools or custom hacks (Perl / sed scripts etc.). CC'ing @bradfitz for comments (would be great to try to "dogfood" gomvpkg for camlistore vendoring! 😄 )

See https://go-review.googlesource.com/#/c/8969/ for a related discussion of gomvpkg (in the context of updating the Go FAQ and the current pointer to github.com/kr/goven)