Release Notes: fsck will gracefully recover if temporary indices already exist (e.g. if the previous fsck was interrupted). This release will not fail with a "BadDigest" error when objects are only partially retrieved from the backend.
Release Notes: There are no changes in S3QL itself. The S3QL 2.8 tarball accidentally included a copy of the Python dugong module; this has been fixed.
Release Notes: Fixes various problems with using a proxy server. Sending SIGUSR1 to mount.s3ql now generates a stack trace (debugging feature). When passing --installed to the test runner, S3QL commands are now loaded from $PATH instead of the packages bin/ directory. The runtest.py script now comes with the correct shebang (i.e. it can now be called as "./runtests.py" instead of "python3 runtests.py"). S3QL now requires the Python Dugong module. A filesystem hang when all upload threads encountered unexpected backend problems has been fixed.
Release Notes: Another race condition that could lead to mount.s3ql crashing with `ValueError: I/O operation on closed file` was fixed. S3QL now stores multiple copies of the master encryption key to allow recovery if the backend loses the object holding the primary copy. A problem with automatic cache size detection was fixed (mount.s3ql was treating bytes as kilobytes). An "AttributeError in LegacyDecryptDecompressFilter" crash when reading objects written by old S3QL versions was fixed. A problem with umount.s3ql giving a strange error when the mountpoint is still in use was fixed.
Release Notes: Various changes were made.
Release Notes: Fixes a crash when statvfs() is called on an almost empty filesystem (which may happen automatically when using some desktop environments, resulting in an immediate crash after mounting an empty filesystem). Fixes another race condition that could lead to the (apparent) vanishing of the file system metadata when the mount.s3ql is killed at an unfortunate time.