Bug#1015174: lvm2-udeb: uninstallable, depends on non-udeb libsystemd0

[Cyril Brulebois <kibi@debian.org>]

Package: lvm2-udeb
Version: 2.03.15-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: debian-boot@lists.debian.org

[ Please keep debian-boot@ cc'd. ]

Hi,

lvm2-udeb is no longer installable, which causes some d-i images to fail
to build:

    The following packages have unmet dependencies:
     lvm2-udeb : Depends: libsystemd0 (>= 251.2) but it is not installable

This also causes some issues at runtime (even though it seems a little
strange to get that far, despite the dependency issue):
  https://lists.debian.org/debian-boot/2022/07/msg00015.html

A naive check (grepping in debian/*-udeb after an lvm2 build in unstable)
suggests that only /sbin/lvm in lvm2-udeb pulls such a NEEDED dependency
on libsystemd.so.0, for those symbols:

    U sd_id128_get_machine_app_specific@LIBSYSTEMD_233
    U sd_journal_printv_with_location@LIBSYSTEMD_209
    U sd_journal_send_with_location@LIBSYSTEMD_209

I suppose the journal bits could be patched out for the udeb build (right
now, configure ends up defining SYSTEMD_JOURNAL_SUPPORT to 1 there), but
I'm not sure what consequences disabling APP_MACHINEID_SUPPORT in the udeb
could have for arrays built at installation time (the function call itself
is already guarded within an #ifdef/#endif block, so it seems somewhat
optional already).

Feel free to let us know, and whether you'd like us to try and come up
with a tentative patch.


Cheers,
-- 
Cyril Brulebois (kibi@debian.org)            <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant