-
Notifications
You must be signed in to change notification settings - Fork 293
incorrect executable bit on various files #418
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi Paul |
I pushed the changes to the internal bit bucket,
|
The changes should be deployed , can you please check and confirm ? |
Thanks for that, most of them are fixed but there is
one more executable file that should not be executable:
requirements.txt
…--
bye,
pabs
https://bonedaddy.net/pabs3/
|
I pushed this as well Can you please let me know what is the issue if the executable is set for non executable files ? For your info |
In summary it is a minor issue that doesn't have any major effect.
On Linux a file that is executable but does not have an execution type
marker (the shebang, like #!/bin/sh), if it is attempted to execute it,
the system will be execute it using the system shell, which is
obviously incorrect and will result in errors for Python code etc. Of
course it will be rare that someone will try to execute these files,
but it could happen, which is why the lintian tool for static analysis
of Debian packages warns when files are marked as executable but are
not binaries or scripts. When there are lots of incorrectly executable
files, it means a lot of noise in the lintian output.
https://lintian.debian.org/tags/executable-not-elf-or-script
On Windows it seems like the default is to not mark the files as
executable, and it seems you have to explicitly enable that:
https://stackoverflow.com/questions/21691202/how-to-create-file-execute-mode-permissions-in-git-on-windows
…--
bye,
pabs
https://bonedaddy.net/pabs3/
|
@adizohar looks like some more instances of this have been introduced in the examples directory. I think it would be a good idea for you to add a GitHub Actions check to give errors when more incorrect executable bits are added.
|
Those will be fixed next week |
@adizohar some of the issues got fixed, thanks! there are now only five issues left!
|
@adizohar this issue got fully fixed, thanks! |
Many of the files (including PNG images) in the git repository incorrectly have the execute bit set even though they are clearly not scripts with a shebang or executables.
This command can be used to fix all of the files:
This command can be used to print details of the files:
The text was updated successfully, but these errors were encountered: