Your package python-dbusmock failed to build from source in current rawhide. http://koji.fedoraproject.org/koji/taskinfo?taskID=6981360 For details on mass rebuild see https://fedoraproject.org/wiki/Fedora_21_Mass_Rebuild
Created attachment 905167 [details] build.log
Created attachment 905168 [details] root.log
Created attachment 905169 [details] state.log
Created attachment 907310 [details] build log Fails on RHEL-7 even with the latest upstream package.
A bit of progress on https://admin.fedoraproject.org/updates/python-dbusmock-0.11.1-1.fc20 but not there yet.
For the record, the dbusmock template is fixed for NM 0.9.10 (and trunk) in the upstream version 0.11.1. There is one remaining test failure which is due to a regression (crash) in NetworkManager itself, which I reported as https://bugzilla.gnome.org/show_bug.cgi?id=734466 .
So this should go probably to NM maintainers, right?
I guess so; the NM fix got committed upstream a while ago. Alternatively you could of course disable the test in dbusmock, but as this is an actual crash in NM it seems better to just fix that?
The crash from comment #6 is fixed in Fedora. Fedora 21: http://koji.fedoraproject.org/koji/buildinfo?buildID=590579 Rawhide: http://koji.fedoraproject.org/koji/buildinfo?buildID=590588 Is there some other problem in python-dbusmock or can we close the bug now?
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
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.