# Erlang/OTP 26.1 Released

**URL:** <https://erlangforums.com/t/erlang-otp-26-1-released/2886>\
**Category:** Erlang News\
**Tags:** erlang-release\
**Created:** [September 21, 2023, 7:08am UTC](https://erlangforums.com/t/erlang-otp-26-1-released/2886 "2023-09-21T07:08:50Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![proxyles](https://erlangforums.com/letter_avatar_proxy/v4/letter/p/9de053/32.png) [@proxyles](https://erlangforums.com/u/proxyles)\
**Post date:** [September 21, 2023, 7:08am UTC](https://erlangforums.com/t/erlang-otp-26-1-released/2886/1 "2023-09-21T07:08:50Z")

</div>

## OTP 26.1 [#](https://www.erlang.org/news/165#otp-261)

Erlang/OTP 26.1 is the first maintenance patch package for OTP 26, with mostly bug fixes as well as improvements.

For details about bugfixes and potential incompatibilities see the [Erlang 26.1 README](https://erlang.org/download/otp_src_26.1.readme)

The Erlang/OTP source can also be found at GitHub on the official Erlang repository, [GitHub - erlang/otp: Erlang/OTP](https://github.com/erlang/otp)

Download links for this and previous versions are found here

- [Downloads - Erlang/OTP](https://www.erlang.org/downloads)

---

<div class="post-metadata">

**Author:** ![dlachausse](https://erlangforums.com/user_avatar/erlangforums.com/dlachausse/32/2067_2.png) [@dlachausse](https://erlangforums.com/u/dlachausse)\
**Post date:** [September 21, 2023, 11:29am UTC](https://erlangforums.com/t/erlang-otp-26-1-released/2886/2 "2023-09-21T11:29:22Z")

</div>

Just a heads up, you linked to the Erlang **25**.1 README instead of **26**.1.

Great job to everyone involved with this release!

---

<div class="post-metadata">

**Author:** ![nzok](https://erlangforums.com/letter_avatar_proxy/v4/letter/n/4af34b/32.png) [@nzok](https://erlangforums.com/u/nzok)\
**Post date:** [September 21, 2023, 11:46am UTC](https://erlangforums.com/t/erlang-otp-26-1-released/2886/3 "2023-09-21T11:46:40Z")

</div>

Speaking of releases,

% sudo apt update  
…  
Err:18 [http://binaries.erlang-solutions.com/debian](http://binaries.erlang-solutions.com/debian) jammy Release  
404 Not Found [IP: 13.33.21.93 80]  
…  
E: The repository ‘[http://binaries.erlang-solutions.com/debian](http://binaries.erlang-solutions.com/debian) jammy Release’ does not have a Release file.

What do I do about this, especially to get an updated Erlang?

---

<div class="post-metadata">

**Author:** ![LeonardB](https://erlangforums.com/user_avatar/erlangforums.com/leonardb/32/1856_2.png) [@LeonardB](https://erlangforums.com/u/LeonardB)\
**Post date:** [September 21, 2023, 1:13pm UTC](https://erlangforums.com/t/erlang-otp-26-1-released/2886/4 "2023-09-21T13:13:51Z")

</div>

IIRC erlang-solutions stopped providing packages a while back (in Feb I think)

Using the RabbitMQ PPA for Erlang is an option if you just want pre-compiled debs vs building your own release with kerl/asdf

[https://launchpad.net/~rabbitmq/+archive/ubuntu/rabbitmq-erlang](https://launchpad.net/~rabbitmq/+archive/ubuntu/rabbitmq-erlang)

---

<div class="post-metadata">

**Author:** ![sverker](https://erlangforums.com/user_avatar/erlangforums.com/sverker/32/841_2.png) [@sverker](https://erlangforums.com/u/sverker)\
**Post date:** [September 21, 2023, 1:18pm UTC](https://erlangforums.com/t/erlang-otp-26-1-released/2886/5 "2023-09-21T13:18:37Z")

</div>

> [@dlachausse](#):
>
> Just a heads up, you linked to the Erlang **25**.1 README instead of **26**.1.

Link fixed. Thank you.

---

<div class="post-metadata">

**Author:** ![ilkka](https://erlangforums.com/user_avatar/erlangforums.com/ilkka/32/2086_2.png) [@ilkka](https://erlangforums.com/u/ilkka)\
**Post date:** [September 21, 2023, 1:46pm UTC](https://erlangforums.com/t/erlang-otp-26-1-released/2886/6 "2023-09-21T13:46:47Z")

</div>

There’s been some work over there to support jammy, see [https://github.com/esl/packages/issues/15](https://github.com/esl/packages/issues/15) for the latest. I just use asdf these days.

---

<div class="post-metadata">

**Author:** ![gonzalobf](https://erlangforums.com/user_avatar/erlangforums.com/gonzalobf/32/1480_2.png) [@gonzalobf](https://erlangforums.com/u/gonzalobf)\
**Post date:** [September 21, 2023, 2:54pm UTC](https://erlangforums.com/t/erlang-otp-26-1-released/2886/7 "2023-09-21T14:54:15Z")

</div>

What is the correct way of reusing ports with `gen_udp` in OTP26.1?

Previosly, we did `gen_udp:open(Por, [{inet_backend, socket}, {reuseaddr, true}])` and I see `reuseport` was added in [[erts, kernel] reuseaddr/reuseport/exclusiveaddruse support/fixes by rickard-green · Pull Request #6522 · erlang/otp · GitHub](https://github.com/erlang/otp/pull/6522) but I don’t get it to work:

```erlang
1> gen_udp:open(88888, [{inet_backend, socket}, {reuseaddr, true}, {reuseport, true}]).
{ok,{'$inet',gen_udp_socket,
             {<0.92.0>,
              {'$socket',#Ref<0.1985961887.3750363144.125730>}}}}
2> gen_udp:open(88888, [{inet_backend, socket}, {reuseaddr, true}, {reuseport, true}]).
{error,eaddrinuse}

```

In OTP26.0.2:

```erlang
1> gen_udp:open(88888, [{inet_backend, socket}, {reuseaddr, true}]).
{ok,{'$inet',gen_udp_socket,
             {<0.26238807.0>,
              {'$socket',#Ref<0.3205098475.2836529154.55286>}}}}
2> gen_udp:open(88888, [{inet_backend, socket}, {reuseaddr, true}]).
{ok,{'$inet',gen_udp_socket,
             {<0.26238551.0>,
              {'$socket',#Ref<0.3205098475.2836529154.59029>}}}}

```
