#6625: manually removing executable bits doesn't work
--------------------+-------------------------------------------------------
Reporter: mvngu | Owner: cwitty
Type: defect | Status: new
Priority: minor | Milestone: sage-4.1.1
Component: misc | Keywords:
Reviewer: | Author:
Merged: |
--------------------+-------------------------------------------------------
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:
{{{
[mv...@sage bin]$ pwd
/home/mvngu/release/sage-4.1.1.alpha1/local/bin
[mv...@sage bin]$ hg st
M sage-README-osx.txt
M sage-banner
M sage-gdb-commands
M sage-maxima.lisp
M sage-verify-pyc
}}}
Somewhere a script called by the command
{{{
sage -sdist <version-number>
}}}
is restoring those executable bits.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/6625>
Sage <http://sagemath.org/>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en
-~----------~----~----~----~------~----~------~--~---
