-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Release] R libarrow binaries have the wrong version number #32627
Comments
Jacob Wujciak / @assignUser: |
Kouhei Sutou / @kou: https://apache.jfrog.io/ui/native/arrow/r/9.0.0/libarrow/bin/ubuntu-22.04/ We should remove ".20220729"' from ".asc" and ".sha512", right? |
Kouhei Sutou / @kou: |
Kouhei Sutou / @kou: It seems that built packages for 9.0.0-rc2 already have ".20220729". Is it intentional? I think that we should use "9.0.0" not "9.0.0.20220719" here. |
Neal Richardson / @nealrichardson: |
Jacob Wujciak / @assignUser: |
Kouhei Sutou / @kou: Can we use |
Jacob Wujciak / @assignUser: |
Kouhei Sutou / @kou:
This will generate "r-pkg_*.10.0.0.zip" not "r-pkg_*10.0.0.202210XX.zip" for "10.0.0-rc1" because "10.0.0-rc1" doesn't have ".devXXX". |
Kouhei Sutou / @kou: |
The libarrow binaries that are uploaded during the release process have the wrong version number. This is an issue with the submit binaries script/r-binary-packages job. The arrow version should be picked up by the job even if not passed explicitly as a custom param.
Reporter: Jacob Wujciak / @assignUser
Assignee: Kouhei Sutou / @kou
PRs and other links:
Note: This issue was originally created as ARROW-17353. Please see the migration documentation for further details.
The text was updated successfully, but these errors were encountered: