Em Thu, May 10, 2012 at 12:45:08PM +0200, intrigeri escreveu: > backupninja upstream and Debian maintainer hat on: > I trust you to find a good long-term solution, > but the backupninja 1.0 release is currently blocked > by the remaining critical bugs in the rsync handler, > and the Wheezy freeze is coming *soon*, > so I now need to set a clear deadline: > > If the rsync handler is not in a good enough state on May 20th yet, > I'll release backupninja 1.0 *without* the rsync handler, > and upload it to Debian sid.
Seems fair and I hope we can do it. I just cycled over all backupninja rsync issues[1], checked their status and made the needed commits so now I think we can test a rsync handler candidate for the 1.0 release. I merged all my recent work in my rsync branch[2] which right now is merged with master. So the rsync handler can be either tested from the current code at my rsync branch[3] or use a diff from from backupinja shipped on debian squeeze. I'm deploying the current rsync handler code on my systems to see if it's stable enough. Paul, could you also test this new version? [1] https://labs.riseup.net/code/projects/backupninja/issues [2] https://git.sarava.org/?p=backupninja.git;a=shortlog;h=refs/heads/rsync [3] https://git.sarava.org/?p=backupninja.git;a=blob_plain;f=handlers/rsync.in;hb=refs/heads/rsync -- rhatto at riseup.net pubkey 64E39FCA / keys.indymedia.org
signature.asc
Description: Digital signature
