Ubuntu
s3ql package

  1. Bug #1272375
  2. Activity log

Activity log for bug #1272375

Date Who What changed Old value New value Message
2014-01-24 15:16:27 Martin Pitt bug added bug
2014-01-26 18:19:36 Matthias Klose bug added subscriber Matthias Klose
2014-01-27 06:39:44 Martin Pitt description When running s3ql's tests with python3.4 as default python3 version, all tests fail completely: ____________________ ERROR collecting tests/t1_backends.py _____________________ tests/t1_backends.py:11: in <module> > from s3ql.backends import local, s3, gs, s3c, swift, rackspace E ImportError: No module named s3ql.backends ______________________ ERROR collecting tests/t1_dump.py _______________________ tests/t1_dump.py:11: in <module> > import unittest2 as unittest E ImportError: No module named unittest2 __________________ ERROR collecting tests/t1_ordered_dict.py ___________________ tests/t1_ordered_dict.py:11: in <module> > import unittest2 as unittest E ImportError: No module named unittest2 ___________________ ERROR collecting tests/t2_block_cache.py ___________________ tests/t2_block_cache.py:12: in <module> > from s3ql.backends import local E ImportError: No module named s3ql.backends and similar. There are a few such failures when merely making python3.4 a supported version (but not the default), as in current trusty-proposed: https://jenkins.qa.ubuntu.com/job/trusty-adt-s3ql/36/ARCH=i386,label=adt/ but it is not nearly as bad. When running s3ql's tests with python3.4 as default python3 version, all tests fail completely: http://people.canonical.com/~pitti/tmp/autopkgtest-py34/fail/py34-s3ql/results/ ____________________ ERROR collecting tests/t1_backends.py _____________________ tests/t1_backends.py:11: in <module> > from s3ql.backends import local, s3, gs, s3c, swift, rackspace E ImportError: No module named s3ql.backends ______________________ ERROR collecting tests/t1_dump.py _______________________ tests/t1_dump.py:11: in <module> > import unittest2 as unittest E ImportError: No module named unittest2 __________________ ERROR collecting tests/t1_ordered_dict.py ___________________ tests/t1_ordered_dict.py:11: in <module> > import unittest2 as unittest E ImportError: No module named unittest2 ___________________ ERROR collecting tests/t2_block_cache.py ___________________ tests/t2_block_cache.py:12: in <module> > from s3ql.backends import local E ImportError: No module named s3ql.backends and similar. There are a few such failures when merely making python3.4 a supported version (but not the default), as in current trusty-proposed:   https://jenkins.qa.ubuntu.com/job/trusty-adt-s3ql/36/ARCH=i386,label=adt/ but it is not nearly as bad.
2014-01-28 10:22:37 Martin Pitt s3ql (Ubuntu): status New Fix Committed
2014-02-19 13:07:51 Matthias Klose s3ql (Ubuntu): status Fix Committed Invalid