Created attachment 1259419 [details] build.log Build of recent usbguard fails because of test failure on s390x. If the root cause is [1488526261.352] (E) ERROR: loadFiles: /sys/bus/usb/devices: No such file or directory then is it expected, there is no USB on the mainframe (and unlikely ever will be). Our preference is to still build userspace stuff like this, because it reduces the differences from user's and packager's point of view. See build.log from https://s390.koji.fedoraproject.org/koji/taskinfo?taskID=2510629 in attachments. Version-Release number of selected component (if applicable): usbguard-0.6.3-0.1.20170301gitfcde518.fc27
usbguard-0.6.3-0.1.20170319gite528ff6.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-adb1d83ec8
confirmed in https://s390.koji.fedoraproject.org/koji/buildinfo?buildID=481236 Please update F-26 branch too.
(In reply to Dan Horák from comment #2) > confirmed in > https://s390.koji.fedoraproject.org/koji/buildinfo?buildID=481236 > > Please update F-26 branch too. Update for F-26 is pending: https://bodhi.fedoraproject.org/updates/FEDORA-2017-adb1d83ec8
(In reply to Daniel Kopeček from comment #3) > (In reply to Dan Horák from comment #2) > > confirmed in > > https://s390.koji.fedoraproject.org/koji/buildinfo?buildID=481236 > > > > Please update F-26 branch too. > > Update for F-26 is pending: > > https://bodhi.fedoraproject.org/updates/FEDORA-2017-adb1d83ec8 yup, sorry for noise, it built too - https://s390.koji.fedoraproject.org/koji/taskinfo?taskID=2528177
usbguard-0.6.3-0.1.20170319gite528ff6.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-adb1d83ec8
usbguard-0.6.3-0.1.20170319gite528ff6.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.