Comment 11 for bug 1634609

"Also, I requested that golang-go.crypto be de-vendorized in juju-core in zesty and continue to not be vendorized in xenial since it is an LTS and we'll be supporting it for quite some time."

Not convinced this is what's happened. Looking at a xenial build log, it certainly *builds* a local copy of crypto. And if, as this bug states, the crypto in yakkety was too old for juju, I don't see how the crypto in xenial would be magically okay, given that the juju versions are the same in both.