Your package python-foolscap failed to build from source in current rawhide. http://koji.fedoraproject.org/koji/taskinfo?taskID=6984034 For details on mass rebuild see https://fedoraproject.org/wiki/Fedora_21_Mass_Rebuild
Created attachment 905272 [details] build.log
Created attachment 905273 [details] root.log
Created attachment 905274 [details] state.log
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
All but one of the 109 test failures are due to http://foolscap.lothar.com/trac/ticket/141 , which should be fixed in upstream foolscap 0.8.0 (see bug 1214129 for update request). The remaining test failure is: exceptions.AttributeError: 'CancelPendingDeliveries' object has no attribute 'tubA' foolscap.test.test_tub.CancelPendingDeliveries.test_cancel_pending_deliveries I will file this upstream. There may be other test failures which would only be visible after the upgrade to 0.8.0.
Filed upstream as http://foolscap.lothar.com/trac/ticket/234#ticket .
Brian Warner (author of foolscap) wrote: > That failure [i.e. http://foolscap.lothar.com/trac/ticket/234 ] almost certainly an artifact of the SSL problem. I'm pretty sure that 0.8.0 will fix it.
python-foolscap-0.8.0-1.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/python-foolscap-0.8.0-1.fc22
Package python-foolscap-0.8.0-1.fc22: * should fix your issue, * was pushed to the Fedora 22 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing python-foolscap-0.8.0-1.fc22' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-11629/python-foolscap-0.8.0-1.fc22 then log in and leave karma (feedback).
python-foolscap-0.8.0-1.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.