On Sun, May 03, 2020 at 09:02:11PM +0200, Paul Gevers wrote: > > Alright, then I recommend this: > > reassign 958841 src:erlang 1:22.3.2+dfsg-1 > > clone 958841 -1 > > reassign -1 src:elixir-lang 1.9.1.dfsg-1.3 > > retitle -1 elixir-lang: incompatible with erlang 22 > > # consider also leaving a longer message somewhere…? > > close 958841 1:22.3.3+dfsg-1 > > > > Doing that should live a RC bug in elixir-lang, and cause its autorm in > > a while, and leave erlang where it is, letting it migrate to testing as > > soon as elixir-lang is out. The rm from testing of elixir-lang could be > > expedited if nothing happens. > > I agree with this approach. It leaves the maintainers of elixir-lang > some time to fix the situation. If they don't fix it, it will be removed > and erlang can migrate. Unless there is some issue that I am not aware > of that warrants a faster migration (and hence removal of elixir-lang).
Very well, I've now send that to command@, and added a `summary` to the cloned bug to explain a bit what's happening. The new bug against elixir-lang is #959701. > Given the issue as I understand it, I don't want to binNMU it. I think > the binNMU'd package can migrate before erlang and then the package in > testing is broken (until erlang migrates) which isn't cool I don't think that would happen. bin:elixir depends on erlang-pcre-8.43, which is provided by bin:erlang-core in testing, but erlang-core in unstable only provides erlang-pcre-8.43-1 instead. (I believe that's the original cause of the breakage, an ABI break in that thing.) -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. More about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature