FileStore 13.02

Note that because we're switching to Dbase32 encoding for the file IDs, we wont be able to support the interim version zero protocol alongside the final version one protocol; however, we will provide a migration tool that will allow you to migrate your current V0 library to V1.

Starting with V1 and going forward, we will maintain indefinite backward compatibility will all protocol versions, and all versions will be able to coexist alongside one another. Newly added files will be hashed according to the newest protocol version, but you will always be able to locate and verify a file according to an ID computed with an older protocol version. This means the reference integrity between your edits and your files will always be preserved.

Changes include:

* Dropped Python 3.2 support, now requiring Python 3.3 or newer

* Dropped back-ported posix_fadvise() C extension as we can now use os.posix_fadvise() from the Python stdlib

* Changed the V1 protocol from a 280-bit digest to a 240-bit digest, and switched it from Base32 encoding to Dbase32 encoding (note that V0 is still the active protocol, the switch-over to V1 hasn't happened yet)

* For now, removed the protocol selection-by-ID-length functionality; this was still incomplete and as we have a demanding migration ahead of us, it's better to have less complexity to deal with during the migration

* Big refactor of the unit tests for `filestore.protocols`; in particular, no digest values are in the unit tests anymore; instead, digests come from the JSON data files only, making it much easier to tweak a protocol without having to make huge changes in the unit tests

* Removed filestore-crashdb.conf, and updated source_filestore.py to provide the same info as we only need Apport 2.5+ compatibility now

* Added filestore.tests.run entry point for running the tests against the installed package like this:

  $ python3 -m filestore.tests.run