After version 1.2.8 zlib started to be more restrict while checking for errors [1]. This caused erlang (wrong) code to not be able to use binary_to_term/1, which causes a lot of trouble, mainly the inability to use dialyzer, as can be seen on [2]. This affects all erlang versions >= 17.0 (On [2] Sverker says R16B03, but then corrects himself on [3]). What should be the approach to protect gentoo users for this issue? We could both limit zlib version on the affected versions (which includes all of the current available on portage) or use the preliminary path provided on [2]. 1 - https://github.com/madler/zlib/commit/b516b4bdd7c0c9f0858adfebf732089014f7b282 2 - http://erlang.org/pipermail/erlang-questions/2017-January/091452.html 3 - http://erlang.org/pipermail/erlang-questions/2017-January/091453.html
=sys-libs/zlib-1.2.8* is gone for good. I suggest fixing erlang here.
I'd prefer to wait for an official patch, something that's in their upstream repo. Let's at least give it a few days to see if they land it quickly (which seems likely).
(In reply to Dirkjan Ochtman from comment #2) > I'd prefer to wait for an official patch, something that's in their upstream > repo. Let's at least give it a few days to see if they land it quickly > (which seems likely). Any news on this? The fix landed nearly a month ago; February 2 for Erlang 18 and February 8 for Erlang 19. Erlang 18 announcement: http://erlang.org/pipermail/erlang-questions/2017-February/091577.html Erlang 18 git tag: https://github.com/erlang/otp/tree/OTP-18.3.4.5 Erlang 19 announcement: http://erlang.org/pipermail/erlang-questions/2017-February/091628.html Erlang 19 git tag: https://github.com/erlang/otp/tree/OTP-19.2.3 Among other things, this breaks the Elixir unit tests. As ever, I am _more than happy_ to do the scutwork to turn one of their Patch Releases into something that's more palatable for you. If it makes you feel any better about it, I get the sense that Gentoo's builds are already "unsupported", so changing the form of Patch Releases isn't going to push us any further away from upstream in that direction.
Maybe we can take tarballs from the GitHub releases, like https://github.com/erlang/otp/archive/OTP-19.2.3.tar.gz? That would be an okay strategy for me. I don't know how it would differ from the sources we get from erlang.org today. What do you mean by our builds being "unsupported"?
I will not be maintaining erlang anymore, sorry. If you can contribute, please work with the proxy maintenance team.
Is this fixed by 19.3? I would stabilize that version then
x86 stable
amd64 stable
ppc stable
