Comment 9 for bug 471385

As one of the contributors of the nssbackup project I want to give some information on the state of sbackup/nssbackup:

* the project sbackup is not actively maintained since more than 2 years now (the current version sticks to 0.10.5) and it is very likely (in fact it is pretty sure) that the original developer will not continue working on sbackup.

* nssbackup is a fork of the sbackup project. It shares the same ideas as sbackup but does not share code. It is fully rewritten. The main reason for the creation of this fork were differences between the developers regarding sbackup's behaviour and future. While the original sbackup author seems not very able to spend time on sbackup, some good job was done by the other developers on bugs and features. Also, with respect to the code base, sbackup is a dead-end.
After a discussion with Aigars Mahinovs, the founder of sbackup project, we agreed that nssbackup could and should be renamed in sbackup, taking over the sbackup project.

* the nssbackup-team (2 active developers at the moment) is denoted as maintainer for sbackup. However, we will not spend any effort into sbackup rather improving nssbackup and finally replacing sbackup in the repositories.

* at the moment we are still working on release nssbackup 0.2.

* Many of the bugs present in sbackup are fixed in nssbackup resp. doesn't exist there. So, please just give it a try and help making it better. You can use it as usual software including installing via package manager.
Have a look at the project's site at https://launchpad.net/nssbackup and at the FAQs: https://answers.edge.launchpad.net/nssbackup/+faqs.

Hope this helps - Thank you.

Jean-Peer (nssbackup-team)