Bug#1123615: systemd-userdbd: consider making it Multi-Arch: foreign
Package: systemd-userdbd
Version: 259-1
Severity: normal
X-Debbugs-Cc: debian-cross@lists.debian.org
libnss-systemd 259-1 newly Recommends systemd-userdbd. systemd-userdbd
is Multi-Arch: no (the default), meaning that when an i386 package has a
Depends or Recommends on systemd-userdbd, that dependency will only be
considered to be satisfied if you install systemd-userdbd:i386.
On a system with both libnss-systemd:amd64 and libnss-systemd:i386,
when I upgraded from 259~rc3-1 to 259-1, aptitude arbitrarily chose to
satisfy the Recommends for libnss-systemd:i386 and break the Recommends
for libnss-systemd:amd64 instead of the other way around, meaning that
it proposed to install libsystemd-shared:i386 and its dependency
libraries. This seems probably unintended.
If systemd-userdbd does what I think it does (providing an
architecture-independent API that works for both amd64 and i386 clients,
via D-Bus or varlink or some similar protocol), then it should probably
be Multi-Arch: foreign like systemd-container, systemd-resolved and
systemd-timesyncd are.
That way, installing libnss-systemd for any architecture (even cross
architectures) would pull in systemd-userdbd for the system's primary
architecture.
Thanks,
smcv
Reply to: