<div><div dir="auto">By default kerl uses the <a href="http://erlang.org">erlang.org</a> releases page. The patch tags are not listed there for some reason. </div></div><div dir="auto">To fetch this tag you need to use the fit backend so that kerl fetched things from github. </div><div dir="auto"><br></div><div dir="auto">export KERL_BUILD_BACKEND=git</div><div dir="auto"><br></div><div dir="auto">Then proceed as usual. I may not have remembered the variable’s name properly, it is described in kerl’s readme though. </div><div dir="auto"><br></div><div dir="auto">I opened a PR there so that the default backend be git but I think the argument is about breaking backwards compatibility. Maybe leave a comment there? Please?</div><div><br><div class="gmail_quote"><div dir="ltr">On Fri 12 Oct 2018 at 22:59, Frank Muller <<a href="mailto:frank.muller.erl@gmail.com">frank.muller.erl@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div dir="auto">Hi Rickard</div></div><div><br><div class="gmail_quote"><div dir="ltr">Why it’s not available for download?</div><div dir="ltr">“kerl update releases” shows nothing new.</div></div></div><div><div class="gmail_quote"><div dir="ltr"><br></div><div dir="ltr">/Frank </div><div dir="ltr"><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Patch Package: OTP 21.1.1<br>
Git Tag: OTP-21.1.1<br>
Date: 2018-10-12<br>
Trouble Report Id: OTP-14297, OTP-15318, OTP-15333, OTP-15335,<br>
OTP-15337, OTP-15342, OTP-15348<br>
Seq num: ERIERL-242, ERL-689, ERL-737, ERL-738,<br>
ERL-747<br>
System: OTP<br>
Release: 21<br>
Application: compiler-7.2.6, eldap-1.2.6, erts-10.1.1,<br>
ssl-9.0.3<br>
Predecessor: OTP 21.1<br>
<br>
Check out the git tag OTP-21.1.1, and build a full OTP system<br>
including documentation. Apply one or more applications from this<br>
build as patches to your installation using the 'otp_patch_apply'<br>
tool. For information on install requirements, see descriptions for<br>
each application version below.<br>
<br>
---------------------------------------------------------------------<br>
--- compiler-7.2.6 --------------------------------------------------<br>
---------------------------------------------------------------------<br>
<br>
The compiler-7.2.6 application can be applied independently of other<br>
applications on a full OTP 21 installation.<br>
<br>
--- Fixed Bugs and Malfunctions ---<br>
<br>
OTP-15335 Application(s): compiler<br>
Related Id(s): ERL-689, OTP-15219<br>
<br>
In rare circumstances, the matched out tail of a binary<br>
could be the entire original binary. (There was partial<br>
correction to this problem in version 7.2.5 of the<br>
compiler application.)<br>
<br>
<br>
Full runtime dependencies of compiler-7.2.6: crypto-3.6, erts-9.0,<br>
hipe-3.12, kernel-4.0, stdlib-2.5<br>
<br>
<br>
---------------------------------------------------------------------<br>
--- eldap-1.2.6 -----------------------------------------------------<br>
---------------------------------------------------------------------<br>
<br>
The eldap-1.2.6 application can be applied independently of other<br>
applications on a full OTP 21 installation.<br>
<br>
--- Fixed Bugs and Malfunctions ---<br>
<br>
OTP-15342 Application(s): eldap<br>
Related Id(s): ERIERL-242<br>
<br>
A race condition at close could cause the eldap client<br>
to exit with a badarg message as cause.<br>
<br>
<br>
Full runtime dependencies of eldap-1.2.6: asn1-3.0, erts-6.0,<br>
kernel-3.0, ssl-5.3.4, stdlib-2.0<br>
<br>
<br>
---------------------------------------------------------------------<br>
--- erts-10.1.1 -----------------------------------------------------<br>
---------------------------------------------------------------------<br>
<br>
Note! The erts-10.1.1 application can *not* be applied independently<br>
of other applications on an arbitrary OTP 21 installation.<br>
<br>
On a full OTP 21 installation, also the following runtime<br>
dependency has to be satisfied:<br>
-- kernel-6.1 (first satisfied in OTP 21.1)<br>
<br>
<br>
--- Fixed Bugs and Malfunctions ---<br>
<br>
OTP-14297 Application(s): erts<br>
Related Id(s): OTP-15141<br>
<br>
A bug where the socket option 'pktoptions' caused a<br>
read of uninitialized memory has been fixed. Would<br>
cause malfunction on FreeBSD.<br>
<br>
<br>
OTP-15318 Application(s): erts<br>
<br>
Fixed a memory leak on errors when reading files.<br>
<br>
<br>
OTP-15333 Application(s): erts<br>
Related Id(s): ERL-737<br>
<br>
File access through UNC paths works again on Windows.<br>
This regression was introduced in OTP 21.<br>
<br>
<br>
Full runtime dependencies of erts-10.1.1: kernel-6.1, sasl-3.0.1,<br>
stdlib-3.5<br>
<br>
<br>
---------------------------------------------------------------------<br>
--- ssl-9.0.3 -------------------------------------------------------<br>
---------------------------------------------------------------------<br>
<br>
The ssl-9.0.3 application can be applied independently of other<br>
applications on a full OTP 21 installation.<br>
<br>
--- Fixed Bugs and Malfunctions ---<br>
<br>
OTP-15337 Application(s): ssl<br>
Related Id(s): ERL-738<br>
<br>
Correct alert handling with new TLS sender process,<br>
from ssl-9.0.2. CLOSE ALERTS could under some<br>
circumstances be encoded using an incorrect cipher<br>
state. This would cause the peer to regard them as<br>
unknown messages.<br>
<br>
<br>
OTP-15348 Application(s): ssl<br>
Related Id(s): ERL-747<br>
<br>
Correct handling of socket packet option with new TLS<br>
sender process, from ssl-9.0.2. When changing the<br>
socket option {packet, 1|2|3|4} with ssl:setopts/2 the<br>
option must internally be propagated to the sender<br>
process as well as the reader process as this<br>
particular option also affects the data to be sent.<br>
<br>
<br>
Full runtime dependencies of ssl-9.0.3: crypto-4.2, erts-10.0,<br>
inets-5.10.7, kernel-6.0, public_key-1.5, stdlib-3.5<br>
<br>
<br>
---------------------------------------------------------------------<br>
---------------------------------------------------------------------<br>
---------------------------------------------------------------------<br>
_______________________________________________<br>
erlang-questions mailing list<br>
<a href="mailto:erlang-questions@erlang.org" target="_blank">erlang-questions@erlang.org</a><br>
<a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" target="_blank">http://erlang.org/mailman/listinfo/erlang-questions</a><br>
</blockquote></div></div>
_______________________________________________<br>
erlang-questions mailing list<br>
<a href="mailto:erlang-questions@erlang.org" target="_blank">erlang-questions@erlang.org</a><br>
<a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" target="_blank">http://erlang.org/mailman/listinfo/erlang-questions</a><br>
</blockquote></div></div>-- <br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div><br></div><div>Cheers,</div><div>-- </div><div>Pierre Fenoll</div></div><div><br></div></div></div>