Follow-up Comment #45, bug #66583 (group groff):
[just the build failure issue]
At 2024-12-31T09:55:05-0500, Alejandro Colomar wrote:
> kpathsea: Running mktextfm lcircle10
> /usr/share/texlive/texmf-dist/web2c/mktexnam: Could not map source
> abbreviation for lcircle10.
> /usr/share/texlive/tex
Hi Branden,
On Tue, Dec 31, 2024 at 10:04:22AM -0500, G. Branden Robinson wrote:
> Follow-up Comment #45, bug #66583 (group groff):
>
> [just the build failure issue]
>
> Looks to me like a missing TeX-related dependency. (A missing font,
> maybe?)
Most likely. I sometimes install stuff with
Follow-up Comment #46, bug #66583 (group groff):
Hi Branden,
On Tue, Dec 31, 2024 at 10:04:22AM -0500, G. Branden Robinson wrote:
> Follow-up Comment #45, bug #66583 (group groff):
>
> [just the build failure issue]
>
> Looks to me like a missing TeX-related dependency. (A missing font,
> maybe?
Follow-up Comment #47, bug #66583 (group groff):
At 2024-12-31T10:27:22-0500, Alejandro Colomar wrote:
> Most likely. I sometimes install stuff with --no-install-recommends,
> which might have been the responsible for this. It's good that it
> unveiled a bug in groff's build system
This conclus
Follow-up Comment #44, bug #66583 (group groff):
Hi Branden,
On Tue, Dec 31, 2024 at 07:24:03AM -0500, G. Branden Robinson wrote:
> Follow-up Comment #43, bug #66583 (group groff):
>
> Hi Alex,
>
> At 2024-12-30T01:24:39+0100, Alejandro Colomar wrote:
>> I don't know that build system [imake], an
Hi Branden,
On Tue, Dec 31, 2024 at 07:24:03AM -0500, G. Branden Robinson wrote:
> Follow-up Comment #43, bug #66583 (group groff):
>
> Hi Alex,
>
> At 2024-12-30T01:24:39+0100, Alejandro Colomar wrote:
> > I don't know that build system [imake], and don't know what I would
> > think of it. But
Follow-up Comment #2, bug #66586 (group groff):
At 2024-12-31T03:14:37-0500, Dave wrote:
> Follow-up Comment #1, bug #66586 (group groff):
>
> How does this differ from bug #61450?
It doesn't. I had simply forgotten about that ticket.
> In that bug, you said the solution "might be as simple as
Follow-up Comment #52, bug #66583 (group groff):
Hi Alex,
[comment #51 comment #51:]
> On Tue, Dec 31, 2024 at 01:18:50PM -0500, anonymous wrote:
>> Follow-up Comment #50, bug #66583 (group groff):
>> [comment #44 comment #44:]
>>> On Tue, Dec 31, 2024 at 07:24:03AM -0500, G. Branden Robinson wro
Follow-up Comment #1, bug #66586 (group groff):
How does this differ from bug #61450? In that bug, you said the solution
"might be as simple as adding a conditional to `skip_line()`," which is
exactly what your patch here does.
___
Reply
Update of bug #66586 (group groff):
Status: Postponed => Duplicate
Assigned to:None => gbranden
Open/Closed:Open => Closed
___
Follow-up Comme
Follow-up Comment #43, bug #66583 (group groff):
Hi Alex,
At 2024-12-30T01:24:39+0100, Alejandro Colomar wrote:
> On Sun, Dec 29, 2024 at 05:47:41PM -0500, G. Branden Robinson wrote:
>> Follow-up Comment #33, bug #66583 (group groff):
>> To lead with a summary: I partly disagree with your rants,
Follow-up Comment #5, bug #61450 (group groff):
Bug #66586 is a duplicate of this.
Some further observations:
1. Put this warning in the "style" category planned for _groff_ 1.25.
2. Rename `skip_line()` to `discard_rest_of_input_line()` or similar.
3. Check the warning configuration within
Follow-up Comment #50, bug #66583 (group groff):
[comment #44 comment #44:]
> On Tue, Dec 31, 2024 at 07:24:03AM -0500, G. Branden Robinson wrote:
>>> Also, the list of targets should be unconditional, and configure
>>> shouldn't mess with them. Targets are make(1)'s business. But
>>> usually, .
Follow-up Comment #49, bug #66583 (group groff):
[comment #42 comment #42:]
> Thanks.
>
> Also, if file #56729 is merely a bug-fixed version of file #56727, I'd like
> to delete the latter attachment so that it doesn't get used inadvertently.
Go ahead; I would have done it myself if I had the p
Hi Branden,
On Tue, Dec 31, 2024 at 11:01:31AM -0500, G. Branden Robinson wrote:
> Follow-up Comment #47, bug #66583 (group groff):
>
> At 2024-12-31T10:27:22-0500, Alejandro Colomar wrote:
> > Most likely. I sometimes install stuff with --no-install-recommends,
> > which might have been the res
Follow-up Comment #48, bug #66583 (group groff):
Hi Branden,
On Tue, Dec 31, 2024 at 11:01:31AM -0500, G. Branden Robinson wrote:
> Follow-up Comment #47, bug #66583 (group groff):
>
> At 2024-12-31T10:27:22-0500, Alejandro Colomar wrote:
>> Most likely. I sometimes install stuff with --no-insta
Follow-up Comment #4, bug #66586 (group groff):
[comment #2 comment #2:]
>> How does this differ from bug #61450?
>
> It doesn't. I had simply forgotten about that ticket.
OK. It was a coin toss to me whether it was an inadvertent dup or I was
missing some distinction between the two. Thanks
Hi onf,
On Tue, Dec 31, 2024 at 01:18:50PM -0500, anonymous wrote:
> Follow-up Comment #50, bug #66583 (group groff):
>
> [comment #44 comment #44:]
> > On Tue, Dec 31, 2024 at 07:24:03AM -0500, G. Branden Robinson wrote:
> >> I trust you realize that you and onf are arguing diametrically opposed
Follow-up Comment #51, bug #66583 (group groff):
Hi onf,
On Tue, Dec 31, 2024 at 01:18:50PM -0500, anonymous wrote:
> Follow-up Comment #50, bug #66583 (group groff):
>
> [comment #44 comment #44:]
>> On Tue, Dec 31, 2024 at 07:24:03AM -0500, G. Branden Robinson wrote:
>>> I trust you realize tha
19 matches
Mail list logo
