Re: [rdiff-backup-users] Maintenance

[Dominic Raferd]

Ned, re the verification issue, I suggest you look back in mailing list archives to a post entitled 'Verify times increasing' by Daniel Miller on 20 November 2009, and the follow-up posts. He then started a thread 'Implementing new features' on 3 February 2010 and then a thread 'New feature: --verify-full' on 11 February 2010. Lastly a thread 'Restarting development ... or starting over' on 5 April 2010.

Daniel coded a modified version of rdiff-backup which allowed full subsequent verification, but then started a new project to match and improve on the features of rdiff-backup which AFAIK was never published. You might be able to reach him for more info.

I know nothing about the internal coding of rdiff-backup, I'm afraid, maybe someone else here does?

Dominic

On 28/04/2013 18:34, Edward Ned Harvey wrote:

From: Dominic Raferd [mailto:address@hidden]

I might
be able to get you an email address for him though. Failing that I guess

you

could create a fork.

Thanks, I was able to reach Ben Escoto, who gave me an address for Andrew @
princeton.edu.  Ben has long since been a non-maintainer, but he at least
still has admin access to the project, so if Andrew proves to be unavailable
for some reason, we should be able to at least able to resurrect access
without being forced into the fork.  

That was only today, so the fact that I don't have a response yet is
irrelevant.  The fact that I don't have a bounce yet is highly relevant.
;-)  Still, if you've got another address for Andrew, that would be
appreciated.

There is a wish-list somewhere (quite a long and old one I'm afraid). 

That's the thing about volunteer effort.  People are motivated to work on
whatever they care about.   ;-)

Some of the recurrent issues relate to backups to/on Windows filesystems

or

saving/recovering Windows ACLs. 

Unfortunately, I think I'm unlikely to focus much on the windows side of
things...  I personally pay $17 to goodsync once every couple of years and
I'm happy with that for windows.

One serious failing in rdiff-backup is
its verification procedures which are rather inadequate.

That does sound important.  Could you expand?  (I haven't dug into source
much yet.)

Someone else looked at the rdiff-backup codebase a while back and said it
was very untidy and repetitious and they lost interest in updating it.

Just

warning you before you get stuck in! But you would be performing a great
service...

Yeah, in the quick look I had already at the source code, there seemed to be
a lot of indirection ... Which is confusing without a map, but if there's a
good block diagram illustrating the interfaces between the zillion tiny
little classes etc, that goes a long way toward making it all clear.

--
TimeDicer: Free File Recovery from Whenever