Devuan bug report logs - #844
systemd-boot-efi: Broken man pages

Package: systemd-boot-efi; Maintainer for systemd-boot-efi is (unknown); Source for systemd-boot-efi is src:systemd.

Reported by: murzik <lorietta2023@gmail.com>

Date: Sun, 24 Mar 2024 23:02:02 UTC

Severity: minor

Tags: debian

Found in version 252.22-1~deb12u1

Full log

Message #15 received at 844@bugs.devuan.org (full text, mbox, reply):

Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=2607:f8b0:4864:20::1144; helo=mail-yw1-x1144.google.com; envelope-from=lorietta2023@gmail.com; receiver=<UNKNOWN> 
Date: Wed, 03 Apr 2024 22:07:50 +1100
From: murzik <lorietta2023@gmail.com>
Subject: Re: bug#844: systemd-boot-efi: Broken man pages
To: Mark Hindley <mark@hindley.org.uk>
Cc: 844@bugs.devuan.org
Message-Id: <2L5DBS.T9QOCYZP64CK@gmail.com>
In-Reply-To: <ZgHty6rlNk2w1_bp@hindley.org.uk>
References: <KUJVAS.IZEOYIY8E6H11@gmail.com>
	<ZgHty6rlNk2w1_bp@hindley.org.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=-h2MP1iqvWySrhbGtRkEt"

[Message part 1 (text/plain, inline)]

oh.. sad. anyway, thanks for letting me know. This error will 100% be 
revealed sooner or later. maybe its possible to just replace 
systemd-stub-efi with systemd-srub-efi-standalone? It will be extremely 
strange if the only way to use sd-stub in devuan is to dig into the 
meason config and build systemd yourself. Also, implementing a 
standalone package will be extremely simple - nothing other than 
editing the meson config is required. Also, there is already a 
ready-made config and implementation: 
<https://github.com/schreiberstein/systemd-efi-stub-standalone>
As far as I can tell, the project has experience in this.
we already have systemd-bootchart; systmed-sysusers-standalone; 
systemd-tpmfiles-standalone; systemd-oomd.. I don't think adding one 
standalone package will be a problem.

On Mon, Mar 25 2024 at 09:34:03 PM +00:00:00, Mark Hindley 
<mark@hindley.org.uk> wrote:
> Control: tags -1 debian
> 
> On Mon, Mar 25, 2024 at 09:59:08AM +1100, murzik wrote:
>>     Package: systemd-boot-efi
> 
> This is not a forked package and Devuan uses Debian's packages 
> directly without
> recompilation.
> 
>>     X-Debbugs-Cc: lorietta2023@gmail.com 
>> <mailto:lorietta2023@gmail.com>
>>     Version: 252.22-1~deb12u1
>>     Severity: minor
>>     Dear Maintainer,
>>     Looks like linuxia32.efi.stub and linuxx64.efi.stub man pages are
>>     broken.
>>     The package was installed from the repositories via APT and 
>> passes
>>     integrity tests.
>>     [✖ user@host ~ ]$ man linuxia32.efi.stub
>>     man: can't resolve man7/systemd-stub.7
>>     No manual entry for linuxia32.efi.stub
>>     [✖ user@host ~ ]$ man linuxx64.efi.stub
>>     man: can't resolve man7/systemd-stub.7
> 
> man7/systemd-stub.7 is contained in bin:systemd[1]. So you have 
> uncovered a
> missing dependency: systemd-boot-efi should depend on systemd.
> 
> In principle, this should be reported to Debian's BTS to be fixed. 
> However, if
> it was fixed in Debian, systemd-boot-efi would become unavailable in 
> Devuan as
> the systemd package and its rdepends are banned and removed by 
> amprolla. That
> may not be what you want to achieve.
> 
> The choice is yours.
> 
> Mark
> 
> [1]  
> <https://packages.debian.org/search?suite=bookworm&arch=any&mode=filename&searchon=contents&keywords=systemd-stub>
>

[Message part 2 (text/html, inline)]

Send a report that this bug log contains spam.

Devuan bug report logs - #844 systemd-boot-efi: Broken man pages

Devuan bug report logs - #844
systemd-boot-efi: Broken man pages