Package: release.debian.org
Severity: normal
User: release.debian....@packages.debian.org
Usertags: binnmu
Control: block 1069929 by -1


Hi release team!

In order to complete transition to Erlang 27 (see [1] for detail), I'd like
to ask you for a series of binNMUs. The packages erlang-asciideck,
erlang-base64url, erlang-cf, erlang-cowlib, erlang-erlware-commons,
erlang-getopt, erlang-goldrush, erlang-horse, erlang-idna, erlang-jiffy,
erlang-jose, erlang-lager, erlang-luerl, erlang-poolboy,
erlang-unicode-util-compat, erlang-mochiweb are not required to be
updated/ported to the new Erlang version, simple binNmu should be sufficient
for them.

  nmu erlang-asciideck . ANY . unstable . -m "Rebuild with Erlang 27, see 
#1069929"
  nmu erlang-base64url . ANY . unstable . -m "Rebuild with Erlang 27, see 
#1069929"
  nmu erlang-cf . ANY . unstable . -m "Rebuild with Erlang 27, see #1069929"
  nmu erlang-cowlib . ANY . unstable . -m "Rebuild with Erlang 27, see #1069929"
  nmu erlang-erlware-commons . ANY . unstable . -m "Rebuild with Erlang 27, see 
#1069929"
  nmu erlang-getopt . ANY . unstable . -m "Rebuild with Erlang 27, see #1069929"
  nmu erlang-goldrush . ANY . unstable . -m "Rebuild with Erlang 27, see 
#1069929"
  nmu erlang-horse . ANY . unstable . -m "Rebuild with Erlang 27, see #1069929"
  nmu erlang-idna . ANY . unstable . -m "Rebuild with Erlang 27, see #1069929"
  nmu erlang-jiffy . ANY . unstable . -m "Rebuild with Erlang 27, see #1069929"
  nmu erlang-jose . ANY . unstable . -m "Rebuild with Erlang 27, see #1069929"
  nmu erlang-lager . ANY . unstable . -m "Rebuild with Erlang 27, see #1069929"
  nmu erlang-luerl . ANY . unstable . -m "Rebuild with Erlang 27, see #1069929"
  nmu erlang-poolboy . ANY . unstable . -m "Rebuild with Erlang 27, see 
#1069929"
  nmu erlang-unicode-util-compat . ANY . unstable . -m "Rebuild with Erlang 27, 
see #1069929"
  nmu erlang-mochiweb . ANY . unstable . -m "Rebuild with Erlang 27, see 
#1069929"

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069929

Cheers!
-- 
Sergei Golovan

Reply via email to