-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
GH-33626: [Packaging][RPM] Don't remove metadata for non-target arch #33672
Conversation
… arch ADBC reuses dev/release/05-binary-upload.sh for its RPM packages. ADBC only provides x86_64 packages. ADBC doesn't provide aarch64 packages for now. In this situation, ADBC release deletes Yum repository metadata for aarch64 unexpectedly. dev/release/05-binary-upload.sh should not touch Yum repository metadata for aarch64 in ADBC release.
@github-actions crossbow submit almalinux-8-arm64 |
Revision: 695eca6 Submitted crossbow builds: ursacomputing/crossbow @ actions-2cf528b305
|
+1 |
Benchmark runs are scheduled for baseline = 988be40 and contender = 4bb7d94. 4bb7d94 is a master commit associated with this PR. Results will be available as each benchmark for each run completes. |
['Python', 'R'] benchmarks have high level of regressions. |
Fix datafusion-contrib#47. It's for the next release. We need apache/arrow#33672.
Fix #47. It's for the next release. We need apache/arrow#33672.
Which issue does this PR close?
Closes #33626
Rationale for this change
ADBC reuses dev/release/05-binary-upload.sh for its RPM packages. ADBC only provides x86_64 packages. ADBC doesn't provide aarch64 packages for now.
In this situation, ADBC release deletes Yum repository metadata for aarch64 unexpectedly. dev/release/05-binary-upload.sh should not touch Yum repository metadata for aarch64 in ADBC release.
What changes are included in this PR?
Copy Yum repository metadata for non-target architecture as-is.
Are these changes tested?
Yes.
Are there any user-facing changes?
No.