Hello Thomas I really appreciate your actions intended to keep the package in testing. However, the removed tests show that there are some problems on arm64 which we can't simply ignore. If we do that, there will be other bug reports, making us do something about it. I have to confess that I remove some tests from the package as well, but in 2 specific cases: * rebar3: we haven't still got rebar3 in Debian, so there's nothing to test. * backports: sometimes the tests from backported Elixir reveals some bugs[1] in Erlang from stable, so there are two solutions in the cases like that: 1) remove the corresponding tests or 2) backport Erlang along with Elixir. Removing tests is cheaper.
Coming back to Elixir and the problems related to arm64. I believe we have to find a better solution. It’s not a big deal if the package is removed from testing right now. It will turn out in testing again 1) when we figure out the root of the problem and fix it; or 2) when I (or someone else) update the package to the newest version which (probably) will be sustainable to the problem. [1] https://sources.debian.org/src/elixir-lang/1.9.1.dfsg-1~bpo10+1/debian/patches/remove_runs_eval_and_version_commands_test.patch/ -- Evgeny
