> The post above seems to describe a problem that happened repeatably over a > wireless connection but not so far wired. I don't know why, but maybe the > connection was intermittent and sbackup does not catch breaks in the > connection. > So I don't claim this is a problem that has been introduced in fixing the > current bug.
So this might be a problem of sbackup not handling connection breakage . I though it was a problem with gnomevfs too, but I can understand that there is a problem if the connection breaks . Maybe you must fill it as another bug ... > > There is still one remaining problem I've seen (two posts ago) with your > fix. I think I have fixed it (if the problem you're talking about is the "gnomevfs.NotFoundError: File not found" one ). we have also changed the behaviour so that incomplete snapshots are not removed automatically . > > When that is wrapped up and a fixed version appears on Feisty's servers > as a bug-fix push, I'd like to send you (Ouattara) a token payment for > your help with this (if that doesn't contradict any launchpad policies). > > Thanks! > c > Ohh :-) that's so generous of you. What I like the most is to see people happy when I try to solve bugs . That's my main payment :-) FYI , I don't think launchpad has any problem with that. ( https://launchpad.net/legal ) -- gnomevfs.NotFoundError even when the "test" works in remote backup site https://bugs.launchpad.net/bugs/67814 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
