← Back to team overview

nssbackup-team team mailing list archive

Re: [Question #62529]: why conflict with sbackup?

 

Question #62529 on NSsbackup changed:
https://answers.launchpad.net/nssbackup/+question/62529

    Status: Open => Answered

Jean-Peer Lorenz proposed the following answer:
Hey Anton,

I want to try to answer your questions.

>However, sbackup currently seems slightly more stable and reliable.

I really don't think so. In my opinion sbackup contains many (partly
blocker) bugs and does not create reliable backups. This was the reason
for me to turn to NSsbackup.


>So, the question is, why is this listed as a conflict?

Since both packages have the same purpose it is nor reasonable neither
useful for `end-users` to install them beside each other. Main reason
might be the backup format: NSsbackup is compatible with sbackup i.e. it
uses mainly the same configuration file structure (that's actually all).
But this does not mean that sbackup is able to handle data that was
created by NSsbackup.


>Are there really things that are incompatible between them?

In fact, due to sophisticated features provided by NSsbackup here is a
completelly different backup format in use. You can upgrade your
existing backups with the help of NSsbackup, but there is no possibility
to read such backups in sbackup again. So, in my opinion (and from the
view of end-users) the packages conflict.


>but should that not be up to the users (or distro builders) to decide?

Of course, and the user can decide all the time. You can install
NSsbackup (this removes sbackup) and test it, whether it meets your
needs. As a smart user, one shouldn't do this with important data ;) The
software is eventually crappy. Now, you can decide to use it or to go
back to sbackup. If you decide to use NSsbackup you can manually upgrade
your exsiting backups. If not, you can re-install sbackup (this removes
NSsbackup) and everything is as it was before.


>I'd therefore like to use sbackup, while working on nssbackup.

No problem, you can do so. You can work on the source code and use
sbackup. (You cannot and should not modify the files installed from a
Debian package, of course!)


Some questions from me:

What are you actually going to work on?
Would you help translating NSsbackup?
Before implementing new features the is a lot of work to be done related to documentation, website etc. Do you have some time/experience?

Thank you, HTH.
Jean-Peer

-- 
You received this question notification because you are a member of
NSsbackup team, which is an answer contact for NSsbackup.