Re: Debian #1066832: [fsverity-utils] hard Build-Depends on unportable package pandoc

Re: Debian #1066832: [fsverity-utils] hard Build-Depends on unportable package pandoc

[Thorsten Glaser]

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
-- 
21:12⎜<Vutral> sogar bei opensolaris haben die von der community so
ziemlich jeden mist eingebaut │ man sollte unices nich so machen das
desktopuser zuviel intresse kriegen │ das macht die code base kaputt
21:13⎜<Vutral:#MirBSD> linux war früher auch mal besser :D

Bug#1066832: Info received (Debian #1066832: [fsverity-utils] hard Build-Depends on unportable package pandoc)

[Debian Bug Tracking System]

Thank you for the additional information you have supplied regarding
this Bug report.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 Romain Perier <romain.perier@gmail.com>

If you wish to submit further information on this problem, please
send it to 1066832@bugs.debian.org.

Please do not send mail to owner@bugs.debian.org unless you wish
to report a problem with the Bug-tracking system.

-- 
1066832: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066832
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

Re: Debian #1066832: [fsverity-utils] hard Build-Depends on unportable package pandoc

[Eric Biggers]

[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