travis+ml-rsync at subspacefield.org
2011-Mar-12 02:41 UTC
two bugs in rsync 3.0.6 - ampersands in filenames, double quoting required
1) deleting path/to/(Something) Word Word Anotherword--Word Word.pdf IO error encountered -- skipping file deletion I think either the -- is causing it to fail, or more likely, the next filename, which it didn't bother to print out, which has an ampersand in the name, causes it to fail. I am using SSH as a substrate, of course, and I think you guys failed to escape things, so the ampersand is hosing your protocol somehow. 2) I am also aware that when rsyncing to a foreign system, you have to "double escape" filenames - if the target has a space in it, you must use not one, but two sets of quotes. Since you can't nest double quotes or single quotes, this means that you have to use both. This is fairly annoying, for a number of reasons, including the difficulty of doing variable substitution (single quotes prevent it, so you gotta bust out for the variable and then back in), and the fact that it's not intuitive at all. -- I'm not sleeping; I'm regenerating. | http://www.subspacefield.org/~travis/ My emails do not usually have attachments; it's a digital signature that your mail program doesn't understand. If you are a spammer, please email john at subspacefield.org to get blacklisted. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 834 bytes Desc: not available URL: <http://lists.samba.org/pipermail/rsync/attachments/20110311/2411ea89/attachment.pgp>
travis+ml-rsync at subspacefield.org
2011-Mar-12 03:00 UTC
maybe a Unicode problem? was Re: two bugs in rsync 3.0.6 - ampersands in filenames, double quoting required
On Fri, Mar 11, 2011 at 06:41:26PM -0800, travis+ml-rsync at subspacefield.org wrote:> deleting path/to/(Something) Word Word Anotherword--Word Word.pdf > IO error encountered -- skipping file deletion > > I think either the -- is causing it to fail, or more likely, the next > filename, which it didn't bother to print out, which has an ampersand > in the name, causes it to fail. > > I am using SSH as a substrate, of course, and I think you guys failed > to escape things, so the ampersand is hosing your protocol somehow.Actually, I'm unable to replicate the error with some test files with the exact same names. Just to test the escaping, I tried creating this dir: (Word) Word Word Word--Word & Word (Word Word.).ext id&"id& id&"id&`id` I was expecting to find some shell-escapes, so I threw those last two in for good measure. I was able to create and delete those filenames on the target properly. So I didn't find the shell escape I was looking for. This time it failed when trying to delete a file containing the word G\#303\#266del I wonder if there's some issues with Unicode... -- I'm not sleeping; I'm regenerating. | http://www.subspacefield.org/~travis/ My emails do not usually have attachments; it's a digital signature that your mail program doesn't understand. If you are a spammer, please email john at subspacefield.org to get blacklisted. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 834 bytes Desc: not available URL: <http://lists.samba.org/pipermail/rsync/attachments/20110311/0bdd44ad/attachment.pgp>
alex conway
2011-Mar-12 20:39 UTC
two bugs in rsync 3.0.6 - ampersands in filenames, double quoting required
fuck off On Sat, Mar 12, 2011 at 2:41 AM, <travis+ml-rsync at subspacefield.org> wrote:> 1) > > deleting path/to/(Something) Word Word Anotherword--Word Word.pdf > IO error encountered -- skipping file deletion > > I think either the -- is causing it to fail, or more likely, the next > filename, which it didn't bother to print out, which has an ampersand > in the name, causes it to fail. > > I am using SSH as a substrate, of course, and I think you guys failed > to escape things, so the ampersand is hosing your protocol somehow. > > 2) > > I am also aware that when rsyncing to a foreign system, you have to > "double escape" filenames - if the target has a space in it, you must > use not one, but two sets of quotes. Since you can't nest double > quotes or single quotes, this means that you have to use both. > > This is fairly annoying, for a number of reasons, including the > difficulty of doing variable substitution (single quotes prevent it, > so you gotta bust out for the variable and then back in), and the fact > that it's not intuitive at all. > -- > I'm not sleeping; I'm regenerating. | > http://www.subspacefield.org/~travis/ > My emails do not usually have attachments; it's a digital signature > that your mail program doesn't understand. > If you are a spammer, please email john at subspacefield.org to get > blacklisted. > > -- > Please use reply-all for most replies to avoid omitting the mailing list. > To unsubscribe or change options: > https://lists.samba.org/mailman/listinfo/rsync > Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.samba.org/pipermail/rsync/attachments/20110312/f1344b63/attachment.html>
Seemingly Similar Threads
- HDB, a hard drive backup program
- Rails 2.3.5/Ruby1.8.7 Collection_Select Labels with ampersands "&"
- feature request: "remote user is root, make remote owner is foo"
- does rsync work in lockstep? parallel could improve high latency performance
- IO error encountered, skipping file deletion - WTF?