[Duplicity-tracker] [bug #21896] Two problems with rsync under 0.4.8 + patch

[Peter Schuller]

Follow-up Comment #3, bug #21896 (project duplicity):

I have to say that the use of --delete to begin with feels very dangerous,
specifically because misstakes can have huge effects (nuking /, or nuking your
~, etc). Of course if the backend is struly rsync only --delete has to be
used. But perhaps it could be used on individual files only, specifically
identified, rather than on on a full directory synch.

As for the file, I have no clue why it's being opened. It's being deleted in
"most" cases (i.e., when there are no failures) since it's added to the
to_delete list. But I don't see the use of it.

Perhaps there is history we're missing. Last change of that line was cosmetic
in revision 1.19, and before that I'm not sure.


    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?21896>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/