GH-46083: [Release][Packages] Use Artifactory for APT/Yum repositories again #46108
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…itories again It seems that ASF's Maven repository (Nexus 2) isn't suitable for APT/Yum repositories because it can't update existing files. We need to update existing files for APT/Yum repositories' metadata.
|
|
github-actions
bot
added
Component: Ruby
awaiting committer review
Member
Author
|
I'm trying this with 20.0.0 RC0 artifacts on local... |
Member
Author
|
Uploaded to https://packages.apache.org/ui/native/arrow/*-rc/ . I'll check them later. |
assignUser
reviewed
Apr 11, 2025
Member
|
I am testing this in #46076 and getting errors because the repo files still point to repo1.a.o but I guess that's expected because we have to regenerate the list? |
assignUser
reviewed
Apr 11, 2025
Member
|
We should also revert #46082 |
Co-authored-by: Jacob Wujciak-Jens <[email protected]>
Member
Author
Right. We need to rebuild I'll test the current verify scripts with 20.0.0 RC0 packages before we merge this: diff --git a/dev/release/verify-apt.sh b/dev/release/verify-apt.sh
index 02296c2079..90c171e906 100755
--- a/dev/release/verify-apt.sh
+++ b/dev/release/verify-apt.sh
@@ -131,7 +131,7 @@ else
rc)
sed \
-i"" \
- -e "s,^URIs: \\(.*\\)/,URIs: \\1-${suffix}/,g" \
+ -e "s,^URIs: https://repo1.maven.org/maven2/org/apache/arrow/${distribution},URIs: ${artifactory_base_url}/,g" \
/etc/apt/sources.list.d/apache-arrow.sources
;;
esacdiff --git a/dev/release/verify-yum.sh b/dev/release/verify-yum.sh
index 8691e538ec..d1d4b25574 100755
--- a/dev/release/verify-yum.sh
+++ b/dev/release/verify-yum.sh
@@ -179,6 +179,7 @@ else
suffix=${TYPE%-release}
sed \
-i"" \
+ -e "s,https://repo1.maven.org/maven2/org/apache/arrow,${artifactory_base_url},g" \
-e "s,/almalinux/,/almalinux-${suffix}/,g" \
-e "s,/centos/,/centos-${suffix}/,g" \
-e "s,/amazon-linux/,/amazon-linux-${suffix}/,g" \ |
Member
Author
Member
Author
|
Member
Author
|
It worked. This is ready. |
|
After merging your PR, Conbench analyzed the 4 benchmarking runs that have been run so far on merge-commit 72c246a. There were no benchmark performance regressions. 🎉 The full Conbench report has more details. It also includes information about 78 possible false positives for unstable benchmarks that are known to sometimes produce them. |
assignUser
added a commit
that referenced
this pull request
Apr 15, 2025
…s again (#46108) ### Rationale for this change It seems that ASF's Maven repository (Nexus 2) isn't suitable for APT/Yum repositories because it can't update existing files. We need to update existing files for APT/Yum repositories' metadata. Let's keep using Artifactory for 20.0.0. We may revisit this after 20.0.0 release. ### What changes are included in this PR? * Use Artifatory again. * Use packages.apache.org not apache.jfrog.io. ### Are these changes tested? Yes. ### Are there any user-facing changes? No. (Keep the existing URL.) * GitHub Issue: #46083 Lead-authored-by: Sutou Kouhei <[email protected]> Co-authored-by: Sutou Kouhei <[email protected]> Co-authored-by: Jacob Wujciak-Jens <[email protected]> Signed-off-by: Jacob Wujciak-Jens <[email protected]>
zanmato1984
pushed a commit
to zanmato1984/arrow
that referenced
this pull request
Apr 15, 2025
…itories again (apache#46108) ### Rationale for this change It seems that ASF's Maven repository (Nexus 2) isn't suitable for APT/Yum repositories because it can't update existing files. We need to update existing files for APT/Yum repositories' metadata. Let's keep using Artifactory for 20.0.0. We may revisit this after 20.0.0 release. ### What changes are included in this PR? * Use Artifatory again. * Use packages.apache.org not apache.jfrog.io. ### Are these changes tested? Yes. ### Are there any user-facing changes? No. (Keep the existing URL.) * GitHub Issue: apache#46083 Lead-authored-by: Sutou Kouhei <[email protected]> Co-authored-by: Sutou Kouhei <[email protected]> Co-authored-by: Jacob Wujciak-Jens <[email protected]> Signed-off-by: Jacob Wujciak-Jens <[email protected]>
kou
added a commit
to kou/arrow-adbc
that referenced
this pull request
Apr 29, 2025
arrow-apt-source and arrow-release changed to use packages.apache.org from apache.jfrog.io in apache/arrow#46108 . (Note that packages.apache.org is an alias of apache.jfrog.io.) We need to do the same change to pass CI. Closes apache#2754
kou
added a commit
to kou/arrow-adbc
that referenced
this pull request
Apr 29, 2025
arrow-apt-source and arrow-release changed to use packages.apache.org from apache.jfrog.io in apache/arrow#46108 . (Note that packages.apache.org is an alias of apache.jfrog.io.) We need to do the same change to pass CI. Closes apache#2754
lidavidm
pushed a commit
to apache/arrow-adbc
that referenced
this pull request
Apr 29, 2025
…2756) arrow-apt-source and arrow-release changed to use packages.apache.org from apache.jfrog.io in apache/arrow#46108 . (Note that packages.apache.org is an alias of apache.jfrog.io.) We need to do the same change to pass CI. Fixes #2757.
colin-rogers-dbt
pushed a commit
to dbt-labs/arrow-adbc
that referenced
this pull request
Jun 10, 2025
…pache#2756) arrow-apt-source and arrow-release changed to use packages.apache.org from apache.jfrog.io in apache/arrow#46108 . (Note that packages.apache.org is an alias of apache.jfrog.io.) We need to do the same change to pass CI. Fixes apache#2757.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Rationale for this change
It seems that ASF's Maven repository (Nexus 2) isn't suitable for APT/Yum repositories because it can't update existing files. We need to update existing files for APT/Yum repositories' metadata.
Let's keep using Artifactory for 20.0.0. We may revisit this after 20.0.0 release.
What changes are included in this PR?
Are these changes tested?
Yes.
Are there any user-facing changes?
No. (Keep the existing URL.)