Date: Wed, 14 May 1997 12:42:31 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Cc: rjk@sparcmill.grauel.com (Richard J Kuhns) Subject: Re: Problem getting up-to-date with 2.2 using CTM Message-ID: <19970514124231.YX61637@uriah.heep.sax.de> In-Reply-To: <199705121339.IAA17025@sparcmill.grauel.com>; from Richard J Kuhns on May 12, 1997 08:39:25 -0500 References: <199705121339.IAA17025@sparcmill.grauel.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 </usr2/2.2/src-2.2.0217.gz> > 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. You might get more luck with CVSup in this case, since it can handle mismatching files (and will at worst retransfer them entirely, something CTM cannot do since it's operating offline). -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970514124231.YX61637>