No Debian trixie packages on deb1.rabbitmq.com

[noonedeadpunk]

Is your feature request related to a problem? Please describe.

Hi,

We used to be using https://ppa1.rabbitmq.com/rabbitmq/rabbitmq-erlang as a source for erlang on Debian Trixie.

With removal of the repository content, we attempted to switch to https://deb1.rabbitmq.com/rabbitmq-erlang/, but quickly realized that Trixie is not present there, and Debian Trixie instruction is not mentioning existance of erlang package either.

However, I see the corresponding branch does exist within the project:
https://github.com/rabbitmq/erlang-debian-package/tree/OTP-27.x/debian/trixie

Packages seems to be also present on Cloudsmith as well: https://cloudsmith.io/~rabbitmq/repos/rabbitmq-erlang/packages/?q=distribution%3Adebian+AND+distribution%3Atrixie

Describe the solution you'd like

Debian Trixie erlang packages are published in deb1.rabbitmq.com/rabbitmq-erlang/debian/trixie

Describe alternatives you've considered

No response

Additional context

No response

[michaelklishin]

@noonedeadpunk our team has been asking everyone to stop using Cloudsmith directly for several years. It already runs out of traffic quota in 2-3 weeks every month.

Debian Trixie packages of Erlang 27 are produced as of September.

They are not published to the deb*.rabbitmq.com repositories yet. They will be one day but I don't have an ETA and producing Erlang releases is not a priority for Team RabbitMQ. We only produce these packages because Debian's packages are always hopelessly out of date.

A single Erlang/OTP release on Debian Trixie is 60 (yes, sixty) packages. That requires special tooling for handling release artifacts compared to RabbitMQ (a single .deb file) or Erlang, RabbitMQ RPMs (a single .rpm file for each, assuming our zero dependency Erlang package is used).

I'm quite certain that using the Bookworm version will work perfectly fine on Trixie, although the OpenSSL version bump from 3.0 to 3.5 can be problematic (it was for certain RPM-based distributions). You are welcome to try it.

[michaelklishin]

Also, everyone is welcome to build this package from source — all the hard work was already done for you — and publish the packages to your own Cloudsmith (or PackageCloud, or Artifactory) account.

You will immediately see what I mean by "this Debian package requires extra tooling for sane publishing." In any case, the hard work of adapting the package for very recent Erlang and several Debian/Ubuntu versions is done, the community that wants to use the Trixie version should take it from here when it comes to builds and distribution. We are only in the Erlang/OTP packaging business because Linux distribution maintainers have been dropping the ball so badly for years and years.

[noonedeadpunk]

Thank you for detailed response.

stop using Cloudsmith directly for several years

Yes, sure, I was using CloudSmith UI as a search engine only, to see what is available in ppa1/yum1 repos, as listing directory indexes was prohibited there.
It was not used as a package source for a couple of years now.

I was just assuming that the new deb1 repos are behaving alike to already removed ppa1, and that if packages were already built (and they were working nicely by the way), then there is just some missing "promote" workflow I was not able to find in the repo by myself.
So was hoping it could be a simple fix, which I just failed find on myself.

[michaelklishin]

Your thinking is largely correct, deb*.rabbitmq.com were created by importing most packages from ppa*.rabbitmq.com.

Back in the ppa*.rabbitmq.com era, we have started building Trixie packages before it was released. Then a few breaking changes in Erlang and Debian follows, for example, their autoconf version assumptions have diverged, so package builds failed at ./configure.

That has stopped the flow of Trixie packages. Then Trixie shipped, we have consulted with the Erlang/OTP team and fixed the package to not run autoconf at all (it's not necessary these days).

Anyhow, the Trixie packages of Erlang 27 are now build successfully and will be distributed to our mirrors soon-ish (I cannot make any ETA promises).

Note that for RabbitMQ users specifically, the Erlang 27.x that Trixie ships is sufficient, which means we were under little pressure to update our tooling that drives aptly to import those 60 packages per version. I guess now we see more interest.

Sorry about this situation. Trixie builds for x86-64 will be covered soon enough.

[michaelklishin]

@noonedeadpunk Erlang/OTP 27.3.4.6 is now available for Debian Trixie on deb1.rabbitmq.com and deb2.rabbitmq.com.

[noonedeadpunk]

Thanks for the update! It was faster then I expected :)

I've already tested it, and it seems to work nicely!

[michaelklishin]

Sweet, thank you!

Going forward we have a 90-95% automated infrastructure so Erlang releases will show up in our Debian repos within no more than a few days since their releases.

In order to deal with the 50-60 package strong releases, all packages are now released as a single tarball and our repo management tool can import them (aptly itself can only import one .deb file at a time).

And the tool itself will be open sourced soon. I doubt almost anyone would need it but for the sake of transparency and being more contribution-friendly (or contribution-ready anyway) in more areas, it's the right thing to do.