-
-
Notifications
You must be signed in to change notification settings - Fork 528
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
manually removing executable bits doesn't work #6625
Comments
comment:1
Attachment: scripts_6625_no_x_bit.patch.gz The |
Attachment: trac_6625-no-x-bit.patch.gz rebased against Sage 4.3.1.rc1; apply to SAGE_LOCAL/bin |
Author: Willem Jan Palenstijn |
Reviewer: Minh Van Nguyen |
comment:2
The attachment scripts_6625_no_x_bit.patch fails to apply against Sage 4.3.1.rc1:
The failure results from #7975, which removes dsage from Sage and the patches on #7975 have been merged in Sage 4.3.1.rc1. The guilty line from scripts_6625_no_x_bit.patch is:
Essentially the patch looks good. I have rebased it against Sage 4.3.1.rc1, so only my rebase trac_6625-no-x-bit.patch needs reviewing. |
comment:3
Thanks. The rebase looks good to me. |
Merged: sage-4.3.2.alpha0 |
comment:4
Merged trac_6625-no-x-bit.patch in the script repository. |
This is a follow up to #3687. Apparently, the issue of executable bits pop up again after they had been manually removed. That is, manually remove the executable bits of sage-banner, sage-gdb-commands, sage-maxima.lisp, and sage-verify-pyc. Then create a source distribution and you see those executable bits restored:
Somewhere a script called by the command
is restoring those executable bits.
Component: misc
Author: Willem Jan Palenstijn
Reviewer: Minh Van Nguyen
Merged: sage-4.3.2.alpha0
Issue created by migration from https://trac.sagemath.org/ticket/6625
The text was updated successfully, but these errors were encountered: