diff options
author | Greg Price <gnprice@gmail.com> | 2019-08-21 04:53:59 (GMT) |
---|---|---|
committer | Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com> | 2019-08-21 04:53:59 (GMT) |
commit | 9ece4a5057d52c42a8a064a6c0c7f923267fb3db (patch) | |
tree | b5966d4146b545743bbe993a6894b197cd5f3d78 /.azure-pipelines/posix-deps-apt.sh | |
parent | 5b95a1507e349da5adae6d2ab57deac3bdd12f15 (diff) | |
download | cpython-9ece4a5057d52c42a8a064a6c0c7f923267fb3db.zip cpython-9ece4a5057d52c42a8a064a6c0c7f923267fb3db.tar.gz cpython-9ece4a5057d52c42a8a064a6c0c7f923267fb3db.tar.bz2 |
Unmark files as executable that can't actually be executed. (GH-15353)
There are plenty of legitimate scripts in the tree that begin with a
`#!`, but also a few that seem to be marked executable by mistake.
Found them with this command -- it gets executable files known to Git,
filters to the ones that don't start with a `#!`, and then unmarks
them as executable:
$ git ls-files --stage \
| perl -lane 'print $F[3] if (!/^100644/)' \
| while read f; do
head -c2 "$f" | grep -qxF '#!' \
|| chmod a-x "$f"; \
done
Looking at the list by hand confirms that we didn't sweep up any
files that should have the executable bit after all. In particular
* The `.psd` files are images from Photoshop.
* The `.bat` files sure look like things that can be run.
But we have lots of other `.bat` files, and they don't have
this bit set, so it must not be needed for them.
Automerge-Triggered-By: @benjaminp
Diffstat (limited to '.azure-pipelines/posix-deps-apt.sh')
-rwxr-xr-x | .azure-pipelines/posix-deps-apt.sh | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/.azure-pipelines/posix-deps-apt.sh b/.azure-pipelines/posix-deps-apt.sh index 4f48990..e0f4ca5 100755 --- a/.azure-pipelines/posix-deps-apt.sh +++ b/.azure-pipelines/posix-deps-apt.sh @@ -1,3 +1,4 @@ +#!/bin/sh apt-get update apt-get -yq install \ |