[jira] [Updated] (CASSANDRA-17748) Move deb/rpm repositories from dist/downloads .a.o to apache.jfrog.io
[ https://issues.apache.org/jira/browse/CASSANDRA-17748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-17748: --- Fix Version/s: 3.11.14 4.0.6 4.1 4.2 (was: 4.x) (was: 3.11.x) (was: 4.0.x) (was: 4.1.x) Source Control Link: https://github.com/apache/cassandra-website/commit/eaa6b3e7ab510547346d5c5584977962e0b9549a https://github.com/apache/cassandra-builds/commit/05a381784449faaa455e481ba8412a87f48dd872 https://github.com/apache/cassandra/commit/b492341eb5789889e56c55bfef6f Resolution: Fixed Status: Resolved (was: Ready to Commit) > Move deb/rpm repositories from dist/downloads .a.o to apache.jfrog.io > - > > Key: CASSANDRA-17748 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17748 > Project: Cassandra > Issue Type: Task > Components: Packaging >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Urgent > Labels: pull-request-available > Fix For: 3.11.14, 4.0.6, 4.1, 4.2 > > Time Spent: 20m > Remaining Estimate: 0h > > Move our official debian and redhat repositories from downloads.apache.org to > Apache's JFrog Artifactory server at apache.jfrog.io > That is, the following URLs would be moved from > ``` > https://downloads.apache.org/cassandra/debian/ > https://downloads.apache.org/cassandra/redhat/ > ``` > to > ``` > https://apache.jfrog.io/artifactory/cassandra-deb/ > https://apache.jfrog.io/artifactory/cassandra-rpm/ > ``` > The rationale to do this is to avoid the strict opinionated checksum and > signature requirements on downloads.a.o (dist.a.o), as the debian and redhat > repositories have their own system for integrity and signing (which we > already do). > Furthermore, as these repositories and their binaries are "convenience > binaries" and not the official Cassandra source binaries, they do not need to > be on downloads.a.o and can be served from apache.jfrog.io. This is similar > to maven binaries (and docker images). Apache Arrow is already taking this > approach: https://arrow.apache.org/install/ > An advantage to using apache.frog.io is that these repositories maintain all > past patch versions on each repo series (major/minor). This has been > requested by users a number of times, for the sake of rolling back to a > previous patch version. downloads.a.o can only contain the latest version. > This will BREAK everyone's existing > `/etc/apt/sources.list.d/cassandra.sources.list` and > `/etc/yum.repos.d/cassandra.repo` files. Folk will need to update these files > to point to the new repo URLs. This would require an announcement to both > users@ and dev@. I do not know how we can avoid this breakage. We could put > in a simple README.md in the original URL locations explaining the breakage > and how to fix. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17748) Move deb/rpm repositories from dist/downloads .a.o to apache.jfrog.io
[ https://issues.apache.org/jira/browse/CASSANDRA-17748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-17748: --- Status: Ready to Commit (was: Review In Progress) > Move deb/rpm repositories from dist/downloads .a.o to apache.jfrog.io > - > > Key: CASSANDRA-17748 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17748 > Project: Cassandra > Issue Type: Task > Components: Packaging >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Urgent > Labels: pull-request-available > Fix For: 3.11.x, 4.0.x, 4.1.x, 4.x > > > Move our official debian and redhat repositories from downloads.apache.org to > Apache's JFrog Artifactory server at apache.jfrog.io > That is, the following URLs would be moved from > ``` > https://downloads.apache.org/cassandra/debian/ > https://downloads.apache.org/cassandra/redhat/ > ``` > to > ``` > https://apache.jfrog.io/artifactory/cassandra-deb/ > https://apache.jfrog.io/artifactory/cassandra-rpm/ > ``` > The rationale to do this is to avoid the strict opinionated checksum and > signature requirements on downloads.a.o (dist.a.o), as the debian and redhat > repositories have their own system for integrity and signing (which we > already do). > Furthermore, as these repositories and their binaries are "convenience > binaries" and not the official Cassandra source binaries, they do not need to > be on downloads.a.o and can be served from apache.jfrog.io. This is similar > to maven binaries (and docker images). Apache Arrow is already taking this > approach: https://arrow.apache.org/install/ > An advantage to using apache.frog.io is that these repositories maintain all > past patch versions on each repo series (major/minor). This has been > requested by users a number of times, for the sake of rolling back to a > previous patch version. downloads.a.o can only contain the latest version. > This will BREAK everyone's existing > `/etc/apt/sources.list.d/cassandra.sources.list` and > `/etc/yum.repos.d/cassandra.repo` files. Folk will need to update these files > to point to the new repo URLs. This would require an announcement to both > users@ and dev@. I do not know how we can avoid this breakage. We could put > in a simple README.md in the original URL locations explaining the breakage > and how to fix. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17748) Move deb/rpm repositories from dist/downloads .a.o to apache.jfrog.io
[ https://issues.apache.org/jira/browse/CASSANDRA-17748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-17748: --- Reviewers: Brandon Williams Status: Review In Progress (was: Patch Available) > Move deb/rpm repositories from dist/downloads .a.o to apache.jfrog.io > - > > Key: CASSANDRA-17748 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17748 > Project: Cassandra > Issue Type: Task > Components: Packaging >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Urgent > Labels: pull-request-available > Fix For: 3.11.x, 4.0.x, 4.1.x, 4.x > > > Move our official debian and redhat repositories from downloads.apache.org to > Apache's JFrog Artifactory server at apache.jfrog.io > That is, the following URLs would be moved from > ``` > https://downloads.apache.org/cassandra/debian/ > https://downloads.apache.org/cassandra/redhat/ > ``` > to > ``` > https://apache.jfrog.io/artifactory/cassandra-deb/ > https://apache.jfrog.io/artifactory/cassandra-rpm/ > ``` > The rationale to do this is to avoid the strict opinionated checksum and > signature requirements on downloads.a.o (dist.a.o), as the debian and redhat > repositories have their own system for integrity and signing (which we > already do). > Furthermore, as these repositories and their binaries are "convenience > binaries" and not the official Cassandra source binaries, they do not need to > be on downloads.a.o and can be served from apache.jfrog.io. This is similar > to maven binaries (and docker images). Apache Arrow is already taking this > approach: https://arrow.apache.org/install/ > An advantage to using apache.frog.io is that these repositories maintain all > past patch versions on each repo series (major/minor). This has been > requested by users a number of times, for the sake of rolling back to a > previous patch version. downloads.a.o can only contain the latest version. > This will BREAK everyone's existing > `/etc/apt/sources.list.d/cassandra.sources.list` and > `/etc/yum.repos.d/cassandra.repo` files. Folk will need to update these files > to point to the new repo URLs. This would require an announcement to both > users@ and dev@. I do not know how we can avoid this breakage. We could put > in a simple README.md in the original URL locations explaining the breakage > and how to fix. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17748) Move deb/rpm repositories from dist/downloads .a.o to apache.jfrog.io
[ https://issues.apache.org/jira/browse/CASSANDRA-17748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-17748: --- Fix Version/s: 3.11.x 4.0.x 4.1.x 4.x > Move deb/rpm repositories from dist/downloads .a.o to apache.jfrog.io > - > > Key: CASSANDRA-17748 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17748 > Project: Cassandra > Issue Type: Task > Components: Packaging >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Urgent > Labels: pull-request-available > Fix For: 3.11.x, 4.0.x, 4.1.x, 4.x > > > Move our official debian and redhat repositories from downloads.apache.org to > Apache's JFrog Artifactory server at apache.jfrog.io > That is, the following URLs would be moved from > ``` > https://downloads.apache.org/cassandra/debian/ > https://downloads.apache.org/cassandra/redhat/ > ``` > to > ``` > https://apache.jfrog.io/artifactory/cassandra-deb/ > https://apache.jfrog.io/artifactory/cassandra-rpm/ > ``` > The rationale to do this is to avoid the strict opinionated checksum and > signature requirements on downloads.a.o (dist.a.o), as the debian and redhat > repositories have their own system for integrity and signing (which we > already do). > Furthermore, as these repositories and their binaries are "convenience > binaries" and not the official Cassandra source binaries, they do not need to > be on downloads.a.o and can be served from apache.jfrog.io. This is similar > to maven binaries (and docker images). Apache Arrow is already taking this > approach: https://arrow.apache.org/install/ > An advantage to using apache.frog.io is that these repositories maintain all > past patch versions on each repo series (major/minor). This has been > requested by users a number of times, for the sake of rolling back to a > previous patch version. downloads.a.o can only contain the latest version. > This will BREAK everyone's existing > `/etc/apt/sources.list.d/cassandra.sources.list` and > `/etc/yum.repos.d/cassandra.repo` files. Folk will need to update these files > to point to the new repo URLs. This would require an announcement to both > users@ and dev@. I do not know how we can avoid this breakage. We could put > in a simple README.md in the original URL locations explaining the breakage > and how to fix. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17748) Move deb/rpm repositories from dist/downloads .a.o to apache.jfrog.io
[ https://issues.apache.org/jira/browse/CASSANDRA-17748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-17748: --- Status: Patch Available (was: In Progress) > Move deb/rpm repositories from dist/downloads .a.o to apache.jfrog.io > - > > Key: CASSANDRA-17748 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17748 > Project: Cassandra > Issue Type: Task > Components: Packaging >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Urgent > Labels: pull-request-available > > Move our official debian and redhat repositories from downloads.apache.org to > Apache's JFrog Artifactory server at apache.jfrog.io > That is, the following URLs would be moved from > ``` > https://downloads.apache.org/cassandra/debian/ > https://downloads.apache.org/cassandra/redhat/ > ``` > to > ``` > https://apache.jfrog.io/artifactory/cassandra-deb/ > https://apache.jfrog.io/artifactory/cassandra-rpm/ > ``` > The rationale to do this is to avoid the strict opinionated checksum and > signature requirements on downloads.a.o (dist.a.o), as the debian and redhat > repositories have their own system for integrity and signing (which we > already do). > Furthermore, as these repositories and their binaries are "convenience > binaries" and not the official Cassandra source binaries, they do not need to > be on downloads.a.o and can be served from apache.jfrog.io. This is similar > to maven binaries (and docker images). Apache Arrow is already taking this > approach: https://arrow.apache.org/install/ > An advantage to using apache.frog.io is that these repositories maintain all > past patch versions on each repo series (major/minor). This has been > requested by users a number of times, for the sake of rolling back to a > previous patch version. downloads.a.o can only contain the latest version. > This will BREAK everyone's existing > `/etc/apt/sources.list.d/cassandra.sources.list` and > `/etc/yum.repos.d/cassandra.repo` files. Folk will need to update these files > to point to the new repo URLs. This would require an announcement to both > users@ and dev@. I do not know how we can avoid this breakage. We could put > in a simple README.md in the original URL locations explaining the breakage > and how to fix. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17748) Move deb/rpm repositories from dist/downloads .a.o to apache.jfrog.io
[ https://issues.apache.org/jira/browse/CASSANDRA-17748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-17748: --- Attachment: chill.png > Move deb/rpm repositories from dist/downloads .a.o to apache.jfrog.io > - > > Key: CASSANDRA-17748 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17748 > Project: Cassandra > Issue Type: Task > Components: Packaging >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Urgent > Labels: pull-request-available > > Move our official debian and redhat repositories from downloads.apache.org to > Apache's JFrog Artifactory server at apache.jfrog.io > That is, the following URLs would be moved from > ``` > https://downloads.apache.org/cassandra/debian/ > https://downloads.apache.org/cassandra/redhat/ > ``` > to > ``` > https://apache.jfrog.io/artifactory/cassandra-deb/ > https://apache.jfrog.io/artifactory/cassandra-rpm/ > ``` > The rationale to do this is to avoid the strict opinionated checksum and > signature requirements on downloads.a.o (dist.a.o), as the debian and redhat > repositories have their own system for integrity and signing (which we > already do). > Furthermore, as these repositories and their binaries are "convenience > binaries" and not the official Cassandra source binaries, they do not need to > be on downloads.a.o and can be served from apache.jfrog.io. This is similar > to maven binaries (and docker images). Apache Arrow is already taking this > approach: https://arrow.apache.org/install/ > An advantage to using apache.frog.io is that these repositories maintain all > past patch versions on each repo series (major/minor). This has been > requested by users a number of times, for the sake of rolling back to a > previous patch version. downloads.a.o can only contain the latest version. > This will BREAK everyone's existing > `/etc/apt/sources.list.d/cassandra.sources.list` and > `/etc/yum.repos.d/cassandra.repo` files. Folk will need to update these files > to point to the new repo URLs. This would require an announcement to both > users@ and dev@. I do not know how we can avoid this breakage. We could put > in a simple README.md in the original URL locations explaining the breakage > and how to fix. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17748) Move deb/rpm repositories from dist/downloads .a.o to apache.jfrog.io
[ https://issues.apache.org/jira/browse/CASSANDRA-17748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-17748: --- Attachment: (was: chill.png) > Move deb/rpm repositories from dist/downloads .a.o to apache.jfrog.io > - > > Key: CASSANDRA-17748 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17748 > Project: Cassandra > Issue Type: Task > Components: Packaging >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Urgent > Labels: pull-request-available > > Move our official debian and redhat repositories from downloads.apache.org to > Apache's JFrog Artifactory server at apache.jfrog.io > That is, the following URLs would be moved from > ``` > https://downloads.apache.org/cassandra/debian/ > https://downloads.apache.org/cassandra/redhat/ > ``` > to > ``` > https://apache.jfrog.io/artifactory/cassandra-deb/ > https://apache.jfrog.io/artifactory/cassandra-rpm/ > ``` > The rationale to do this is to avoid the strict opinionated checksum and > signature requirements on downloads.a.o (dist.a.o), as the debian and redhat > repositories have their own system for integrity and signing (which we > already do). > Furthermore, as these repositories and their binaries are "convenience > binaries" and not the official Cassandra source binaries, they do not need to > be on downloads.a.o and can be served from apache.jfrog.io. This is similar > to maven binaries (and docker images). Apache Arrow is already taking this > approach: https://arrow.apache.org/install/ > An advantage to using apache.frog.io is that these repositories maintain all > past patch versions on each repo series (major/minor). This has been > requested by users a number of times, for the sake of rolling back to a > previous patch version. downloads.a.o can only contain the latest version. > This will BREAK everyone's existing > `/etc/apt/sources.list.d/cassandra.sources.list` and > `/etc/yum.repos.d/cassandra.repo` files. Folk will need to update these files > to point to the new repo URLs. This would require an announcement to both > users@ and dev@. I do not know how we can avoid this breakage. We could put > in a simple README.md in the original URL locations explaining the breakage > and how to fix. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17748) Move deb/rpm repositories from dist/downloads .a.o to apache.jfrog.io
[ https://issues.apache.org/jira/browse/CASSANDRA-17748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-17748: --- Status: In Progress (was: Patch Available) > Move deb/rpm repositories from dist/downloads .a.o to apache.jfrog.io > - > > Key: CASSANDRA-17748 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17748 > Project: Cassandra > Issue Type: Task > Components: Packaging >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Urgent > Labels: pull-request-available > > Move our official debian and redhat repositories from downloads.apache.org to > Apache's JFrog Artifactory server at apache.jfrog.io > That is, the following URLs would be moved from > ``` > https://downloads.apache.org/cassandra/debian/ > https://downloads.apache.org/cassandra/redhat/ > ``` > to > ``` > https://apache.jfrog.io/artifactory/cassandra-deb/ > https://apache.jfrog.io/artifactory/cassandra-rpm/ > ``` > The rationale to do this is to avoid the strict opinionated checksum and > signature requirements on downloads.a.o (dist.a.o), as the debian and redhat > repositories have their own system for integrity and signing (which we > already do). > Furthermore, as these repositories and their binaries are "convenience > binaries" and not the official Cassandra source binaries, they do not need to > be on downloads.a.o and can be served from apache.jfrog.io. This is similar > to maven binaries (and docker images). Apache Arrow is already taking this > approach: https://arrow.apache.org/install/ > An advantage to using apache.frog.io is that these repositories maintain all > past patch versions on each repo series (major/minor). This has been > requested by users a number of times, for the sake of rolling back to a > previous patch version. downloads.a.o can only contain the latest version. > This will BREAK everyone's existing > `/etc/apt/sources.list.d/cassandra.sources.list` and > `/etc/yum.repos.d/cassandra.repo` files. Folk will need to update these files > to point to the new repo URLs. This would require an announcement to both > users@ and dev@. I do not know how we can avoid this breakage. We could put > in a simple README.md in the original URL locations explaining the breakage > and how to fix. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17748) Move deb/rpm repositories from dist/downloads .a.o to apache.jfrog.io
[ https://issues.apache.org/jira/browse/CASSANDRA-17748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRA-17748: --- Labels: pull-request-available (was: ) > Move deb/rpm repositories from dist/downloads .a.o to apache.jfrog.io > - > > Key: CASSANDRA-17748 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17748 > Project: Cassandra > Issue Type: Task > Components: Packaging >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Urgent > Labels: pull-request-available > > Move our official debian and redhat repositories from downloads.apache.org to > Apache's JFrog Artifactory server at apache.jfrog.io > That is, the following URLs would be moved from > ``` > https://downloads.apache.org/cassandra/debian/ > https://downloads.apache.org/cassandra/redhat/ > ``` > to > ``` > https://apache.jfrog.io/artifactory/cassandra-deb/ > https://apache.jfrog.io/artifactory/cassandra-rpm/ > ``` > The rationale to do this is to avoid the strict opinionated checksum and > signature requirements on downloads.a.o (dist.a.o), as the debian and redhat > repositories have their own system for integrity and signing (which we > already do). > Furthermore, as these repositories and their binaries are "convenience > binaries" and not the official Cassandra source binaries, they do not need to > be on downloads.a.o and can be served from apache.jfrog.io. This is similar > to maven binaries (and docker images). Apache Arrow is already taking this > approach: https://arrow.apache.org/install/ > An advantage to using apache.frog.io is that these repositories maintain all > past patch versions on each repo series (major/minor). This has been > requested by users a number of times, for the sake of rolling back to a > previous patch version. downloads.a.o can only contain the latest version. > This will BREAK everyone's existing > `/etc/apt/sources.list.d/cassandra.sources.list` and > `/etc/yum.repos.d/cassandra.repo` files. Folk will need to update these files > to point to the new repo URLs. This would require an announcement to both > users@ and dev@. I do not know how we can avoid this breakage. We could put > in a simple README.md in the original URL locations explaining the breakage > and how to fix. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17748) Move deb/rpm repositories from dist/downloads .a.o to apache.jfrog.io
[ https://issues.apache.org/jira/browse/CASSANDRA-17748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-17748: --- Description: Move our official debian and redhat repositories from downloads.apache.org to Apache's JFrog Artifactory server at apache.jfrog.io That is, the following URLs would be moved from ``` https://downloads.apache.org/cassandra/debian/ https://downloads.apache.org/cassandra/redhat/ ``` to ``` https://apache.jfrog.io/artifactory/cassandra-deb/ https://apache.jfrog.io/artifactory/cassandra-rpm/ ``` The rationale to do this is to avoid the strict opinionated checksum and signature requirements on downloads.a.o (dist.a.o), as the debian and redhat repositories have their own system for integrity and signing (which we already do). Furthermore, as these repositories and their binaries are "convenience binaries" and not the official Cassandra source binaries, they do not need to be on downloads.a.o and can be served from apache.jfrog.io. This is similar to maven binaries (and docker images). Apache Arrow is already taking this approach: https://arrow.apache.org/install/ An advantage to using apache.frog.io is that these repositories maintain all past patch versions on each repo series (major/minor). This has been requested by users a number of times, for the sake of rolling back to a previous patch version. downloads.a.o can only contain the latest version. This will BREAK everyone's existing `/etc/apt/sources.list.d/cassandra.sources.list` and `/etc/yum.repos.d/cassandra.repo` files. Folk will need to update these files to point to the new repo URLs. This would require an announcement to both users@ and dev@. I do not know how we can avoid this breakage. We could put in a simple README.md in the original URL locations explaining the breakage and how to fix. was: Move our official debian and redhat repositories from downloads.apache.org to Apache's JFrog Artifactory server at apache.jfrog.io That is, the following URLs would be moved from ``` https://downloads.apache.org/cassandra/debian/ https://downloads.apache.org/cassandra/redhat/ ``` to ``` https://apache.jfrog.io/ui/native/cassandra-deb/ https://apache.jfrog.io/ui/native/cassandra-rpm/ ``` The rationale to do this is to avoid the strict opinionated checksum and signature requirements on downloads.a.o (dist.a.o), as the debian and redhat repositories have their own system for integrity and signing (which we already do). Furthermore, as these repositories and their binaries are "convenience binaries" and not the official Cassandra source binaries, they do not need to be on downloads.a.o and can be served from apache.jfrog.io. This is similar to maven binaries (and docker images). Apache Arrow is already taking this approach: https://arrow.apache.org/install/ An advantage to using apache.frog.io is that these repositories maintain all past patch versions on each repo series (major/minor). This has been requested by users a number of times, for the sake of rolling back to a previous patch version. downloads.a.o can only contain the latest version. This will BREAK everyone's existing `/etc/apt/sources.list.d/cassandra.sources.list` and `/etc/yum.repos.d/cassandra.repo` files. Folk will need to update these files to point to the new repo URLs. This would require an announcement to both users@ and dev@. I do not know how we can avoid this breakage. We could put in a simple README.md in the original URL locations explaining the breakage and how to fix. > Move deb/rpm repositories from dist/downloads .a.o to apache.jfrog.io > - > > Key: CASSANDRA-17748 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17748 > Project: Cassandra > Issue Type: Task > Components: Packaging >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Urgent > > Move our official debian and redhat repositories from downloads.apache.org to > Apache's JFrog Artifactory server at apache.jfrog.io > That is, the following URLs would be moved from > ``` > https://downloads.apache.org/cassandra/debian/ > https://downloads.apache.org/cassandra/redhat/ > ``` > to > ``` > https://apache.jfrog.io/artifactory/cassandra-deb/ > https://apache.jfrog.io/artifactory/cassandra-rpm/ > ``` > The rationale to do this is to avoid the strict opinionated checksum and > signature requirements on downloads.a.o (dist.a.o), as the debian and redhat > repositories have their own system for integrity and signing (which we > already do). > Furthermore, as these repositories and their binaries are "convenience > binaries" and not the official Cassandra source binaries, they do not need to > be on downloads.a.o and can be served from apache.jfrog.io. T
[jira] [Updated] (CASSANDRA-17748) Move deb/rpm repositories from dist/downloads .a.o to apache.jfrog.io
[ https://issues.apache.org/jira/browse/CASSANDRA-17748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-17748: --- Description: Move our official debian and redhat repositories from downloads.apache.org to Apache's JFrog Artifactory server at apache.jfrog.io That is, the following URLs would be moved from ``` https://downloads.apache.org/cassandra/debian/ https://downloads.apache.org/cassandra/redhat/ ``` to ``` https://apache.jfrog.io/ui/native/cassandra-deb/ https://apache.jfrog.io/ui/native/cassandra-rpm/ ``` The rationale to do this is to avoid the strict opinionated checksum and signature requirements on downloads.a.o (dist.a.o), as the debian and redhat repositories have their own system for integrity and signing (which we already do). Furthermore, as these repositories and their binaries are "convenience binaries" and not the official Cassandra source binaries, they do not need to be on downloads.a.o and can be served from apache.jfrog.io. This is similar to maven binaries (and docker images). Apache Arrow is already taking this approach: https://arrow.apache.org/install/ An advantage to using apache.frog.io is that these repositories maintain all past patch versions on each repo series (major/minor). This has been requested by users a number of times, for the sake of rolling back to a previous patch version. downloads.a.o can only contain the latest version. This will BREAK everyone's existing `/etc/apt/sources.list.d/cassandra.sources.list` and `/etc/yum.repos.d/cassandra.repo` files. Folk will need to update these files to point to the new repo URLs. This would require an announcement to both users@ and dev@. I do not know how we can avoid this breakage. We could put in a simple README.md in the original URL locations explaining the breakage and how to fix. was: Move our official debian and redhat repositories from downloads.apache.org to Apache's JFrog Artifactory server at apache.jfrog.io That is, the following URLs would be moved from ``` https://downloads.apache.org/cassandra/debian/ https://downloads.apache.org/cassandra/redhat/ ``` to ``` https://apache.jfrog.io/artifactory/cassandra-deb/ https://apache.jfrog.io/artifactory/cassandra-rpm/ ``` The rationale to do this is to avoid the strict opinionated checksum and signature requirements on downloads.a.o (dist.a.o), as the debian and redhat repositories have their own system for integrity and signing (which we already do). Furthermore, as these repositories and their binaries are "convenience binaries" and not the official Cassandra source binaries, they do not need to be on downloads.a.o and can be served from apache.jfrog.io. This is similar to maven binaries (and docker images). Apache Arrow is already taking this approach: https://arrow.apache.org/install/ An advantage to using apache.frog.io is that these repositories maintain all past patch versions on each repo series (major/minor). This has been requested by users a number of times, for the sake of rolling back to a previous patch version. downloads.a.o can only contain the latest version. This will BREAK everyone's existing `/etc/apt/sources.list.d/cassandra.sources.list` and `/etc/yum.repos.d/cassandra.repo` files. Folk will need to update these files to point to the new repo URLs. This would require an announcement to both users@ and dev@. I do not know how we can avoid this breakage. We could put in a simple README.md in the original URL locations explaining the breakage and how to fix. > Move deb/rpm repositories from dist/downloads .a.o to apache.jfrog.io > - > > Key: CASSANDRA-17748 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17748 > Project: Cassandra > Issue Type: Task > Components: Packaging >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Urgent > > Move our official debian and redhat repositories from downloads.apache.org to > Apache's JFrog Artifactory server at apache.jfrog.io > That is, the following URLs would be moved from > ``` > https://downloads.apache.org/cassandra/debian/ > https://downloads.apache.org/cassandra/redhat/ > ``` > to > ``` > https://apache.jfrog.io/ui/native/cassandra-deb/ > https://apache.jfrog.io/ui/native/cassandra-rpm/ > ``` > The rationale to do this is to avoid the strict opinionated checksum and > signature requirements on downloads.a.o (dist.a.o), as the debian and redhat > repositories have their own system for integrity and signing (which we > already do). > Furthermore, as these repositories and their binaries are "convenience > binaries" and not the official Cassandra source binaries, they do not need to > be on downloads.a.o and can be served from apache.jfrog.io. This
[jira] [Updated] (CASSANDRA-17748) Move deb/rpm repositories from dist/downloads .a.o to apache.jfrog.io
[ https://issues.apache.org/jira/browse/CASSANDRA-17748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-17748: --- Test and Documentation Plan: manual tests (testing a missing url, testing new url) Status: Patch Available (was: Open) > Move deb/rpm repositories from dist/downloads .a.o to apache.jfrog.io > - > > Key: CASSANDRA-17748 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17748 > Project: Cassandra > Issue Type: Task > Components: Packaging >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Urgent > > Move our official debian and redhat repositories from downloads.apache.org to > Apache's JFrog Artifactory server at apache.jfrog.io > That is, the following URLs would be moved from > ``` > https://downloads.apache.org/cassandra/debian/ > https://downloads.apache.org/cassandra/redhat/ > ``` > to > ``` > https://apache.jfrog.io/artifactory/cassandra-deb/ > https://apache.jfrog.io/artifactory/cassandra-rpm/ > ``` > The rationale to do this is to avoid the strict opinionated checksum and > signature requirements on downloads.a.o (dist.a.o), as the debian and redhat > repositories have their own system for integrity and signing (which we > already do). > Furthermore, as these repositories and their binaries are "convenience > binaries" and not the official Cassandra source binaries, they do not need to > be on downloads.a.o and can be served from apache.jfrog.io. This is similar > to maven binaries (and docker images). Apache Arrow is already taking this > approach: https://arrow.apache.org/install/ > An advantage to using apache.frog.io is that these repositories maintain all > past patch versions on each repo series (major/minor). This has been > requested by users a number of times, for the sake of rolling back to a > previous patch version. downloads.a.o can only contain the latest version. > This will BREAK everyone's existing > `/etc/apt/sources.list.d/cassandra.sources.list` and > `/etc/yum.repos.d/cassandra.repo` files. Folk will need to update these files > to point to the new repo URLs. This would require an announcement to both > users@ and dev@. I do not know how we can avoid this breakage. We could put > in a simple README.md in the original URL locations explaining the breakage > and how to fix. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17748) Move deb/rpm repositories from dist/downloads .a.o to apache.jfrog.io
[ https://issues.apache.org/jira/browse/CASSANDRA-17748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-17748: --- Description: Move our official debian and redhat repositories from downloads.apache.org to Apache's JFrog Artifactory server at apache.jfrog.io That is, the following URLs would be moved from ``` https://downloads.apache.org/cassandra/debian/ https://downloads.apache.org/cassandra/redhat/ ``` to ``` https://apache.jfrog.io/artifactory/cassandra-deb/ https://apache.jfrog.io/artifactory/cassandra-rpm/ ``` The rationale to do this is to avoid the strict opinionated checksum and signature requirements on downloads.a.o (dist.a.o), as the debian and redhat repositories have their own system for integrity and signing (which we already do). Furthermore, as these repositories and their binaries are "convenience binaries" and not the official Cassandra source binaries, they do not need to be on downloads.a.o and can be served from apache.jfrog.io. This is similar to maven binaries (and docker images). Apache Arrow is already taking this approach: https://arrow.apache.org/install/ An advantage to using apache.frog.io is that these repositories maintain all past patch versions on each repo series (major/minor). This has been requested by users a number of times, for the sake of rolling back to a previous patch version. downloads.a.o can only contain the latest version. This will BREAK everyone's existing `/etc/apt/sources.list.d/cassandra.sources.list` and `/etc/yum.repos.d/cassandra.repo` files. Folk will need to update these files to point to the new repo URLs. This would require an announcement to both users@ and dev@. I do not know how we can avoid this breakage. We could put in a simple README.md in the original URL locations explaining the breakage and how to fix. was: Move our official debian and redhat repositories from downloads.apache.org to Apache's JFrog Artifactory server at apache.jfrog.io That is, the following URLs would be moved from ``` https://downloads.apache.org/cassandra/debian/ https://downloads.apache.org/cassandra/redhat/ ``` to ``` https://apache.jfrog.io/artifactory/cassandra-deb/ https://apache.jfrog.io/artifactory/cassandra-rpm/ ``` The rationale to do this is to avoid the strict opinionated checksum and signature requirements on downloads.a.o (dist.a.o), as the debian and redhat repositories have their own system for integrity and signing (which we already do). Furthermore, as these repositories and their binaries are "convenience binaries" and not the official Cassandra source binaries, they do not need to be on downloads.a.o and can be served from apache.jfrog.io. This is similar to maven binaries (and docker images). This will BREAK everyone's existing `/etc/apt/sources.list.d/cassandra.sources.list` and `/etc/yum.repos.d/cassandra.repo` files. Folk will need to update these files to point to the new repo URLs. This would require an announcement to both users@ and dev@. I do not know how we can avoid this breakage. We could put in a simple README.md in the original URL locations explaining the breakage and how to fix. > Move deb/rpm repositories from dist/downloads .a.o to apache.jfrog.io > - > > Key: CASSANDRA-17748 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17748 > Project: Cassandra > Issue Type: Task > Components: Packaging >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Urgent > > Move our official debian and redhat repositories from downloads.apache.org to > Apache's JFrog Artifactory server at apache.jfrog.io > That is, the following URLs would be moved from > ``` > https://downloads.apache.org/cassandra/debian/ > https://downloads.apache.org/cassandra/redhat/ > ``` > to > ``` > https://apache.jfrog.io/artifactory/cassandra-deb/ > https://apache.jfrog.io/artifactory/cassandra-rpm/ > ``` > The rationale to do this is to avoid the strict opinionated checksum and > signature requirements on downloads.a.o (dist.a.o), as the debian and redhat > repositories have their own system for integrity and signing (which we > already do). > Furthermore, as these repositories and their binaries are "convenience > binaries" and not the official Cassandra source binaries, they do not need to > be on downloads.a.o and can be served from apache.jfrog.io. This is similar > to maven binaries (and docker images). Apache Arrow is already taking this > approach: https://arrow.apache.org/install/ > An advantage to using apache.frog.io is that these repositories maintain all > past patch versions on each repo series (major/minor). This has been > requested by users a number of times, for the sake of rolling back to a > previ
[jira] [Updated] (CASSANDRA-17748) Move deb/rpm repositories from dist/downloads .a.o to apache.jfrog.io
[ https://issues.apache.org/jira/browse/CASSANDRA-17748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-17748: --- Description: Move our official debian and redhat repositories from downloads.apache.org to Apache's JFrog Artifactory server at apache.jfrog.io That is, the following URLs would be moved from ``` https://downloads.apache.org/cassandra/debian/ https://downloads.apache.org/cassandra/redhat/ ``` to ``` https://apache.jfrog.io/artifactory/cassandra-deb/ https://apache.jfrog.io/artifactory/cassandra-rpm/ ``` The rationale to do this is to avoid the strict opinionated checksum and signature requirements on downloads.a.o (dist.a.o), as the debian and redhat repositories have their own system for integrity and signing (which we already do). Furthermore, as these repositories and their binaries are "convenience binaries" and not the official Cassandra source binaries, they do not need to be on downloads.a.o and can be served from apache.jfrog.io. This is similar to maven binaries (and docker images). This will BREAK everyone's existing `/etc/apt/sources.list.d/cassandra.sources.list` and `/etc/yum.repos.d/cassandra.repo` files. Folk will need to update these files to point to the new repo URLs. This would require an announcement to both users@ and dev@. I do not know how we can avoid this breakage. We could put in a simple README.md in the original URL locations explaining the breakage and how to fix. was: Move our official debian and redhat repositories from downloads.apache.org to Apache's JFrog Artifactory server at apache.jfrog.io That is, the following URLs would be moved from ``` https://downloads.apache.org/cassandra/debian/ https://downloads.apache.org/cassandra/redhat/ ``` to ``` https://apache.jfrog.io/artifactory/cassandra-deb/ https://apache.jfrog.io/artifactory/cassandra-rpm/ ``` The rationale to do this is to avoid the strict opinionated checksum and signature requirements on downloads.a.o (same as dist.a.o), as the debian and redhat repositories have their own system for integrity and signing (which we already do). Furthermore, as these repositories and their binaries are "convenience binaries" and not the official Cassandra source binaries, they do not need to be on downloads.a.o and can be served from apache.jfrog.io. This is similar to maven binaries (and docker images). This will BREAK everyone's existing `/etc/apt/sources.list.d/cassandra.sources.list` and `/etc/yum.repos.d/cassandra.repo` files. Folk will need to update these files to point to the new repo URLs. This would require an announcement to both users@ and dev@. I do not know how we can avoid this breakage. We could put in a simple README.md in the original URL locations explaining the breakage and how to fix. > Move deb/rpm repositories from dist/downloads .a.o to apache.jfrog.io > - > > Key: CASSANDRA-17748 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17748 > Project: Cassandra > Issue Type: Task > Components: Packaging >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Urgent > > Move our official debian and redhat repositories from downloads.apache.org to > Apache's JFrog Artifactory server at apache.jfrog.io > That is, the following URLs would be moved from > ``` > https://downloads.apache.org/cassandra/debian/ > https://downloads.apache.org/cassandra/redhat/ > ``` > to > ``` > https://apache.jfrog.io/artifactory/cassandra-deb/ > https://apache.jfrog.io/artifactory/cassandra-rpm/ > ``` > The rationale to do this is to avoid the strict opinionated checksum and > signature requirements on downloads.a.o (dist.a.o), as the debian and redhat > repositories have their own system for integrity and signing (which we > already do). > Furthermore, as these repositories and their binaries are "convenience > binaries" and not the official Cassandra source binaries, they do not need to > be on downloads.a.o and can be served from apache.jfrog.io. This is similar > to maven binaries (and docker images). > This will BREAK everyone's existing > `/etc/apt/sources.list.d/cassandra.sources.list` and > `/etc/yum.repos.d/cassandra.repo` files. Folk will need to update these files > to point to the new repo URLs. This would require an announcement to both > users@ and dev@. I do not know how we can avoid this breakage. We could put > in a simple README.md in the original URL locations explaining the breakage > and how to fix. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apac
[jira] [Updated] (CASSANDRA-17748) Move deb/rpm repositories from dist/downloads .a.o to apache.jfrog.io
[ https://issues.apache.org/jira/browse/CASSANDRA-17748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-17748: --- Change Category: Semantic Complexity: Normal Priority: Urgent (was: Normal) Status: Open (was: Triage Needed) > Move deb/rpm repositories from dist/downloads .a.o to apache.jfrog.io > - > > Key: CASSANDRA-17748 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17748 > Project: Cassandra > Issue Type: Task > Components: Packaging >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Urgent > > Move our official debian and redhat repositories from downloads.apache.org to > Apache's JFrog Artifactory server at apache.jfrog.io > That is, the following URLs would be moved from > ``` > https://downloads.apache.org/cassandra/debian/ > https://downloads.apache.org/cassandra/redhat/ > ``` > to > ``` > https://apache.jfrog.io/artifactory/cassandra-deb/ > https://apache.jfrog.io/artifactory/cassandra-rpm/ > ``` > The rationale to do this is to avoid the strict opinionated checksum and > signature requirements on downloads.a.o (same as dist.a.o), as the debian and > redhat repositories have their own system for integrity and signing (which we > already do). > Furthermore, as these repositories and their binaries are "convenience > binaries" and not the official Cassandra source binaries, they do not need to > be on downloads.a.o and can be served from apache.jfrog.io. This is similar > to maven binaries (and docker images). > This will BREAK everyone's existing > `/etc/apt/sources.list.d/cassandra.sources.list` and > `/etc/yum.repos.d/cassandra.repo` files. Folk will need to update these files > to point to the new repo URLs. This would require an announcement to both > users@ and dev@. I do not know how we can avoid this breakage. We could put > in a simple README.md in the original URL locations explaining the breakage > and how to fix. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
