Re: Current MacCvsX a3 problem

Am 17.10.2004 um 20:41 schrieb Alexandre Parenteau:

>
> Hi,
>
> I'm getting a new error I have never seen before. When a file needs an
> update, but I modified it, cvs will copy the file foo.c to a new 
> #.foo.c.35
> (or something like that).
>
> During this operation the copy fails with error -35 (not such volume). 
> Note
> also that my sandbox is not on the main drive, I'm using 10.3.5.
>
> I verified it is still working with a2.
>
> Now could someone tell me why the copy of a mac file had to change in
> cvs-1.10, and what was done about it ?

Sure, I can tell you:
The old way of backing up files that were modified did not copy the 
resource forks, so essentially, your resource forks were lost and this 
may render the backup copy useless in some cases (especially if the 
resource fork is all you cared about, like in pure resource files :(  )

I changed the code inside the cvsgui tool to call a Mac specific copy 
routine that would duplicate both data and resource fork (in fact, it'd 
attempt to copy _all_ available forks).

Is your repository on an UFS volume by any chance? That's one reason I 
could imagine why the new copy routine could fail. (Of course, this 
would be a bug in the copy routine, since it should be smart enough to 
handle non-HFS volumes...)

</jum>


[Non-text portions of this message have been removed]



------------------------ Yahoo! Groups Sponsor --------------------~--> 
Make a clean sweep of pop-up ads. Yahoo! Companion Toolbar.
Now with Pop-Up Blocker. Get it for free!
http://us.click.yahoo.com/L5YrjA/eSIIAA/yQLSAA/NhFolB/TM
--------------------------------------------------------------------~-> 

 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/cvsgui-dev/

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/