Update of bug #68115 (group groff):

                Severity:              3 - Normal => 4 - Important
                  Status:                    None => Confirmed
             Assigned to:                    None => gbranden
                 Summary: neqn: @g@ is not replaced when made => [eqn] neqn:
@g@ is not replaced when made

    _______________________________________________________

Follow-up Comment #1:

[comment #0 original submission:]
> == Bug description ==
> groff 1.24.0 distributed a buggy neqn program which invokes @g@eqn 
> instead of eqn or geqn, leading to downstream software error. For 
> example, I wanted to browse poll.3p manual, but man failed to open 
> the manual and told me as following:
> 

> man: command exited with status 127: (cd /usr/share/man &&
> /usr/lib/man-db/zsoelim) | (cd /usr/share/man && /usr/lib/man-db/manconv -f
> UTF-8:ISO-8859-1 -t UTF-8//IGNORE) | (cd /usr/share/man && preconv -e UTF-8)
> | (cd /usr/share/man && tbl) | (cd /usr/share/man && neqn -Tascii) | (cd
> /usr/share/man && nroff -mandoc -rLL=169n -rLT=169n -Tascii)


> 
> == Bug investigation ==
> I traced man with strace, which took me some time, but I managed
> to catch some detail: neqn exited with 127. If I run neqn directly,
> it throws an error:
> 

> /usr/bin/neqn: line 59: exec: @g@eqn: not found


> 
> After cloning groff git repo and diffing between 1.23.0 and
> 1.24.0, the only difference is the src/preproc/eqn/neqn.sh.
> Manually checking src/preproc/eqn/eqn.am script, I found that
> when making neqn, the sed command argument order is wrong,
> leading to @g@ not substituted. I will send a patch soon to solve
> this problem.

Good grief!  I'm sorry we didn't have a regression test to detect this.

You're right, it's just stone cold busted, and probably everywhere.


$ neqn
/home/branden/groff-stable/bin/neqn: 59: exec: @g@eqn: not found


We'll have a regression test now.  I'll write one.

Thanks for the report.  I apologize for the blunder.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?68115>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/

Attachment: signature.asc
Description: PGP signature

Reply via email to