This bug was fixed in the package s3ql - 2.13+dfsg-1
---------------
s3ql (2.13+dfsg-1) unstable; urgency=medium
* New upstream release.
* Dropped patches/fix_test_check_objects_temp.diff (fixed upstream).
* Dropped patches/debug_test_thread_hang.diff (fixed upstream).
* Fixed a bug that caused fsck.s3ql to either abort with a
"apsw.ConstraintError" or to incorrectly consider storage objects
as missing when the connection to remote server is interrupted
while retrieving the object list. Closes: #771452.
* Fixed a problem where mount.s3ql would crash when unmouting the
file system because it could not delete the cache directory. This
could happen when the file system was not unmounted cleanly, but
fsck.s3ql was then run on a different system (or using a different
cache directory). Closes: #772052.
-- Nikolaus Rath <nikol...@rath.org> Sat, 31 Jan 2015 20:16:12 -0800
** Changed in: s3ql (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1223514
Title:
autopkgtest failure: Tests fails to import s3ql python modules
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/s3ql/+bug/1223514/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
