Subject: | Pushing does not propagate failures from rsync |
Date: | Tue, 8 Sep 2009 15:49:26 -0400 |
To: | bug-App-SD [...] rt.cpan.org |
From: | Nelson Elhage <nelhage [...] MIT.EDU> |
[nelhage@phanatique:~/code/barnowl]$ git sd publish --to /tmp/foo/bar
Exporting a clone of this replica
Exporting records...
Exporting changesets...
Exporting resolution database
Exporting records...
Exporting changesets...
Publishing the exported clone of the replica to /tmp/foo/bar with rsync
rsync: writefd_unbuffered failed to write 4 bytes [sender]: Broken pipe (32)
rsync: mkdir "/tmp/foo/bar" failed: No such file or directory (2)
rsync error: error in file IO (code 11) at main.c(594) [receiver=3.0.5]
rsync: connection unexpectedly closed (9 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(600) [sender=3.0.5]
Publication complete.
[nelhage@phanatique:~/code/barnowl]$ echo $?
0
The question of whether it should do the 'mkdir -p' is potentially
another ticket, but it shouldn't be claiming success when the rsync
failed.