groff
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Doubts about a typo fix


From: Paul Eggert
Subject: Re: Doubts about a typo fix
Date: Sat, 26 Nov 2022 18:32:09 -0800
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2

On 2022-11-26 13:56, G. Branden Robinson wrote:

A lot of the pieces are in place to make this work (Deri and I have
wrangled over gropdf's diagnostic messages in this very area, but I
think we reached consensus :D ), but it needs integration testing under
multiple scenarios.

In the meantime I filed an Ubuntu bug here:

https://bugs.launchpad.net/ubuntu/+source/groff/+bug/1998031

Unfortunately I don't have an Ubuntu 22.10 host that's public. The GCC Compile Farm has a 22.04 host; perhaps that's good enough.


I believe Solaris troff to be fossilized

Yes and no. Solaris 10 is no longer supported after January 2024, so if it and all the other traditional troffs die out by 2024 we can stop worrying about this then.

Solaris 11.4, the only Oracle Solaris version that is planned to be supported after January 2024, is based on groff 1.22.3 instead of on traditional troff. See:

https://docs.oracle.com/cd/E88353_01/html/E37839/troff-1.html
https://www.illumos.org/issues/12692


Oh, and one more thing. And this is relevant to TZDB! Ubuntu's groff ignores the TZ environment variable; see:

https://bugs.launchpad.net/ubuntu/+source/groff/+bug/1908333

This is apparently due to Ubuntu's reproducible-build folks going off the deep end. For example, on Ubuntu 22.10:

$ echo $TZ; date; echo '\n[year]-\n[mo]-\n[dy] \n[hours]:\n[minutes]:\n[seconds]' | groff -Tascii | grep .

Sat Nov 26 18:30:29 PST 2022
2022-11-27 2:30:29

I hope upstream groff never does this....



reply via email to

[Prev in Thread] Current Thread [Next in Thread]