trivial problems in the sage_scripts spkg #3687
Description
Below is a list trivial problems in the sage_scripts spkg that were found by Debian's automatic package quality checking tools:
# Scripts missing #!/bin/sh lines in sage_scripts-3.0.5.spkg:
sage-pull
sage-push
sage-mirror
sage-mirror-darcs-scripts
sage-osx-open
# Scripts missing #!/usr/bin/python lines in sage_scripts-3.0.5.dpkg:
sage-startuptime.py
sage-gdb-pythonstartup
dsage_setup.py
# Files unnecessarily marked as executable in sage_scripts-3.0.5.spkg
sage-banner
sage-gdb-commands
sage-maxima.lisp
# Scripts that use #!sage or #!sage.bin as their interpreter in sage_scripts-3.0.5.spkg
# You want to use #!/usr/bin/env sage
sage-ipython
sage-location
sage-preparse
sage-run
sage-run2
# Weird files in sage_scripts-3.0.5.spkg marked executable
sage-README-osx.txt (duplicate of file of the same name in the root of the sage distribution)
sage-verify-pyc (this one is just weird)
Component: packages: standard
Author: Tim Abbott
Reviewer: Adam Webb
Merged: Sage 4.1.1.alpha1
Issue created by migration from https://trac.sagemath.org/ticket/3687