Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: After updating python-boto to 2.38.0-1.el7, duplicity gives the error: BackendException: Could not initialize backend: No module named vendored Version-Release number of selected component (if applicable): python-boto-2.38.0-1.el7.noarch Additional info: The following version works fine: python-boto-2.34.0-4.el7.noarch
Also I'd appreciate any info about how to safely downgrade python-boto alone. Running: yum history undo N .. will remove some other packages as well, such as opendmarc, and I would like to go through fixing *.rpmsave files etc. Also: yum downgrade python-boto-2.34.0-4.el7.noarch .. returns: No package python-boto-2.34.0-4.el7.noarch available. What does 'Unbundled python-six (boto #3086)' mean in the changelog? python-six is installed in my system. Thanks in advance.
>and I would like to go through fixing *.rpmsave files etc. Of course, I meant: "I wouldn't want ..."
IIRC, a python-boto update causing problems to duplicity has happened before. Since duplicity is a commonly used backup utility, maybe it would be nice if more feedback was requested from duplicity users before pushing the python-boto update to the stable repos.
Installed version of python-six: python-six-1.3.0-4.el7.noarch
Steps to resolve (downgrade), until this is fixed: yum remove python-boto cd /tmp wget https://kojipkgs.fedoraproject.org//packages/python-boto/2.34.0/4.el7/noarch/python-boto-2.34.0-4.el7.noarch.rpm yum -y localinstall python-boto-2.34.0-4.el7.noarch.rpm rm -f python-boto-2.34.0-4.el7.noarch.rpm yum install duplicity
Unbundling refers to making something use the system's copy of a library rather than one that it includes alongside its own code, which in boto's case is six. RHEL 7's version of six is too old for boto to use (see bug 1185409), so on that OS it would fall back to the bundled copy if I hadn't papered over this bug on my test VM by forgetting I had recently used my test VM to test a newer version of six. This is fixed in python-boto-2.38.0-2.el7, which you can install from koji and upvote here: https://admin.fedoraproject.org/updates/python-boto-2.38.0-2.el7 python-boto-2.38.0-1.el7 sat in epel-testing for nearly two months with no feedback, positive or negative. Do you know of a way to contact EPEL's duplicity users to ask them to test updates? *** This bug has been marked as a duplicate of bug 1229863 ***
Garrett, thanks for looking into this. I'll update python-boto to python-boto-2.38.0-2.el7 and report back. > python-boto-2.38.0-1.el7 sat in epel-testing for nearly two months with no feedback, positive or negative. Do you know of a way to contact EPEL's duplicity users to ask them to test updates? Unfortunately, there is no other way. I'm enabling epel-testing in one of my VMs and I'll report any problems I notice with duplicity from now on. BTW, I'm testing this on C7 exclusively. Thanks again.
I confirm that python-boto-2.38.0-2.el7.noarch.rpm works fine with duplicity-0.6.24-5.el7.x86_64 and python-six-1.3.0-4.el7.noarch. Thanks for taking care of this. I'll add karma to the koji build.