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
Clean up permissions on non-scripts? #4949
Comments
samth
added a commit
to racket/eopl
that referenced
this issue
Mar 8, 2024
Related to racket/racket#4949.
I dealt with the ones in |
Sam Tobin-Hochstadt ***@***.***> writes:
I dealt with the ones in `eopl` (although the `-exec` didn't work for me).
--
Reply to this email directly or view it on GitHub:
#4949 (comment)
You are receiving this because you authored the thread.
Message ID: ***@***.***>
Is there a corresponding commit in the main racket repo? Probably not
worth deep investigation, but I could well have used GNU specific find
options.
d
|
|
shuhung ***@***.***> writes:
> bremner commented Mar 12, 2024 via email:
> Is there a corresponding commit in the main racket repo? Probably not worth deep investigation, but I could well have used GNU specific find options. d
racket/eopl@d313612
Yes, I was wondering about racket/racket, but I guess the eopl source is
not actually tracked there.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What version of Racket are you using?
8.12[cs]
What program did you run?
While building Debian packages for 8.12, I noticed many warnings about executable files that are not scripts.
You can find them with something like
find . -perm /u+x -type f -exec awk 'NR==1 && !/#!/ {print FILENAME; exit 0}' {} ;
Many of the results are from eopl
What should have happened?
I guess these files will generate warnings for other packagers as well, so perhaps they should be fixed in the racket source?
The text was updated successfully, but these errors were encountered: