Client installation fails during provisioning because python-jsonschema is unavailable

[Max Brustkern]

I'm currently getting failures installing the utah-client package during provisioning because python-jsconschema is unavailable. I'd like to provide that deb in the server package so we can install it without access to the PPA if needed. Are you building it from a recipe somewhere, or should I just grab the version that's currently in the PPA and use that?

[Javier Collado (javier.collado)]

Is that happening because lack of network connection? My first idea about jsonschema was to add it as a third party package to sources in `utah.contrib` since it's just a single source file. However, Joe preferred not to have it in the utah branch, so maybe we should rethink this or discuss again to see how to fix this problem.

Regarding the package, I built it locally using `pkgme`, but there isn't any launchpad recipe, so if you need the source package then grab it directly from launchpad.

[Max Brustkern (nuclearbob)]

I'm testing some changes for this that are here:
https://code.launchpad.net/~nuclearbob/utah/internal-jsonschema
In this branch, during the postinst for utah, we pull a python-jsonschema deb from the PPA, and then during installclient in provisioning, we install that. If it works, I'll propose it for merging.