cvs client: refetching unpatchable files

[James Croxford]

Hello,

Don't if you can help but I am having a problem with CVS. This message keeps
appears on the log;

P CRMQU.src
cvs client: refetching unpatchable files
U CRMQU.src

It seems CVS is having a problem patching this file (amongst others),
however it then updates the file instead, which is obviously good in that we
get the end result.

The version of the CVS command we have is 1.11

I need to understand why a patch would fail, or at least some of the
possible reasons, and ideally would like to fix this so the patch works if
at all possible.

Is any one able to help? 

With Regards,

James Croxford*
 Disclaimer

This email transmission is confidential and intended solely for the
person or organization to whom it is addressed. If you are not the
intended recipient, you must not copy, distribute or disseminate the
information, or take any action in reliance of it. Any views expressed
in this message are those of the individual sender, except where the
sender specifically states them to be the views of any organization or
employer. If you have received this message in error, do not open any
attachment but please notify the sender (above) deleting this message
>from your system. Please rely on your own virus check no
responsibility is taken by the sender for any damage arising out of
any bug or virus infection.
*___
Bug-cvs mailing list
Bug-cvs@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-cvs

Re: cvs client: refetching unpatchable files

[Larry Jones]

James Croxford writes:
> 
> This is a multi-part message in MIME format.

Please do not send MIME and/or HTML encrypted messages to the list.
Plain text only, PLEASE!

> The version of the CVS command we have is 1.11

That version is ancient -- the current stable release is 1.11.20!  I
strongly suggest upgrading both the client(s) and the server (although
the server is most important): .  That may well
fix the problem.

> I need to understand why a patch would fail, or at least some of the
> possible reasons, and ideally would like to fix this so the patch works if
> at all possible.

The usual reason is that something has changed the file without changing
the timestamp.

> *
>  Disclaimer

Such disclaimers on messages sent to public mailing lists are silly at
best.  Please give your lawyers a cookie and put them in a nice padded
room where they won't hurt themselves or annoy others.

-Larry Jones

The living dead don't NEED to solve word problems. -- Calvin


___
Bug-cvs mailing list
Bug-cvs@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-cvs