Update to upstream version '0.0.16'
with Debian dir 8ee159076086af1b1fe9b04b24911dcf74f794d3

Fix T685 out of spite.

While we wait for a cleaner refactoring of this code, this fixes the immediate
clogging of the database with bogus data issue.

Update to upstream version '0.0.15'
with Debian dir 97dc0b51a86e37118da8229816323f139f51f753

Related T703

This resolves the caveat mentioned in prior commit about not being
able to use blake2 prior to 3.5

Related T692
Closes D192

- Add module docstring
- Add blake2s256 and blake2b512 in supported algorithms
- Spawn a new variable DEFAULT_ALGORITHMS as default computed
  algorithms for the main functions

Related T692

Remove the limit on the python3 version, this should be transparent.
If the hash requested is not available, this will raise with an
explanation on the error.

Related T692

The same caveat applies, will only be supported from python3.6 onward.

Related T692

The caveat is that it will only be supported when we will be using
python3 >= 3.5.

Related T692

Update to upstream version '0.0.14'
with Debian dir 8cff57a553c99d8ddb0376b975d4cc85ab2fbacc

Related T700

Closes T255
Ref. D179

Found by investigating T75

Update to upstream version '0.0.13'
with Debian dir 439aa89bb06c7be06d404762c3794fc4e105500e

The subversion loader (T680) has shown that throwing floating point values
around for timestamps is a mess waiting to happen.

We now coerce all clients to send us timestamps as integer numbers of seconds
and microseconds, avoiding data losses everywhere.

Update to upstream version '0.0.12'
with Debian dir 4a001e17c2684cfef3b0db63e6fcadcb8171e22f

- default
- ignoring empty folders
- ignore folder based on pattern in names

Update to upstream version '0.0.11'
with Debian dir a108f7c4dbea9105ec578d819bf6d8c357e6501c