"Checksum mismatch -- will transfer entire file"

Victor Sudakov sudakov+freebsd at sibptus.tomsk.ru
Thu Dec 31 04:32:58 UTC 2009


Colleagues,

I cvsup the FreeBSD CVS repository daily from cvsup.ru.freebsd.org.
Both the client and the server run CVSup Software version: SNAP_16_1h,
Protocol version: 17.0. 

Recently I noticed that there are lots of messages
"Checksum mismatch -- will transfer entire file" about all kinds of
downloaded files, e.g.


src/lib/libc/posix1e/acl_delete_entry.c,v: Checksum mismatch -- will transfer entire file
Bad version saved in /var/ncvs/src/lib/libc/posix1e/#cvs.cvsup-54795.92

When I diff the files, I see the following:

*** #cvs.cvsup-54795.92	2009-12-31 05:15:13.000000000 +0600
--- acl_delete_entry.c,v	2009-12-30 22:38:19.000000000 +0600
***************
*** 108,128 ****
  branches;
  next	;
  
- 1.7.24.1
- date	2008.10.02.02.57.24;	author kensmith;	state Exp;
- branches;
- next	;
- 
- 1.7.26.1
- date	2008.11.25.02.59.29;	author kensmith;	state Exp;
- branches;
- next	;
- 
- 1.7.28.1
- date	2009.04.15.03.14.26;	author kensmith;	state Exp;
- branches;
- next	;
- 
  1.8.2.1
  date	2009.08.03.08.13.06;	author kensmith;	state Exp;
  branches
--- 108,113 ----
***************
*** 139,144 ****
--- 124,144 ----
  branches;
  next	;
  
+ 1.7.24.1
+ date	2008.10.02.02.57.24;	author kensmith;	state Exp;
+ branches;
+ next	;
+ 
+ 1.7.26.1
+ date	2008.11.25.02.59.29;	author kensmith;	state Exp;
+ branches;
+ next	;
+ 
+ 1.7.28.1
+ date	2009.04.15.03.14.26;	author kensmith;	state Exp;
+ branches;
+ next	;
+ 
  
  desc
  @@
***************
*** 604,606 ****
--- 604,607 ----
  d32 1
  d34 1
  @
+ 

which probably means: 

1. There is an extra newline near the end of the RCS file.

2. The changes in the file are the same but placed in different
positions in the file? Not where cvsup expects the changes to be?

I was told this may be an artifact of importing changes in svn back
into cvs. Something goes wrong during the import, perhaps changes are
inserted in the wrong place in the RCS file. Is this problem known,
are there plans to fix it? Is svn2cvs used or something else?

-- 
Victor Sudakov,  VAS4-RIPE, VAS47-RIPN
sip:sudakov at sibptus.tomsk.ru


More information about the freebsd-hackers mailing list