kou opened a new issue, #37350: URL: https://github.com/apache/arrow/issues/37350
### Describe the enhancement requested ### Background We're using a "General" type Artifactory repository to provide APT/Yum repositories. We generate metadata for APT/Yum repositories' by ourself. Recently, we sometimes get 403 Forbidden errors when we use APT repository in the "general" type Artifactory repository. See also #35292. INFRA asked JFrog this. See also https://issues.apache.org/jira/browse/INFRA-24569 . JFrog recommended to migrate to a "Debian" type Artifactory repository. INFRA (not JFrog) also said that "Generic" type Artifactory repository isn't suitable for APT repository. ### Compatibility I already created https://apache.jfrog.io/ui/repos/tree/General/arrow-debian?projectKey=arrow and https://apache.jfrog.io/ui/repos/tree/General/arrow-rpm?projectKey=arrow repositories but I don't do anything yet. If we use "Debian"/"RPM" type repositories instead of the current "General" type repository, users need to change their configuration. I want to avoid it as much as possible. We're providing `apache-arrow-apt-source` package for APT repository and `apache-arrow-source` package for Yum repository. I hope that we can implement a safe migration (users don't need to change anything. users just need to run `apt update`/`dnf update` as usual.) by using them. ### See also * Debian type repository's document: https://jfrog.com/help/r/jfrog-artifactory-documentation/debian-repositories * RPM type repository's document: https://jfrog.com/help/r/jfrog-artifactory-documentation/rpm-repositories ### Component(s) Packaging, Release -- 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]
