https://bugzilla.redhat.com/show_bug.cgi?id=781823 --- Comment #11 from Mario Blättermann <mario.blaettermann@xxxxxxxxx> --- All Python scripts in %{python_sitelib} don't need neither a shebang nor to be executable. You will have to patch them and inform upstream people about this problem. There remains the following issue: easyplay.src: E: specfile-error sh: line 0: fg: no job control This error occurred when rpmlint used rpm to query the specfile. The error is output by rpm and the message should contain more information. #!/bin/sh python3 /usr/lib/python2.7/site-packages/easyplay/easyplay Is it really intended that Python v3 has to run a script which resides in the Python2 module folder? The python3-libs package creates a folder /usr/lib/python3.2/site-packages/ or /usr/lib64/python3.2/site-packages/... ... Stop - just found the possible solution. You have used the macro %{python_sitelib}, but for Pathon3 packages it has to be %{python3_sitelib}. This could cause the issue with running a script in the "old" Python2 folder with Python3. Just test it again. Maybe you can omit the runtime script in /usr/bin. I propose to patch a shebang (#!/usr/bin/env python3) into %{python3_sitelib}/easyplay/easyplay and link it to /usr/bin. This could avoid even more trouble. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review