On Wed, Apr 13, 2011 at 11:17:18AM -0400, Desjardin, Donald wrote:
> In the following example we have sym-links called CURRENT_BLAH_BLAH that
> point to the correct firmware file.  During the checkout, if the
> destination has been created before the link, it works, if the link
> happens to get created first, it fails:
> 
>       $ svn co http://svn/ftLinux/trunk/ftl_linux/firmware
>       A    firmware/bios
>       A    firmware/bios/062-02799bios5.0.16.rom
>       A    firmware/bios/062-02799bios5.0.17.rom
>       A    firmware/bios/CURRENT_DRACO_BIOS           <- worked
>       A    firmware/bios/bios.spec.in
>       A    firmware/bios/Makefile
>       A    firmware/Makefile
>       A    firmware/bmc_fw
>       A    firmware/bmc_fw/CURRENT_DRACO_BMC_FW               <- about
> to FAIL
>       A    firmware/bmc_fw/062-02799bmc_b00.00r03.16p01.05s01.03.bin
>       A    firmware/bmc_fw/062-02799bmc_b00.00r03.17p01.05s01.03.bin
>       A    firmware/bmc_fw/bmc_fw.spec.in
>       A    firmware/bmc_fw/Makefile
>       svn: In directory 'firmware/bmc_fw'
>       svn: Can't move 'firmware/bmc_fw/CURRENT_DRACO_BMC_FW.tmp' to
> 'firmware/bmc_fw/CURRENT_DRACO_BMC_FW': No such file or directory

See this item in the issue tracker:
http://subversion.tigris.org/issues/show_bug.cgi?id=3053

Reply via email to