On Sat, 2009-09-12 at 23:24 +0100, Ganesh Sittampalam wrote:
Darcs already has a WIN32-specific workaround for renaming going wrong
when the new file exists, and my initial guess was that was what was going
wrong here.
BTW, this is not necessary afaik. Rename over an existing file works
[Due to circumstances beyond my control, I cannot CC the OP. Sorry.]
Jason Dagit da...@codersbase.com writes:
[Darcs] assumes that when your OS is [POSIX], all your mounted
volumes will natively support POSIX.
Some CIFS servers (namely, Samba) *do* implement POSIX semantics. I
take it to OP
On Sat, Sep 12, 2009 at 5:22 PM, Trent W. Buck trentb...@gmail.com wrote:
Ew. I'm not keen on calling mv(1) to handle each rename, let alone via
sh (which WILL explode on some paths, and allow injection attacks).
rawSystem does not use sh (hence the raw)
--Max
trentb...@gmail.com (Trent W. Buck) writes:
I'm also puzzled as to why this works -- surely mv(1) assumes POSIX
semantics, too? I would be interested in seeing the exact error
transcript, preferably as an issue on bugs.d.n. I'm not sure the
problem has been diagnosed correctly.
Well, not
On Sep 12, 2009, at 11:22 , Trent W. Buck wrote:
Jason Dagit da...@codersbase.com writes:
which ensures that when the operating system is not WIN32, that
renaming of files will be performed by the OS shell.
I'm also puzzled as to why this works -- surely mv(1) assumes POSIX
semantics, too? I
On Sat, 12 Sep 2009, Brandon S. Allbery KF8NH wrote:
On Sep 12, 2009, at 11:22 , Trent W. Buck wrote:
Jason Dagit da...@codersbase.com writes:
which ensures that when the operating system is not WIN32, that
renaming of files will be performed by the OS shell.
I'm also puzzled as to why this
On Sep 12, 2009, at 18:24 , Ganesh Sittampalam wrote:
On Sat, 12 Sep 2009, Brandon S. Allbery KF8NH wrote:
In order to handle the case where you're moving across filesystems,
mv(1) gracefully degrades to cp + rm. rename(2) does not. This
also happens to work around compatibility issues
Thanks to everyone who pointed me in the right direction on this problem, I
have been able to find a work around that allows me to push to an archive on a
network file share.
After some digging, I discovered the root of the problem. Briefly, Darcs uses
the standard library System.Directory
Hi Darrell,
This message definitely also belongs on the darcs-us...@darcs.net mailing
list. You can find information about how to subscribe here:
http://lists.osuosl.org/mailman/listinfo/darcs-users
Please join our list! I'm adding the list to the CC list in my reply.
On Fri, Sep 11, 2009 at
