From owner-freebsd-current  Sat Aug 19 14:35:34 1995
Return-Path: current-owner
Received: (from majordom@localhost)
          by freefall.FreeBSD.org (8.6.11/8.6.6) id OAA09806
          for current-outgoing; Sat, 19 Aug 1995 14:35:34 -0700
Received: from id.slip.bcm.tmc.edu (hou05.onramp.net [199.1.137.133])
          by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id OAA09777
          for <FreeBSD-current@freefall.FreeBSD.org>; Sat, 19 Aug 1995 14:35:28 -0700
Received: (from rich@localhost) by id.slip.bcm.tmc.edu (8.6.11/8.6.9) id QAA00830; Sat, 19 Aug 1995 16:35:23 -0500
Date: Sat, 19 Aug 1995 16:35:23 -0500
From: Rich Murphey <rich@lamprey.utmb.edu>
Message-Id: <199508192135.QAA00830@id.slip.bcm.tmc.edu>
To: FreeBSD-current@freefall.FreeBSD.org
In-reply-to: <199508191935.MAA00275@gndrsh.aac.dev.com> (rgrimes@gndrsh.aac.dev.com)
Subject: Re: sup/cvs interactions?
Reply-to: rich@lamprey.utmb.edu
Sender: current-owner@FreeBSD.org
Precedence: bulk


It was partly pilot error after all.  I didn't take into
consideration the 2 hour difference in time zones.

The files actually had the same time stamp but 'ls -l'
showed different times in different zones (PST and CST).

|From: "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com>
|> Sup ignores files that are older on the server than on the
|> client, so it wouldn't pick up this kind of change.
|
|This depends on sup options.

Yep, you mentioned the 'keep' option forces this, but I
wasn't using 'keep'.

|> I'm seeing this once in a while.. Rich
|
|Do you have ``old'' in your supfile lines?  Or do you run sup -o?
|
|       -o	Sup will normally  only  upgrade  files  that  have
|		changed  on  the  repository since the last time an
|		upgrade was performed. That is, if the file in  the
|		repository  is  newer  than  the date stored in the
|		when file on the client.  The -o flag, or  the  old
|		supfile  option,  will cause sup to check all files
|		in the collection for changes instead of  just  the
|		new ones.


OK, I did have both 'old' in the supfile and -o on the
command line but sup didn't updates files which had bad
checksums.

Rod has suggested I reinstall sup from the sources and see
if that makes a difference.  I'll try to see whether I can
repeat it.   Rich