Date: Mon, 10 Jan 2000 15:18:47 -0800 (PST) From: superboy@LSH.org To: freebsd-gnats-submit@FreeBSD.org Subject: gnu/16045: groff 1.11 Y2K bug Message-ID: <20000110231847.32FFD152B7@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 16045 >Category: gnu >Synopsis: groff 1.11 Y2K bug >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Jan 10 15:20:03 PST 2000 >Closed-Date: >Last-Modified: >Originator: Russ Smith >Release: 3.4 for i386 >Organization: Network Flight Recorder, Inc. >Environment: FreeBSD valkyrie.nfr.net 3.4-RELEASE FreeBSD 3.4-RELEASE #6: Wed Jan 5 21:14:09 CST 2000 russ@valkyrie.nfr.net:/usr/src/sys/compile/VALKYRIE i386 >Description: Simple enough: 3.4 ships with groff 1.11. This lacks a y2k fix purportedly in more recent versions. In short, the date turns up as 1900. :P >How-To-Repeat: Reference the builtin register \*(td, which should have today's date. >Fix: Upgrade. I installed the current version, groff 1.15, and it works (well, it gets the date right, at any rate). >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000110231847.32FFD152B7>