Before call uninstall, the pin is verified and it can cause error if picked version is mandatory.

   The version 1.0.84 was used by an existing tag on the
   version control, so it would be inconsistent to use this
   version number.

The query present in the sql dump sets gtid_slave_pos, which is used by
slave_pos. current_pos relies on gtid_current_pos, which is not set here
and hence fails to initiate replication.
Another (unintended) effect of using slave_pos is that queries run on the
slave will not break replication. There should be no reason to run queries
on slave (at least, data & schema modification queries while replication
is active), so it would seem better to fail the replication immediately in
order to detect this. So this may not be the best solution - but at least
this fixes this script.

We still want to check the signature of the reference .data file and of the index

/reviewed-on nexedi/slapos!453

It will be used on python2.7

from https://docs.python.org/2/library/subprocess.html :
POSIX users (Linux, BSD, etc.) are strongly encouraged to install and
use the much more recent subprocess32 module instead of the version
included with python 2.7. It is a drop in replacement with better
behavior in many situations.

/reviewed-on nexedi/slapos!476

This is needed by slapos.recipe.cmmi

To fix the build of golang1.10, since the buildout process keeps
/dev/random and /dev/urandom open (where ?).

  The version 1.4.12 was broken so it required a re-release

Always running SQL_CHANGE_MASTER breaks GTID setup (at least on 10.1.24)
as it resets MASTER_USE_GTID. So only run it when not using GTID.
Also, fold SQL_SET_GTID into the existing "if" bloc for simplicity.

( not needed for the current work on jsonschema draft 7 support, but
done at the same time, to merge together two unrelated changes which
cause recompilation so that we recompile only once )

jsonschema = 3.0.0a3 needs a recent setuptools, probably because it uses
setuptools_scm

jsonschema needs six>=1.11.0

Version and requirements information containing six:
  [versions] constraint on six: 1.10.0
  Requirement of mock==2.0.0: six>=1.9
  Requirement of slapos.core==1.4.11: six
  Requirement of bcrypt==3.1.4: six>=1.4.1
  Requirement of cryptography==2.3.1: six>=1.4.1
  Requirement of jsonschema: six>=1.11.0
  Requirement of manuel: six
  Requirement of cliff: six>=1.9.0
  Requirement of pyOpenSSL>=18.0.0: six>=1.5.2

with support for draft7 of json schema

The case where test runner is not enabled got broken in
2a457867

As now the signature is parameterized (in the case of the webrunner),
computing the signature may require not-webrunner-based tools (like
a binary belonging to the SR. Then it can only be done on the
export and the import.

So that we can use
nexedi/slapos.core!51

/reviewed-on nexedi/slapos!438

@tomo @rafael if you have any review on this (should be ok as its kind of same commit than last update one, but well)

/reviewed-on nexedi/slapos!433

this is a followup of nexedi/slapos!427

/reviewed-on nexedi/slapos!431

Since f427842b some software releases has been
found to be without pinnsed eggs for GitPython dependency.

/reviewed-on nexedi/slapos!432

/reviewed-on nexedi/slapos!427

There was two sections writing the file `bin/monitor-httpd` which led to some problems when running things

/reviewed-on nexedi/slapos!426