Package: release.debian.org
Severity: normal
User: release.debian....@packages.debian.org
Usertags: transition
X-Debbugs-Cc: erl...@packages.debian.org
Control: affects -1 + src:erlang
Hi release team!
I'd like to update Erlang for trixie to new major release Erlang 27
which is due in upcoming May or June. Since currently Erlang 25 is
in Debian (two major releases short) I expect some failures of
rebuilding existing packages (Erlang 27 introduces new expressions,
removes some deprecated functions etc.).
I've already uploaded erlang 1:27.0+dfsg~rc3 to experimental for testing and
started to check if the affected packaged build (at least).
My plan is the following:
1. Finish testing all the reverse dependencies with rc3 and upcoming
1:27.0+dfsg,
file bugreports.
2. Elang 27 build depends on a few packages which aren't in testing or
even in Debian yet:
* autoconf (>= 2.72), it is in experimetal at the moment, see [1]
* node-fontsource-inconsolata, node-fontsource-lato,
* node-fontsource-merriweather, they are used to build documentation
(currently Erlang in experimental is built without docs) and sit in
NEW (see [2], [3], [4]). By the way is this normal that the are in NEW
for two months without any resolution?
3. So after these packages clear unstable, and after 1:27.0.1 is out
(June or July 2024), I'll upload Erlang to unstable and likely do
a bunch of NMUs to fix remaining bugs. There will be necessary
to do quite a few bin-NMUs also.
Here is the list of affected packages with short comments where I did
some testing:
# Broken (not in testing)
averell
ejabberd
ejabberd-contrib (builds fine, depends on ejabberd)
erlang-cowboy
erlang-p1-pgsql (builds fine, depends on erlang-p1-xml)
erlang-ranch
erlang-p1-xmpp (builds fine, depends on erlang-p1-xml)
erlang-p1-xml
# Broken (need patching/updating)
erlang-bbmustache
erlang-jiffy
erlang-luerl
erlang-p1-pkix
erlang-p1-sqlite3
erlang-p1-tls
erlang-p1-utils
kamailio (uses only C interface to Erlang, FTBFS is unrelated to Erlang)
mochiweb (fix of rebar3 dependencis should help)
elixir (patch is ready, also upcoming 1.17 will support Erlang 27 explicitly)
rebar3 (updating to 3.23.0 works, have to update dependencies, e.g.
erlang-inets is missing for 27)
wings3d (patch is ready)
yaws (patch is ready)
# Broken (need elixir and likely patching/updating)
erlang-hex
rabbitmq-server
# Build as is
erlang-asciideck
erlang-base64urls
erlang-bear
erlang-bitsack
erlang-cf
erlang-cl
erlang-cowlib
erlang-cuttlefish
erlang-erlware-commons
erlang-folsom
erlang-getopt
erlang-goldrush
erlang-horse
erlang-idna
erlang-jose
erlang-lager
erlang-meck
erlang-metrics
erlang-mimerl
erlang-p1-acme
erlang-p1-cache-tab
erlang-p1-eimp
erlang-p1-iconv
erlang-p1-mqtree
erlang-p1-mysql
erlang-p1-oauth2
erlang-p1-pam
erlang-p1-sip
erlang-p1-stringprep
erlang-p1-stun
erlang-p1-yaml
erlang-p1-yconf
erlang-p1-zlib
erlang-poolboy
erlang-proper
erlang-redis-client
erlang-unicode-util-compat
erlang-uuid
manderlbot
neotoma
rebar
sonic-pi
tsung
[1] https://tracker.debian.org/pkg/autoconf
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065253
[3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065254
[4] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065256
The Ben file below should correctly determine the affected packages, but
definitely does not cover all possible cases of bad and good packages
(some of them require elixir instead of erlang-base, for example)
Ben file:
title = "erlang";
is_affected = .build-depends ~ /dh-rebar|erlang-dev|erlang-base|rebar|rebar3/;
is_good = .depends ~ /erlang-base (>= 1:27/;
is_bad = .depends ~ /erlang-base (>= 1:(1|2[0-6])/;
--
Sergei Golovan
