Re: problem with update -d module/dir1/dir2/file1

[Steve_Shriver]

Hi, 

Also, the following shows the problem is clearly with update -d not 
creating the fullpath to a file as it is advertised to do: 

[release@lxdevweb2 vwr]$ rm -rf catalog/jpg/020
[release@lxdevweb2 vwr]$ cvs update -d catalog/jpg/020/thumb_020997.jpg
cvs [update aborted]: no such directory `catalog/jpg/020'
[release@lxdevweb2 vwr]$ cvs co catalog/jpg/020/thumb_020997.jpg
U catalog/jpg/020/thumb_020997.jpg
[release@lxdevweb2 vwr]$ ls -aCF catalog/jpg/020
CVS/  thumb_020997.jpg
[release@lxdevweb2 vwr]$ cvs update -d catalog/jpg/020/thumb_020998.jpg
U catalog/jpg/020/thumb_020998.jpg

Hope this helps, 
Steve 




The information contained in this e-mail message may be privileged, 
confidential and protected from disclosure. If you are not the intended 
recipient, any dissemination, distribution or copying is strictly 
prohibited. If you think that you have received this e-mail message in 
error please e-mail the sender and delete the message. Thank you. 

----- Forwarded by Steve Shriver/VWRI on 07/28/2009 03:20 PM -----

Steve Shriver/VWRI 
07/28/2009 02:31 PM

To
bug-cvs@nongnu.org
cc

Subject
problem with update -d module/dir1/dir2/file1





Hi, 

Spent a day or two searching thru google for answers to this problem. 
Thought I'd check with you guys too. 

$> cd /dir/local/repo
$> cvs update -d module/d1/d2/file1 

[release@lxdevweb2]$ cvs update -d catalog/jpg/010/thumb_010999.jpg
cvs [update aborted]: no such directory `catalog/jpg/010' 

[release@lxdevweb2]$ ls -aCF catalog/jpg
./  ../  000/  020/  CVS/


[release@lxdevweb2 vwr]$ cvs --version
Concurrent Versions System (CVS) 1.11.22 (client/server)


Seems to be related to the "trailing slash" bug that prevents "cvs update 
-d m1/d1/d2/" but works with "cvs update -d m1/d1/d2".  So do I need to 
test the path exists prior to update? Or put something in the CVS/Entries 
file? 

I'm trying to avoid a full checkout just to get a few files in a 
particular module's path. What are my options? 

Thanks,
Steve 




The information contained in this e-mail message may be privileged, 
confidential and protected from disclosure. If you are not the intended 
recipient, any dissemination, distribution or copying is strictly 
prohibited. If you think that you have received this e-mail message in 
error please e-mail the sender and delete the message. Thank you.