old fortio redirects are broken

[mattmoor]

/assign @srinivashegde86
cc @dushyanthsc

This change removed the go-import <meta> tags that made the old versions work, test-infra needs to move to the fortio.org based import paths ASAP.

istio/istio.io@4d03f08#diff-e3202d59ce8d9d83b8911b4107f87c1e

cc @geeknoid

[mattmoor]

This is an indirect dependency for Serving, so once it is fixed in test-infra, I'd like to verify that my auto-update works for serving.

[geeknoid]

Let me know if you'd like me to reinstate the links for a while.

[mattmoor]

The version of fortio we are on is very old, so I think we need to solve this. If we can't figure it out today, we might reach out about that though. :) thanks @geeknoid

[srinivashegde86]

The sample example mentioned in their docs still uses istio.io - https://github.com/istio/istio/blob/0.3.0/tests/e2e/tests/mixer/mixer_test.go#L37

[srinivashegde86]

Moving to fortio.org fails with "unexpected error while defensively cleaning up after possible derelict nested submodule directories: Entering 'vendor' error: unknown switch `x'"

there was a recent PR in dep when working with submodules - golang/dep#2176. Probably related

[dushyanthsc]

To close the loop here, pinning to a 1.3.1 commit and dep ensure updates the packages correctly. dep ensure -update fortio.org/fortio, tries to pull the latest on fortio and is failing with

 failed to fetch source for fortio.org/fortio: unable to update repository: From https://github.com/fortio/fortio
 ! [rejected]        latest_release -> latest_release  (would clobber existing tag)
: command failed: [git fetch --tags --prune origin]: signal: interrupt