autopkgtest failure: Tests fails to import s3ql python modules

[Jean-Baptiste Lallement]

s3ql autopkgtests [1] fails because s3ql python modules are not in python path.

______________________ ERROR collecting tests/t3_fsck.py _______________________
tests/t3_fsck.py:11: in <module>
> from s3ql.backends import local
E ImportError: No module named s3ql.backends
___________________ ERROR collecting tests/t3_inode_cache.py ___________________
tests/t3_inode_cache.py:11: in <module>
> from s3ql import inode_cache
E ImportError: No module named s3ql
_______________________ ERROR collecting tests/t4_adm.py _______________________
tests/t4_adm.py:11: in <module>
> from s3ql.backends import local
E ImportError: No module named s3ql.backends
______________________ ERROR collecting tests/t4_fuse.py _______________________
tests/t4_fuse.py:11: in <module>
> from s3ql.common import CTRL_NAME
E ImportError: No module named s3ql.common
[...]

[1] http://jenkins.qa.ubuntu.com/view/Saucy/view/AutoPkgTest/job/saucy-adt-s3ql

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: s3ql 1.16-1
ProcVersionSignature: Ubuntu 3.11.0-6.12-generic 3.11.0
Uname: Linux 3.11.0-6-generic x86_64
ApportVersion: 2.12.1-0ubuntu3
Architecture: amd64
Date: Tue Sep 10 14:34:58 2013
InstallationDate: Installed on 2013-09-03 (6 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
MarkForUpload: True
SourcePackage: s3ql
UpgradeStatus: No upgrade log present (probably fresh install)

[Nikolaus Rath (nikratio)]

Fixed in Debian. Thanks for the report!

[Launchpad Janitor (janitor)]

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 <email address hidden> Sat, 31 Jan 2015 20:16:12 -0800