Steps to reproduce the behavior
Attempt to install JRuby of 1.7, 9.0, 9.1 or 9.2 series.
Expected vs. actual behavior
Expected
Installation proceeds.
Actual
URL for install_package points to an S3 bucket (e.g., for JRuby 9.2.8.0 links to https://s3.amazonaws.com/jruby.org/downloads/9.2.8.0/jruby-bin-9.2.8.0.tar.gz) that returns an error with HTTP 403 code:
<Error><Code>AllAccessDisabled</Code><Message>All access to this object has been disabled</Message><RequestId>N7BQA4AETM296AK8</RequestId><HostId>63mGG6CIDbWE1VerWYOVLyBg0xLF5DkhD9dIHB52pFF+7mNsJzactGlSJdmBnOIjkVG7zn47PZU=</HostId></Error>
(Partial) workaround
The Maven Central has many but not all of the releases. For aforementioned 9.2.8.0 the URL would be https://repo1.maven.org/maven2/org/jruby/jruby-dist/9.2.8.0/jruby-dist-9.2.8.0-bin.tar.gz. So an override with RUBY_BUILD_MIRROR_PACKAGE_URL=https://repo1.maven.org/maven2/org/jruby/jruby-dist/9.2.8.0/jruby-dist-9.2.8.0-bin.tar.gz does work.
Steps to reproduce the behavior
Attempt to install JRuby of 1.7, 9.0, 9.1 or 9.2 series.
Expected vs. actual behavior
Expected
Installation proceeds.
Actual
URL for
install_packagepoints to an S3 bucket (e.g., for JRuby 9.2.8.0 links to https://s3.amazonaws.com/jruby.org/downloads/9.2.8.0/jruby-bin-9.2.8.0.tar.gz) that returns an error with HTTP 403 code:(Partial) workaround
The Maven Central has many but not all of the releases. For aforementioned 9.2.8.0 the URL would be https://repo1.maven.org/maven2/org/jruby/jruby-dist/9.2.8.0/jruby-dist-9.2.8.0-bin.tar.gz. So an override with
RUBY_BUILD_MIRROR_PACKAGE_URL=https://repo1.maven.org/maven2/org/jruby/jruby-dist/9.2.8.0/jruby-dist-9.2.8.0-bin.tar.gzdoes work.