Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Still some wrong permissions vs. shebang

See original GitHub issue

Describe the bug #461 is still not totally resolved. With the latest release (4.5.6) these files are still broken:

[   18s] python2-pyfakefs.noarch: W: non-executable-script /usr/lib/python2.7/site-packages/pyfakefs/tests/all_tests.py 644 /usr/bin/env python
[   18s] python2-pyfakefs.noarch: W: non-executable-script /usr/lib/python2.7/site-packages/pyfakefs/tests/all_tests_without_extra_packages.py 644 /usr/bin/env python
[   18s] python2-pyfakefs.noarch: W: non-executable-script /usr/lib/python2.7/site-packages/pyfakefs/tests/example_test.py 644 /usr/bin/env python
[   18s] python3-pyfakefs.noarch: W: non-executable-script /usr/lib/python3.6/site-packages/pyfakefs/tests/all_tests.py 644 /usr/bin/env python
[   18s] python3-pyfakefs.noarch: W: non-executable-script /usr/lib/python3.6/site-packages/pyfakefs/tests/all_tests_without_extra_packages.py 644 /usr/bin/env python
[   18s] python3-pyfakefs.noarch: W: non-executable-script /usr/lib/python3.6/site-packages/pyfakefs/tests/example_test.py 644 /usr/bin/env python
[   18s] This text file contains a shebang or is located in a path dedicated for
[   18s] executables, but lacks the executable bits and cannot thus be executed.  If
[   18s] the file is meant to be an executable script, add the executable bits,
[   18s] otherwise remove the shebang or move the file elsewhere.

How To Reproduce Check shebang lines and/or executable bits on those files.

Your enviroment Does not matter.

Issue Analytics

State:
Created 5 years ago
Comments:17 (17 by maintainers)

Top GitHub Comments

1reaction

kbabiochcommented, Apr 22, 2019

@mrbean-bremen This problem is not related to yours. It is an RPM packaging issue. I will address it, once I touch the package again. Thank you once again for all the love you put into this 😉.

0reactions

mrbean-bremencommented, Apr 18, 2019

Ok, just noticed that the warning for the SLE_12 build is not the original problem, but another one:

python-pyfakefs.src:63: W: files-attr-not-set
python-pyfakefs.src:64: W: files-attr-not-set
python-pyfakefs.src:65: W: files-attr-not-set
A file or a directory entry in a %files section does not have attributes set
which may result in unexpected file permissions and thus security issues in
the resulting binary package depending on the build environment and rpmbuild
version (typically &lt; 4.4).  Add default attributes using %defattr before it in
the %files section, or use per entry %attr's.

I think we can ignore this, as this seems to be specific to this version and not a regression. @kbabioch - please reopen if you think this can/shall be handled.