Hi!

On Thu, 2026-07-09 at 10:29:27 -0500, G. Branden Robinson wrote:
> At 2026-06-19T03:07:34+0200, Guillem Jover wrote:
> > I tried my system pod2man with PERL5LIB pointing to the Pod modules
> > from git, and that didn't fix anything, so it appears like this is not
> > fixed yet (and might have never been reported upstream?), but maybe I
> > botched my testing process. I didn't see anything obvious related to
> > .IP in «git log» (besides the justification fixes).

> If by "upstream" you meant pod2man, it's worth exploring whether that
> tool is generating `TP` macros for things like definition lists, or
> `IP`.  `TP` is a better choice and it is going to become increasingly
> important given changes expected in groff 1.25 and planned for the
> future.

Ah, sorry, indeed by "upstream" I was referring here to podlators.

Checking briefly now, I see multiple instances of «.IP». For example for
dpkg.pod, the source is:

,---
=head2 Package selection states

=over

=item B<install>

The package is selected for installation.

=item B<hold>

A package marked to be on B<hold> is kept on the same version, that is,
no automatic new installs, upgrades or removals will be performed on them,
unless these actions are requested explicitly, or are permitted to be done
automatically with the B<--force-hold> option.

=item B<deinstall>

[…]
`---

And the generated troff is:

,---
.SS "Package selection states"
.IX Subsection "Package selection states"
.IP \fBinstall\fR 4
.IX Item "install"
The package is selected for installation.
.IP \fBhold\fR 4
.IX Item "hold"
A package marked to be on \fBhold\fR is kept on the same version, that is,
no automatic new installs, upgrades or removals will be performed on them,
unless these actions are requested explicitly, or are permitted to be done
automatically with the \fB\-\-force\-hold\fR option.
.IP \fBdeinstall\fR 4
.IX Item "deinstall"
[…]
`---

With the rendered output from man being:

,---
   Package selection states
     install
         The package is selected for installation.

     holdA package marked to be on hold is kept on the same version, that is,
         no automatic new installs, upgrades or removals will be performed on
         them, unless these actions are requested explicitly, or are permitted
         to be done automatically with the --force-hold option.

     deinstall
`---

Branden I guess you are in a getter position to file a bug to podlators
upstream, having more details and knowledge on the matter, but if you
are short on time, I could try to concoct some report (where I'll need
to read about the fine details about this I guess, which I've kind of
skipped up to now O:).

Thanks,
Guillem

Reply via email to