kou opened a new pull request, #45964: URL: https://github.com/apache/arrow/pull/45964
This is based on #45963. So we can't merge this. ### Rationale for this change We want to stop using apache.jfrog.io. See also: #40760 We can use https://repo1.maven.org/maven2/org/apache/arrow or https://github.com/apache/arrow/releases as alternative. ### What changes are included in this PR? This uses https://github.com/apache/arrow/releases as alternative. If we use GitHub Release, we can manage it easier than https://repo1.maven.org/maven2/org/apache/arrow . For example, we'll be able to automate it by GitHub Actions. But GitHub Release doesn't support directory structure. So we need to put all artifacts to https://github.com/apache/arrow/releases/download/X.Y.Z/ . We can't create any directory. For example: apache.jfrog.io and repo1.maven.org: ```text libarrow/bin/darwin-arm64-openssl-1.1/arrow-X.Y.Z.zip libarrow/bin/darwin-arm64-openssl-3.0/arrow-X.Y.Z.zip libarrow/bin/darwin-x86_64-openssl-1.1/arrow-X.Y.Z.zip libarrow/bin/darwin-x86_64-openssl-3.0/arrow-X.Y.Z.zip libarrow/bin/linux-openssl-1.0/arrow-X.Y.Z.zip libarrow/bin/linux-openssl-1.1/arrow-X.Y.Z.zip libarrow/bin/linux-openssl-3.0/arrow-X.Y.Z.zip libarrow/bin/windows/arrow-X.Y.Z.zip ``` GitHub Actions: ```text r-lib__libarrow__bin__darwin-arm64-openssl-1.1__arrow-X.Y.Z.zip r-lib__libarrow__bin__darwin-arm64-openssl-3.0__arrow-X.Y.Z.zip r-lib__libarrow__bin__darwin-x86_64-openssl-1.1__arrow-X.Y.Z.zip r-lib__libarrow__bin__darwin-x86_64-openssl-3.0__arrow-X.Y.Z.zip r-lib__libarrow__bin__linux-openssl-1.0__arrow-X.Y.Z.zip r-lib__libarrow__bin__linux-openssl-1.1__arrow-X.Y.Z.zip r-lib__libarrow__bin__linux-openssl-3.0__arrow-X.Y.Z.zip r-lib__libarrow__bin__windows__arrow-X.Y.Z.zip ``` ### Are these changes tested? No. ### Are there any user-facing changes? Yes. Custom `arrow_repo` doesn't work because URL is changed. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
