Cloudsmith repositories are no longer directly accessible, please switch to the *.rabbitmq.com mirrors #15200
michaelklishin
announced in
Maintainer announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
What Changes
RabbitMQ repositories on Cloudsmith will no longer be publicly available for
dnfandaptclients.Please migrate to
yum*.rabbitmq.comfor the RPM family of distributions and `deb*.rabbitmq.com for Debian- and Ubuntu-based ones.The DNF mirrors currently use the same signing key as the Cloudsmith repositories.
The Debian ones use our team's standard signing key instead.
Does it Mean that Binary Debian and RPM Packages of Open Source RabbitMQ Will No Longer Be Available?
No, it only means that those packages will be available from the package repositories at
*.rabbitmq.com, as documented in the installation guides.Why are We Making This Change?
Team RabbitMQ has been asking our users to migrate away from consuming packages directly from Cloudsmith for a while, since at least 2023.
Our own package repositories have dramatically higher traffic quotas, while Cloudsmith repositories have been running out of quota almost every month.
Because these Cloudsmith repositories still serve as an upstream for our own RPM package repositories, we'd like to preserve the remaining quota for package syncing to
yum*.rabbitmq.com.With this restriction in place, we expect that all new patch releases will become available on
yum*.rabbitmq.comwithin 48 hours after a new release is published.Note that
deb*.rabbitmq.comno longer rely on Cloudsmith, so nothing changes for them.Relevant Discussions
ppa*.rabbitmq.comtodeb*.rabbitmq.commigration announcementBeta Was this translation helpful? Give feedback.
All reactions