From owner-freebsd-hackers Wed May 14 04:53:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA22803 for hackers-outgoing; Wed, 14 May 1997 04:53:12 -0700 (PDT) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA22793 for ; Wed, 14 May 1997 04:53:08 -0700 (PDT) Received: from [208.2.87.4] (cod.dataplex.net [208.2.87.4]) by shrimp.dataplex.net (8.8.5/8.8.5) with ESMTP id GAA12276; Wed, 14 May 1997 06:52:39 -0500 (CDT) X-Sender: rkw@shrimp.dataplex.net Message-Id: In-Reply-To: <19970514124231.YX61637@uriah.heep.sax.de> References: <199705121339.IAA17025@sparcmill.grauel.com>; from Richard J Kuhns on May 12, 1997 08:39:25 -0500 <199705121339.IAA17025@sparcmill.grauel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 14 May 1997 06:53:08 -0500 To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) From: Richard Wackerbarth Subject: Re: Problem getting up-to-date with 2.2 using CTM Cc: hackers@FreeBSD.ORG, rjk@sparcmill.grauel.com (Richard J Kuhns) Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 5:42 AM -0500 5/14/97, J Wunsch wrote: >As Richard J Kuhns wrote: > >> I followed the instructions in src-2.2-CTM-README on ftp.freebsd.org; it >> said that if I wanted to update 2.2.1, I needed to start with >> src-2.2.0217.gz. I tried, with the following results. >> >> : adler$~; cd /usr/src >> : adler$/usr/src; echo "src-2.2 216" > .ctm_status >> : adler$/usr/src; ctm -v /usr2/2.2/src-2.2.02* >> Working on >> FN: release/sysinstall/help/hardware.hlp md5 mismatch. >> FN: release/sysinstall/help/hardware.hlp edit fails. >> Exit(104) > >I think the problem with this is that the releases itself aren't being >built from a distinct CTM delta base. Thus, it's very hard to >maintain synchronization between the CTM batching and the actual >release build process. However, the CTM base delta was built from the release (as posted by Jordan) Particularly because the error is in a sysinstall help file, I suspect that Jordan changed something changed and the release that was placed on the CD did not match to one I was told would be there. When I get back home and can examine the CD, I'll build a base from it. In the interim, you can manually force your way past the problems by deleting the offending entries and forcing the update.