Date: Fri, 16 Nov 2001 18:10:10 -0800 From: "Bruce A. Mah" <bmah@FreeBSD.ORG> To: Joe Clarke <marcus@marcuscom.com> Cc: freebsd-stable@FreeBSD.ORG Subject: Re: -stable release documents are corrupt Message-ID: <200111170210.fAH2AAT60542@c527597-a.cstvl1.sfba.home.com> In-Reply-To: <20011116203557.J70341-100000@shumai.marcuscom.com> References: <20011116203557.J70341-100000@shumai.marcuscom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--==_Exmh_628274786P Content-Type: text/plain; charset=us-ascii If memory serves me right, Joe Clarke wrote: > I didn't see this reported yet, but I noticed the release documents (e.g. > RELNOTES, ERRATA, HARDWARE, etc.) for today's -stable snapshot are all > opaque data files. CVS looks fine, but I wanted to let people know in > case somethings broken with the release process. Confirmed. Well, partially. ERRATA.TXT looks intact and nominally matches up with what I'd expect to see. The others are FUBAR-ed. I suspect something on the machine used for building the snapshots...I rolled a release at home yesterday and its *.HTM and *.TXT files look OK and no one's made any drastic changes to the release documents since then. jkh is the only person I know of who can go in and diagnose/fix any problems though. Until this is fixed, you can try snapshots.jp.freebsd.org...their latest 4-STABLE snapshot looks intact. (They give you the PDF renditions of the release documents too!) Bruce. --==_Exmh_628274786P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: Exmh version 2.3.1+ 05/14/2001 iD8DBQE79ccB2MoxcVugUsMRAvLTAKCVUL6EF/kkN/7f+9nQgGzwxofgEQCbB3PO dXc1E/pmiIvuVTu4tnSEdiQ= =MUDN -----END PGP SIGNATURE----- --==_Exmh_628274786P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200111170210.fAH2AAT60542>