Your package qtlockedfile failed to build from source in current rawhide. http://koji.fedoraproject.org/koji/taskinfo?taskID=10147921 For details on mass rebuild see https://fedoraproject.org/wiki/Fedora_23_Mass_Rebuild
Created attachment 1047922 [details] build.log
Created attachment 1047923 [details] root.log
Created attachment 1047924 [details] state.log
Wierd one, I cannot reproduce this locally. This may be relevant, https://bugreports.qt.io/browse/QTBUG-44595 (behavior of qtLibraryTarget)
Confirmed, this was a behavior change in 5.4.2 and newer. Looks like it's fixed upstream, https://github.com/qtproject/qt-solutions/commit/5a07df503a6f01280f493cbcc2aace462b9dee57
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle. Changing version to '23'. (As we did not run this process for some time, it could affect also pre-Fedora 23 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23
IMHO it's not good to check qt version in prf file. That's something to do in spec content, if you ask me. as I've done so for QTSA. We've to duplicate prf files in individual folders and modify anyways to the dedicated qt version in use.
qtlockedfile-2.4-18.20150629git5a07df5.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/qtlockedfile-2.4-18.20150629git5a07df5.fc22
qtlockedfile-2.4-18.20150629git5a07df5.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/qtlockedfile-2.4-18.20150629git5a07df5.fc21
that's a tricky sed to get right (multiline replacements), imo, patching is safer and more robust in this case.
Re: comment #7 Checking Qt versions in prf's should not be a problem either, it's (more) upstreamable.
(In reply to Rex Dieter from comment #10) > that's a tricky sed to get right (multiline replacements), imo, patching is > safer and more robust in this case. I guess you mean this comment as an answer to my changes done in QTSA, see bug #1239870. Please continue with discussion there. http://pkgs.fedoraproject.org/cgit/qtsingleapplication.git/commit/?id=17b53d3a23dadeb83e928e14906cbd763e173018 http://pkgs.fedoraproject.org/cgit/qtsingleapplication.git/commit/?id=bbfb699b6693fc25e127aafe790185d5e010f0a6
(In reply to Rex Dieter from comment #11) > Re: comment #7 > Checking Qt versions in prf's should not be a problem either, it's (more) > upstreamable. Well, that would not be fully avoidable, at least not while we've to ship for more than one qt major version, meaning currently for both qt4 and qt5.
Package qtlockedfile-2.4-18.20150629git5a07df5.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 qtlockedfile-2.4-18.20150629git5a07df5.fc22' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-12249/qtlockedfile-2.4-18.20150629git5a07df5.fc22 then log in and leave karma (feedback).
qtlockedfile-2.4-18.20150629git5a07df5.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
qtlockedfile-2.4-18.20150629git5a07df5.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.