bugConcurrent Versions System - Bugs: bug #59447, cvs update should pause after...

 
 

bug #59447: cvs update should pause after updating Entries with timestamp in the current timestamp

Submitted by:  None
Submitted on:  Wed 11 Nov 2020 06:42:28 AM UTC
 
Category:  Bug Fix (patch attached) Severity:  3 - Normal
Item Group:  None Status:  None
Privacy:  Public Assigned to:  None
Open/Closed:  Open Release: 
Fixed Release:  None Fixed Feature Release:  None
* Mandatory Fields

Add a New Comment (Rich Markup)
   

Comment Type & Canned Response:
       No canned response available

 

Wed 11 Nov 2020 06:42:28 AM UTC, original submission:  

The following sequence:

1. touch file
2. cvs update
3. echo 'new contents' > file
4. cvs commit -m 'new contents'

fails to commit in step 4 if steps 1, 2, and 3 all happen within the same second. The reason is that step 2 notices that file's timestamp has changed even though the contents have not and updates file's timestamp in CVS/Entries. In step 3 the contents change but the timestamp still matches the one-second-granularity timestamp in CVS/Entries. So in step 4 commit does not realize that file has changed.

The attached fix arranges to sleep until the clock has passed the timestamp of the newest entry that was updated.

Anonymous

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

Attached Files
file #50244:  sleep.patch added by None (3KiB - application/octet-stream)

 

Depends on the following items: None found

Items that depend on this one: None found

 

CC list is empty

 

There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

Only logged-in users can vote.

 

 

 

 

Follows 1 latest change.

Date Changed by Updated Field Previous Value => Replaced by
2020-11-11 None Attached File- => Added sleep.patch, #50244

Back to the top


Powered by Savane 3.9