[MacPorts] #43617: texlive: texi2dvi incompatible with bsdsed
#43617: texlive: texi2dvi incompatible with bsdsed ---------------------+-------------------------------- Reporter: ionic@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: texlive ---------------------+-------------------------------- TeXlive's texi2dvi command is incompatible with bsdsed in the case of texinfo files requiring recode. An incarnation of that can be seen in #38744. A far as I can see, we have to options: ping upstream on this issue and hope for them to resolve the bug, or rewrite texi2dvi (and possibly other tools?!) to use "gsed" instead of just "sed". Maintainer: what is your take on this? -- Ticket URL: <https://trac.macports.org/ticket/43617> MacPorts <http://www.macports.org/> Ports system for OS X
#43617: texlive: texi2dvi incompatible with bsdsed ----------------------+---------------------- Reporter: ionic@… | Owner: dports@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: texlive | ----------------------+---------------------- Changes (by mk@…): * owner: macports-tickets@… => dports@… * cc: dports@… (removed) -- Ticket URL: <https://trac.macports.org/ticket/43617#comment:1> MacPorts <http://www.macports.org/> Ports system for OS X
#43617: texlive: texi2dvi incompatible with bsdsed ----------------------+---------------------- Reporter: ionic@… | Owner: dports@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: texlive | ----------------------+---------------------- Comment (by mojca@…): Doesn't texi2dvi belong to texinfo (non-maintained port) rather than TeX Live? Is anyone willing to come up with a minimal example and send a bug report? {{{ REPORTING BUGS Report bugs to bug-texinfo at gnu.org, general questions and discussion to help-texinfo at gnu.org. GNU Texinfo home page: <http://www.gnu.org/software/texinfo/> General help using GNU software: <http://www.gnu.org/gethelp/> }}} -- Ticket URL: <https://trac.macports.org/ticket/43617#comment:4> MacPorts <http://www.macports.org/> Ports system for OS X
#43617: texlive: texi2dvi incompatible with bsdsed ----------------------+---------------------- Reporter: ionic@… | Owner: dports@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: texlive | ----------------------+---------------------- Comment (by ionic@…): Mea culpa. Indeed, it does. Would you please be so kind to remove dports and change the description + affected port to texinfo? I blindly relied on the maxima port to get its dependencies right (obviously, it's depending on texlive for +printable_docs) and didn't even bother to double-check, whether texi2dvi is actually included in texlive. I could try coming up with a minimal example... at least I kind-of-know what is causing this bug. -- Ticket URL: <https://trac.macports.org/ticket/43617#comment:5> MacPorts <http://www.macports.org/> Ports system for OS X
#43617: texinfo: texi2dvi incompatible with bsdsed ----------------------+-------------------------------- Reporter: ionic@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: texinfo | ----------------------+-------------------------------- Changes (by mojca@…): * owner: dports@… => macports-tickets@… * cc: dports@… (added) * port: texlive => texinfo Old description:
TeXlive's texi2dvi command is incompatible with bsdsed in the case of texinfo files requiring recode.
An incarnation of that can be seen in #38744.
A far as I can see, we have to options: ping upstream on this issue and hope for them to resolve the bug, or rewrite texi2dvi (and possibly other tools?!) to use "gsed" instead of just "sed".
Maintainer: what is your take on this?
New description: texinfo's `texi2dvi` command is incompatible with bsdsed in the case of texinfo files requiring recode. An incarnation of that can be seen in #38744. A far as I can see, we have to options: ping upstream on this issue and hope for them to resolve the bug, or rewrite texi2dvi (and possibly other tools?!) to use "gsed" instead of just "sed". -- -- Ticket URL: <https://trac.macports.org/ticket/43617#comment:6> MacPorts <http://www.macports.org/> Ports system for OS X
#43617: texinfo: texi2dvi incompatible with bsdsed ----------------------+-------------------------------- Reporter: ionic@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: texinfo | ----------------------+-------------------------------- Comment (by ionic@…): I'm just not sure what to do with that. Sure, `texi2dvi` fails with `bsdsed` and it doesn't with `gnused`. But does this mean, that it is a texinfo bug? The baseline is `bsdsed` as shipped by Apple failing when being run on any input containing non-ASCII characters. To make matters even more complicated: it fails only when `LC_CTYPE` is set to any UTF-8 locale. Running `LC_CTYPE=C LANG=C texi2dvi --pdf --batch foo.texi` works fine. So... I guess `texi2dvi` needs some more code to detect the input file's charset and and change the `LC_CTYPE` and `LANG` environment variables accordingly to some locale supporting the detected charset... but does that make sense? -- Ticket URL: <https://trac.macports.org/ticket/43617#comment:7> MacPorts <http://www.macports.org/> Ports system for OS X
#43617: texinfo: texi2dvi incompatible with bsdsed ----------------------+-------------------------------- Reporter: ionic@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: texinfo | ----------------------+-------------------------------- Comment (by ionic@…): Upstream is not interested. We'll have to set `LC_ALL` in our build environment based on the input file's encoding (and hope they don't switch between `UTF-8` and other encodings for different input files.) You may set this ticket's status to `invalid`. -- Ticket URL: <https://trac.macports.org/ticket/43617#comment:8> MacPorts <http://www.macports.org/> Ports system for OS X
#43617: texinfo: texi2dvi incompatible with bsdsed ----------------------+-------------------------------- Reporter: ionic@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: invalid | Keywords: Port: texinfo | ----------------------+-------------------------------- Changes (by mf2k@…): * status: new => closed * resolution: => invalid -- Ticket URL: <https://trac.macports.org/ticket/43617#comment:9> MacPorts <http://www.macports.org/> Ports system for OS X
#43617: texinfo: texi2dvi incompatible with bsdsed ----------------------+-------------------------------- Reporter: ionic@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: invalid | Keywords: Port: texinfo | ----------------------+-------------------------------- Comment (by mojca@…): Do you have any pointers to the relevant conversation? I would prefer to wait a tiny bit before closing this as invalid. It's not tooooo difficult to fix even if upstream disagrees to make any changes. In principle we could even "hardcode-replace" the `sed` with `gsed` to make the tool work in the first place. -- Ticket URL: <https://trac.macports.org/ticket/43617#comment:10> MacPorts <http://www.macports.org/> Ports system for OS X
#43617: texinfo: texi2dvi incompatible with bsdsed ----------------------+-------------------------------- Reporter: ionic@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: invalid | Keywords: Port: texinfo | ----------------------+-------------------------------- Comment (by ionic@…): Pointer: [https://www.mail-archive.com/bug-texinfo@gnu.org/msg06189.html Bug report answer] We could change the scripts to call `gsed`... but that would require to take a look at all binaries/scripts. Shall I rather do that? It would make `texinfo` more difficult to maintain, as one must check for new occurrences of `sed` in new files for instance. -- Ticket URL: <https://trac.macports.org/ticket/43617#comment:11> MacPorts <http://www.macports.org/> Ports system for OS X
#43617: texinfo: texi2dvi incompatible with bsdsed ----------------------+-------------------------------- Reporter: ionic@… | Owner: macports-tickets@… Type: defect | Status: reopened Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: texinfo | ----------------------+-------------------------------- Changes (by mojca@…): * status: closed => reopened * resolution: invalid => -- Ticket URL: <https://trac.macports.org/ticket/43617#comment:12> MacPorts <http://www.macports.org/> Ports system for OS X
#43617: texinfo: texi2dvi incompatible with bsdsed ----------------------+-------------------------------- Reporter: ionic@… | Owner: macports-tickets@… Type: defect | Status: reopened Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: texinfo | ----------------------+-------------------------------- Comment (by mojca@…): Committed in r121939. Once we confirm that it works properly the ticket may be closed. -- Ticket URL: <https://trac.macports.org/ticket/43617#comment:13> MacPorts <http://www.macports.org/> Ports system for OS X
#43617: texinfo: texi2dvi incompatible with bsdsed ----------------------+-------------------------------- Reporter: ionic@… | Owner: macports-tickets@… Type: defect | Status: reopened Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: texinfo | ----------------------+-------------------------------- Comment (by ionic@…): Works for me. -- Ticket URL: <https://trac.macports.org/ticket/43617#comment:14> MacPorts <http://www.macports.org/> Ports system for OS X
#43617: texinfo: texi2dvi incompatible with bsdsed ----------------------+-------------------------------- Reporter: ionic@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: texinfo | ----------------------+-------------------------------- Changes (by mojca@…): * status: reopened => closed * resolution: => fixed -- Ticket URL: <https://trac.macports.org/ticket/43617#comment:15> MacPorts <http://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts