Hi Emilio, On Wed, Jun 17, 2026 at 12:32 PM Emilio Pozuelo Monfort <[email protected]> wrote: > > Control: tags -1 confirmed > > This is already ongoing, marking as such.
Thank you! > > On 03/06/2026 19:37, Sergei Golovan wrote: > > Now, I'm planning to: > > 1. send bugreports to the packages which FTBFS with severity normal; > > 2. upload Erlang 29 and Elixir to unstable right after Elixir 1.20 is > > released > > 3. bump severity of FTBFS bugs to serious; > > 4. make binNMUS for all affected packages (there are 66 of them, two of > > which aren't in testing) > > Are we ready for that binNMU round? Do I understand correctly, that binNMU just replaces the existing package, so if there is the same version in testing and in unstable then the binNMUd version immediately becomes available in testing and in unstable? If it is so, then I'd wait until erlang 29 with a few packages (elixir, elixir-ex-doc) enter testing. If binNMUs are treated as new versions with their own migration schedule, then I'll prepare the list of binNMUs shortly. As for now, I've uploaded erlang, elixir-lang, and a few packages that need updating/patching (tsung, erlang-hex, erlang-erware-commons, elixir-ex-doc). Also, the maintainer of rabbitmq-server has updated it as well. So, there are several new packages in unstable. They are still not in testing either because of their age, or because of some issues with reverse dependencies. In particular: autopkgtests triggered by rabbitmq-server (see [1]) fail because they are trying to run the new rabbitmq-server (built with erlang 29) with erlang 27. I think that simultaneous migration of erlang 29 and rabbitmq-server should be fine, but I didn't find corresponding autopkgtest logs to confirm. Manually executed autopkgtests do not fail for me. Apparently, ruby-bunny requires an update to work with the new rabbitmq-server, but it currently suffers from a random FTBFS bug (see [2]). Santiago did a good job of reporting the bug upstream and preparing the patch. Hopefully, it'll be fixed soon. [1] https://tracker.debian.org/pkg/rabbitmq-server [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1139980 Cheers! -- Sergei Golovan
