Skip to content

[Release][Packaging] 20.0.0 RC0 APT/Yum repositories are broken #46083

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.

Sign up for GitHub

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

Jump to bottom
Closed
kou opened this issue Apr 10, 2025 · 5 comments
Closed

[Release][Packaging] 20.0.0 RC0 APT/Yum repositories are broken #46083

kou opened this issue Apr 10, 2025 · 5 comments
Assignees
@kou
Labels
Component: Packaging Component: Release Priority: Blocker Marks a blocker for the release Type: bug
Milestone
20.0.0

Comments

@kou
Copy link
Member

kou commented Apr 10, 2025

Describe the bug, including details regarding any error messages, version, and platform.

For example:

APT (ubuntu-latest)

   Retry: apt install -y -V --no-install-recommends libarrow-dev=20.0.0-1
  
  WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
  
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Package libarrow-dev is not available, but is referred to by another package.
  This may mean that the package is missing, has been obsoleted, or
  is only available from another source
  
  E: Version '20.0.0-1' for 'libarrow-dev' was not found

This happened because existing files in https://repository.apache.org/content/repositories/staging/org/apache/arrow/ such as https://repository.apache.org/content/repositories/staging/org/apache/arrow/ubuntu/apache-arrow-apt-source-latest-noble.deb weren't updated by Maven repository's "Close" operation. (Note that new files were appeared in https://repository.apache.org/content/repositories/staging/org/apache/arrow/ .)

Component(s)

Release, Packaging
@kou kou added the Type: bug label Apr 10, 2025
@kou
Copy link
Member Author

kou commented Apr 10, 2025

I'm asking about recommended APT/Yum repositories on [email protected]: https://lists.apache.org/thread/d76glb6d9ny6d6g8bjdb80gwndprtz4r

@kou
Copy link
Member Author

kou commented Apr 10, 2025

We may need to keep using Artifactory...

@assignUser
Copy link
Member

Thanks @kou I'll keep an eye on the list and answer any inquiries.

@kou
Copy link
Member Author

kou commented Apr 11, 2025

We haven't received any answer on the thread but let's use Artifactory for 20.0.0.

I'll update our binary update scripts.

@kou kou mentioned this issue Apr 11, 2025
Closed
kou added a commit to kou/arrow-site that referenced this issue Apr 11, 2025
@kou
Revert "Use repo1.maven.org not apache.jfrog.io in the install page (a…
633a620 
…pache#637)"

This reverts commit ad53579.

It seems that we can't use repo1.maven.org for APT/Yum repositories.
See also: apache/arrow#46083
@kou kou mentioned this issue Apr 11, 2025
Open
kou added a commit to kou/arrow that referenced this issue Apr 11, 2025
@kou
apacheGH-46083: [Release][Packages] Use Artifactory for APT/Yum repos…
71f5bf4 
…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 github-actions bot mentioned this issue Apr 11, 2025
Merged
assignUser added a commit that referenced this issue Apr 14, 2025
@kou @assignUser
GH-46083: [Release][Packages] Use Artifactory for APT/Yum repositorie…
72c246a 
…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]>
@assignUser assignUser added this to the 20.0.0 milestone Apr 14, 2025
@assignUser
Copy link
Member

Issue resolved by pull request 46108
#46108

@assignUser assignUser added the Priority: Blocker Marks a blocker for the release label Apr 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kou kou

Labels
Component: Packaging Component: Release Priority: Blocker Marks a blocker for the release Type: bug
Projects
None yet
Milestone
20.0.0
Development

No branches or pull requests
2 participants
@kou @assignUser