From owner-freebsd-stable Sat Jun 10 11:51:14 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rr.gfoster.com (mf8-1-151.mgfairfax.rr.com [24.28.206.151]) by hub.freebsd.org (Postfix) with ESMTP id 3F7D937B86F for ; Sat, 10 Jun 2000 11:51:10 -0700 (PDT) (envelope-from gfoster@gfoster.com) Received: (from gfoster@localhost) by rr.gfoster.com (8.9.3/8.9.3) id OAA80391; Sat, 10 Jun 2000 14:51:00 -0400 (EDT) (envelope-from gfoster) From: Glen Foster MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sat, 10 Jun 2000 14:50:59 -0400 (EDT) To: stable@freebsd.org Subject: upgrading from 3.4-S to 4.0-S no longer works X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14658.35864.621233.152016@rr.gfoster.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Folks, The recent OpenSSH commits to 4.0-S seem to have broken the update path described in /usr/src/UPDATING. As of the 4.0-S of about 5 June it worked, but it appears that it is no longer possible to build a 4.0 world on a 3.4 machine. The answer, of course, is to cvsup the sources before the 2.x SSH stuff went in using the date= directive or get to 4.0-R before going to 4.0-S. Yes, I know the update wasn't supposed to have worked forever and I'm not complaining. I just thought this might save someone the hour or so it takes to find out the hard way. Glen Foster To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message