Comment 18 for bug 1729880

Thanks. I was able to build juju and juju-tools in go on a different architecture. Build the tarball with juju tools build. Replace FORCE-VERSION file with 2.2.6.1 and then go back to the machine I deployed my controller from and run juju tools upgrade juju-2.2.6.1-xenial-arm64.tgz.

However, I think most of this was unnecessary. I should have copied an existing 2.2.6-xenial-arm64, modified/created FORCE-VERSION with 2.2.6.1 and renamed the tarball to 2.2.6.1-xenial-arm64.tgz and uploaded that with juju tools upgrade since the patch only affects the controller