From: Eric Biggers <ebiggers@kernel.org>
To: 1066832@bugs.debian.org, 1066832-submitter@bugs.debian.org,
linux-fscrypt@vger.kernel.org, fsverity@lists.linux.dev
Subject: Re: Debian #1066832: [fsverity-utils] hard Build-Depends on unportable package pandoc
Date: Wed, 20 Mar 2024 15:37:36 -0700 [thread overview]
Message-ID: <20240320223736.GA2310@sol.localdomain> (raw)
In-Reply-To: <Pine.BSM.4.64L.2403140311320.10945@herc.mirbsd.org>
[Added the correct mailing list, fsverity@lists.linux.dev]
On Thu, Mar 14, 2024 at 03:20:07AM +0000, Thorsten Glaser wrote:
> Dixi quod…
>
> >Please split the package so that the part that requires pandoc is
> >done in an arch:all build. Normally, pandoc is needed only for
> >documentation, which is often easy enough to split off in a -doc
> >binary package, which can then move to B-D-Indep and be built on
> >amd64 or whatever hosts.
>
> Looking at this in some detail, this is *only* ONE manual page.
> Splitting into a separate package for one file will not go over
> well with ftpmaster.
>
> Dear upstream, please consider keeping the manpage in something
> else, like mdoc. I would be willing to convert the manpage to
> semantic, readable mdoc for you, even.
>
> (fsverity-utils is a Build-Depends of rpm, some subpackages of
> which are necessary to build other software even in Debian.)
>
> If upstream is not willing, we could:
>
> • do this as local patch (effort updating it every time)
>
> • hack a script that converts man/fsverity.1.md to mdoc;
> this doesn’t need to be a full converter, it needs to
> just be good enough to convert this one page (effort
> one-time, but probably not much if at all when updating)
>
> • as package maintainer, run the pandoc conversion script
> and put the result into debian/fsverity.1 and install
> from there and stop B-D’ing on pandoc (needs some, but
> not much, manual effort on each update, and the package
> maintainer to have a clean sid system on which to do that)
>
> • install a dummy manpage (that maybe summarises the options
> and points the reader to
> https://manpages.debian.org/unstable/fsverity/fsverity.1.en.html
> for the full page) on architectures without pandoc (needs
> a bit of initial hacking, and to keep a whitelist of arches
> with pandoc up-to-date)
>
> bye,
> //mirabilos
I'm not sure how reasonable this request is (surely the rpm package should not
be depending on the fsverity manual page...), but to eliminate the reliance on
pandoc I've gone ahead and replaced the markdown file fsverity.1.md with a
native Linux man page fsverity.1. So, it no longer needs any conversion before
installing it.
I did not choose mdoc, as I'm not familiar with it and it seems to be a BSD-ism.
- Eric
prev parent reply other threads:[~2024-03-20 22:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.BSM.4.64L.2403140237160.10945@herc.mirbsd.org>
2024-03-14 3:20 ` Debian #1066832: [fsverity-utils] hard Build-Depends on unportable package pandoc Thorsten Glaser
2024-03-14 3:33 ` Bug#1066832: Info received (Debian #1066832: [fsverity-utils] hard Build-Depends on unportable package pandoc) Debian Bug Tracking System
2024-03-20 22:37 ` Eric Biggers [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240320223736.GA2310@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=1066832-submitter@bugs.debian.org \
--cc=1066832@bugs.debian.org \
--cc=fsverity@lists.linux.dev \
--cc=linux-fscrypt@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox