In %install, after invocation of %scl_install, current directory is %{bulidroot}/%{scl_prefix} which is not common. I think such macro should not alter the current directory. Issue. %prep generate_some_file >foo %install install foo %{buildroot}... The install command fails because "foo" is not found in the current directory. The current workaound is to install files (ex: the "enable" script) before %scl_install, which doesn't seems correct because - before %scl_install the SCL tree doesn't exists yet (requiring to create the %{buildroot}%{_scl_scripts} dir first) - %scl_install is designed to create the SCL tree - after %scl_install, the SCL tree exists, and so, seems the right place to install additional files.
*** Bug 1017085 has been marked as a duplicate of this bug. ***
scl-utils-20131015-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/scl-utils-20131015-1.fc20
scl-utils-20131015-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/scl-utils-20131015-1.fc19
The "updated update" is here: https://admin.fedoraproject.org/updates/scl-utils-20131016-1.fc19
While testing on real-life collections I found one unrelated issue in scl-utils, a new update has been issued: https://admin.fedoraproject.org/updates/scl-utils-20131017-1.fc19
Package scl-utils-20131017-1.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing scl-utils-20131017-1.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-19205/scl-utils-20131017-1.fc20 then log in and leave karma (feedback).
scl-utils-20131017-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
scl-utils-20131017-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.