Thu, 28 Nov 2002 22:54:58 +0000
Thanks for the reply. Sorry I have got back earlier but I've been rushed
off my feet this week. I've just had another go doing exactly what I was
doing earlier, apparently with some success. So whatever was going wrong
isn't any more.
It could be a network issue (although that would seem unlikely), it
could be Eclipse (but an identical setup at work is fine), and it could
be Crosswire (but nothing seems to have changed there)! So I'm at a loss.
I'll monitor things and tell you if I see any more.
Sorry if I caused any unnecessary alarm.
Troy A. Griffitts wrote:
> I've looked at the repository and it looks just fine. I never
> knew ci was shorthand for commit :) What exactly is the problem? Can
> you checkout the repository to another directory, change
> JDBCBibleUtil.java and then commit it? Can anyone else on the jsword
> team? It might be that you have a corrupted checkout and may just
> need a fresh one. Are you switching between OSes on the same cvs
> checkout? CVS will get confused about conversions it needs to do, if so.
> Joe Walker wrote:
>> And I'm more that a little concerned to see that I'm getting some
>> truncated files.
>> Troy - any ideas?
>> Joe Walker wrote:
>>> CVS is probably not very buildable right now.
>>> I'm trying to check-in a large set of changes, but I keep seeing:
>>> cvs -q ci -m "message"
>>> ok (took 0:00.406)
>>> Info: The modification timstamp was changed for
>>> but the contents match that of the server. The timstamp has been reset.
>>> So half my stuff has gone in, and the other half has not. Clearly
>>> don't expect a CVS checkout to even think about compiling cleanly.
>>> Any ideas what is going wrong?
>>> jsword-devel mailing list
>> jsword-devel mailing list
> jsword-devel mailing list