bazel icon indicating copy to clipboard operation
bazel copied to clipboard

bazel-5.3.0-installer-linux-x86_64.sh: 5: Syntax error: word unexpected

Open cartheur opened this issue 3 years ago • 2 comments

Description of the bug:

Starting with release 5.3.0, a syntax error has appeared in the installation script that causes containers where bazel is being installed to fail. When inspecting the file, it appears that there is binary code inside the shell script.

What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.

curl -LlSsk https://github.com/bazelbuild/bazel/releases/download/5.3.0/bazel-5.3.0-installer-linux-x86_64.sh

Which operating system are you running Bazel on?

Debian 11

What is the output of bazel info release?

release 5.3.0

If bazel info release returns development version or (@non-git), tell us how you built Bazel.

No response

What's the output of git remote get-url origin; git rev-parse master; git rev-parse HEAD ?

No response

Have you found anything relevant by searching the web?

No response

Any other information, logs, or outputs that you want to share?

No response

cartheur avatar Sep 02 '22 09:09 cartheur

Hello @cartheur, Could you please provide the correct order of steps to reproduce the above error. Thanks!

sgowroji avatar Sep 02 '22 10:09 sgowroji

@sgowroji It is simply a curl command to download and install for linux x86_64. When running the shell script, even with just curl -fsSLk https://github.com/bazelbuild/bazel/releases/download/5.3.0/bazel-5.3.0-installer-linux-x86_64.sh gives the error .../bazel-5.3.0-installer-linux-x86_64.sh: 5: Syntax error: word unexpected.

cartheur avatar Sep 02 '22 10:09 cartheur

Thank you for contributing to the Bazel repository! This issue has been marked as stale since it has not had any activity in the last 1+ years. It will be closed in the next 90 days unless any other activity occurs or one of the following labels is added: "not stale", "awaiting-bazeler". Please reach out to the triage team (@bazelbuild/triage) if you think this issue is still relevant or you are interested in getting the issue resolved.

github-actions[bot] avatar Nov 25 '23 01:11 github-actions[bot]

This issue has been automatically closed due to inactivity. If you're still interested in pursuing this, please post @bazelbuild/triage in a comment here and we'll take a look. Thanks!

github-actions[bot] avatar Feb 24 '24 01:02 github-actions[bot]