Comment 17 for bug 1749201

On Mon, Apr 23, 2018 at 09:00:50AM -0000, John A Meinel wrote:
> We expect to have a file "downloaded-tools.txt" that contains a JSON blob
> containing
> {
> "version": "2.3.6-xenial-amd64",
> "URL": "http://path/to/download/location",
> "SHA256": "abcdefgh", # hash of the tools.tar.gz file
> "Size": 1234 # integer length of tools.tar.gz
> }
>
> Note that 2.3.6 has a bad upgrade step, so we're removing it as a target
> and trying to release a 2.3.7 today.
> But that doesn't specifically affect what you're seeing here. (fresh 2.3.6
> is fine, and upgrading series goes via a different path).
>
> It may be that "juju update-series" should do that, though it seems like it
> could be crafted by hand as well.
> Given there was one in trusty, its possible it could just be copied across.

the workaround I'm using is:

cd /var/lib/juju/tools
ln -s ln -s 2.3.6-trusty-amd64 2.3.6-xenial-amd64

It works fine, maybe I should "cp -rfp" instead of using a symlink.

Is this expected to be made by the user? or by juju?, so we can decide if it's a bug in the docs or in juju.