[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Up-to-date check failed for binary file

From: Mark D. Baushke
Subject: Re: Up-to-date check failed for binary file
Date: Mon, 06 Aug 2007 00:16:21 -0700

Hash: SHA1

Chris Velevitch <address@hidden> writes:

> On Aug 5, 10:14 pm, Chris Velevitch <address@hidden> wrote:
> > As I understand it, the error 'Up-to-date check failed' indicates that
> > the repository version is newer than the workspace version. 

Yes. A 'cvs update' will checkout try to update the file revision in
your local checked out tree.

> > However, this file is a binary file and I know it's the current
> > version. In my way of thinking, the repository is wrong for this
> > file. How do I fix it?

What does a 'cvs status' say? Is there really a newer revision in the
repository? If so, what does a 'cvs log' say about that revision number?

I suggest you checkout that file in a separate tree and examine it
to see for sure.

If you think you understand what is happening, you are probably wrong,
but you could do something as simple as

    mv file
    cvs update file
    mv file

to destroy the evidence and really screw up whoever had committed the
revision you didn't like. This is a bad solution most of the time.

> Also, the file is 3.5Mb in size. Is there any size issues for binary
> files?

For some operating systems there can be problems with files in excess of
2GB. This could be either the ,v file on the server or the individual
revision on the client. Those systems need large file support to get
files bigger than 2GB in size.

A 3.5MB file should not be a problem.

        -- Mark
Version: GnuPG v1.4.6 (FreeBSD)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]