Skip to content

manually removing executable bits doesn't work #6625

@sagetrac-mvngu

Description

@sagetrac-mvngu

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:

[mvngu@sage bin]$ pwd
/home/mvngu/release/sage-4.1.1.alpha1/local/bin
[mvngu@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.

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

Metadata

Metadata

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions