python-boto 2.35.1 is available. The version in EPEL is 2.34.0. Please update the package in EPEL to 2.35.1 Thanks.
This is currently blocked by a regression that was introduced in version 2.35.0: https://github.com/boto/boto/issues/2885
According to the github issue mentioned here, this is just a clock skew issue. Meanwhile, boto is already at 2.36.0, and EPEL is still at 2.34.0
python-boto-2.38.0-1.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/python-boto-2.38.0-1.fc21
python-boto-2.38.0-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/python-boto-2.38.0-1.fc20
python-boto-2.38.0-1.el7 has been submitted as an update for Fedora EPEL 7. https://admin.fedoraproject.org/updates/python-boto-2.38.0-1.el7
python-boto-2.38.0-1.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/python-boto-2.38.0-1.el6
Package python-boto-2.38.0-1.el6: * should fix your issue, * was pushed to the Fedora EPEL 6 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=epel-testing python-boto-2.38.0-1.el6' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2015-5760/python-boto-2.38.0-1.el6 then log in and leave karma (feedback).
python-boto-2.38.0-1.el6.noarch breaks duplicity-0.7.02-2.1.csc.x86_64 on centos6: BackendException: Could not initialize backend: No module named vendored
Do you have the full traceback? I suspect it may be using a code path I somehow didn't reach while testing with unbundled python-six.
(In reply to Garrett Holmstrom from comment #9) > Do you have the full traceback? I suspect it may be using a code path I > somehow didn't reach while testing with unbundled python-six. how do I do a full traceback?
To be honest, I am not 100% sure. :-\ Try running it with -v9. This could be due to having an old version of python-six. Which version of python-six do you have installed, and where did you get that duplicity package from?
python-six-1.7.3-1.el6.centos.noarch The duplicity package can be found in this repo: http://anorien.csc.warwick.ac.uk/mirrors/OBS/warwick.ac.uk:/CSC:/Public/CentOS_6/ Last part of the output when running it with -v9: Import of duplicity.backends.azurebackend Succeeded Import of duplicity.backends.botobackend Succeeded Import of duplicity.backends.cfbackend Succeeded Import of duplicity.backends.copycombackend Succeeded Import of duplicity.backends.dpbxbackend Succeeded Import of duplicity.backends.gdocsbackend Succeeded Import of duplicity.backends.giobackend Succeeded Import of duplicity.backends.hsibackend Succeeded Import of duplicity.backends.hubicbackend Succeeded Import of duplicity.backends.imapbackend Succeeded Import of duplicity.backends.lftpbackend Succeeded Import of duplicity.backends.localbackend Succeeded Import of duplicity.backends.megabackend Succeeded Import of duplicity.backends.ncftpbackend Succeeded Import of duplicity.backends.onedrivebackend Failed: invalid syntax (onedrivebackend.py, line 175) Import of duplicity.backends.par2backend Succeeded Import of duplicity.backends.pydrivebackend Succeeded Import of duplicity.backends.rsyncbackend Succeeded Import of duplicity.backends.ssh_paramiko_backend Succeeded Import of duplicity.backends.ssh_pexpect_backend Succeeded Import of duplicity.backends.swiftbackend Succeeded Import of duplicity.backends.sxbackend Succeeded Import of duplicity.backends.tahoebackend Succeeded Import of duplicity.backends.webdavbackend Succeeded Using temporary directory /tmp/duplicity-CNVVda-tempdir Backend error detail: Traceback (most recent call last): File "/usr/bin/duplicity", line 1519, in <module> with_tempdir(main) File "/usr/bin/duplicity", line 1513, in with_tempdir fn() File "/usr/bin/duplicity", line 1354, in main action = commandline.ProcessCommandLine(sys.argv[1:]) File "/usr/lib64/python2.6/site-packages/duplicity/commandline.py", line 1070, in ProcessCommandLine backup, local_pathname = set_backend(args[0], args[1]) File "/usr/lib64/python2.6/site-packages/duplicity/commandline.py", line 961, in set_backend globals.backend = backend.get_backend(bend) File "/usr/lib64/python2.6/site-packages/duplicity/backend.py", line 223, in get_backend obj = get_backend_object(url_string) File "/usr/lib64/python2.6/site-packages/duplicity/backend.py", line 211, in get_backend_object raise BackendException(_("Could not initialize backend: %s") % str(sys.exc_info()[1])) BackendException: Could not initialize backend: No module named vendored BackendException: Could not initialize backend: No module named vendored
python-boto-2.38.0-1.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report.
The release of 'python-boto-2.38.0-1.el7' to the stable repository seems to be bugged. I just installed a new CentOS-7 machine today, installed 'python-boto' and got an error: [vagrant@localhost ~]$ python Python 2.7.5 (default, Jun 17 2014, 18:11:42) [GCC 4.8.2 20140120 (Red Hat 4.8.2-16)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import boto Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/lib/python2.7/site-packages/boto/__init__.py", line 27, in <module> from boto.pyami.config import Config, BotoConfigLocations File "/usr/lib/python2.7/site-packages/boto/pyami/config.py", line 29, in <module> from boto.compat import expanduser, ConfigParser, StringIO File "/usr/lib/python2.7/site-packages/boto/compat.py", line 58, in <module> from boto.vendored import six ImportError: No module named vendored Installing the older rpm 'python-boto-2.34.0-4.el7' works as expected: http://koji.fedoraproject.org/koji/buildinfo?buildID=591755
python-boto-2.38.0-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
python-boto-2.38.0-1.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
The failure on RHEL 7 is bug 1229863.
python-boto-2.38.0-1.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.
Thanks for breaking duplicity on centos6. The error in comment 12 is still caused by the updated python-boto package.
I haven't been able to reproduce that. What exactly did you invoke?
You can find the duplicity package by following the link in comment 12. This is the command I'm using (s3 bucket name starred out): duplicity \ > / \ > --s3-european-buckets \ > --s3-use-multiprocessing \ > --s3-use-new-style \ > --encrypt-key="${GPG_KEY}" \ > --sign-key="${GPG_KEY}" \ > --full-if-older-than 1M \ > s3://s3-eu-west-1.amazonaws.com/*****************/ BackendException: Could not initialize backend: No module named vendored
Works for me: % /usr/bin/duplicity -v9 --s3-european-buckets --s3-use-multiprocessing --s3-use-new-style --full-if-older-than 1M /var/tmp/foo s3://s3-eu-west-1.amazonaws.com/gholms-test-02/ Using archive dir: /root/.cache/duplicity/0b436d0e2efd7a96575243c9d8a676c2 Using backup name: 0b436d0e2efd7a96575243c9d8a676c2 Import of duplicity.backends.azurebackend Succeeded Import of duplicity.backends.botobackend Succeeded Import of duplicity.backends.cfbackend Succeeded Import of duplicity.backends.copycombackend Succeeded Import of duplicity.backends.dpbxbackend Succeeded Import of duplicity.backends.gdocsbackend Succeeded Import of duplicity.backends.giobackend Succeeded Import of duplicity.backends.hsibackend Succeeded Import of duplicity.backends.hubicbackend Succeeded Import of duplicity.backends.imapbackend Succeeded Import of duplicity.backends.lftpbackend Succeeded Import of duplicity.backends.localbackend Succeeded Import of duplicity.backends.megabackend Succeeded Import of duplicity.backends.ncftpbackend Succeeded Import of duplicity.backends.onedrivebackend Failed: invalid syntax (onedrivebackend.py, line 175) Import of duplicity.backends.par2backend Succeeded Import of duplicity.backends.pydrivebackend Succeeded Import of duplicity.backends.rsyncbackend Succeeded Import of duplicity.backends.ssh_paramiko_backend Succeeded Import of duplicity.backends.ssh_pexpect_backend Succeeded Import of duplicity.backends.swiftbackend Succeeded Import of duplicity.backends.sxbackend Succeeded Import of duplicity.backends.tahoebackend Succeeded Import of duplicity.backends.webdavbackend Succeeded Setting multipart boto backend process pool to 4 processes Main action: inc ================================================================================ duplicity 0.7.02 (March 11, 2015) Args: /usr/bin/duplicity -v9 --s3-european-buckets --s3-use-multiprocessing --s3-use-new-style --full-if-older-than 1M /var/tmp/foo s3://s3-eu-west-1.amazonaws.com/gholms-test-02/ ... This is with python-boto-2.38.0-1.el6 and duplicity-0.7.02-2.2.csc. Do you have a manually-installed copy of boto sitting around somewhere? What does ``python -c 'import boto; print boto.__version__, boto.__file__''' yield?
# python -c 'import boto; print boto.__version__, boto.__file__''' Traceback (most recent call last): File "<string>", line 1, in <module> File "/usr/lib/python2.6/site-packages/boto/__init__.py", line 27, in <module> from boto.pyami.config import Config, BotoConfigLocations File "/usr/lib/python2.6/site-packages/boto/pyami/config.py", line 29, in <module> from boto.compat import expanduser, ConfigParser, StringIO File "/usr/lib/python2.6/site-packages/boto/compat.py", line 58, in <module> from boto.vendored import six ImportError: No module named vendored
Well, that's certainly the right place on the filesystem. The other thing that tends to cause that exception is an insufficiently-recent version of python-six, but the version you mentioned earlier is the same one I tested with, and it definitely works. Is that the one python is using or could there be a locally-installed copy lurking somewhere? (python -c 'import six; print six.__version__, six.__file__') If that points to /usr/lib/python2.6/site-packages/six.pyc and you're positive the version is correct then I'm more or less out of ideas. Do you have any? Are you able to replicate this on a clean install?
$ python -c 'import six; print six.__version__, six.__file__' 1.2.0 /usr/lib/python2.6/site-packages/six-1.2.0-py2.6.egg/six.pyc $ rpm -qf /usr/lib/python2.6/site-packages/six-1.2.0-py2.6.egg file /usr/lib/python2.6/site-packages/six-1.2.0-py2.6.egg is not owned by any package Ah! $ ls /usr/lib/python2.6/site-packages | grep six six-1.2.0-py2.6.egg six-1.7.3-py2.6.egg-info six.py six.pyc six.pyo $ rpm -qf /usr/lib/python2.6/site-packages/*six* file /usr/lib/python2.6/site-packages/six-1.2.0-py2.6.egg is not owned by any package python-six-1.7.3-1.el6.centos.noarch python-six-1.7.3-1.el6.centos.noarch python-six-1.7.3-1.el6.centos.noarch python-six-1.7.3-1.el6.centos.noarch Moved away the unowned file. Now: $ python -c 'import six; print six.__version__, six.__file__' 1.7.3 six.pyc It now works. Mystery solved.