[Pkg-erlang-devel] Bug#926241: multi-arch: Please make erlang-* Multi-Arch: allowed

[Tomas Janousek]

Source: erlang
Version: 1:21.2.6+dfsg-1
Severity: normal

Hi, can we please make erlang packages Multi-Arch: allowed so that dependent
packages may choose to depend on erlang-base:any if they're shipping just beam
files? As an example, elixir is built for arch "all", but isn't installable on
i386 debian with amd64 erlang packages. The elixir package will need to
explicitly depend on erlang-base:any, which it currently does not, and I'll
file a separate report later.

(This is related to #692832, but different. Multi-Arch: foreign really isn't
appropriate here, but Multi-Arch: allowed is fine.)

-- System Information:
Debian Release: buster/sid
  APT prefers testing-debug
  APT policy: (980, 'testing-debug'), (980, 'testing'), (980, 'stable'), (500, 'unstable-debug'), (500, 'stable-debug'), (500, 'unstable'), (500, 'stable'), (200, 'experimental-debug'), (200, 'experimental')
Architecture: i386 (x86_64)
Foreign Architectures: amd64

Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_USER, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8), LANGUAGE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- 
Tomáš Janoušek, a.k.a. Pivník, a.k.a. Liskni_si, http://work.lisk.in/