Hello Aigars, sorry for the late reply. Always a lot of work - I'm sure you know what I mean. Thanks for your commitment related to the bugfix for Lucid.
During the last months I've squashed as much open bugs as possible from nssbackup in order to prepare a final merge of sbackup and nssbackup that really satisfies both users of nssbackup and sbackup. Oumar and you agreed some time ago, that both applications should finally re-merge resp. nssbackup should `overtake` sbackup. I hope you still agree. IMO this is a really important step since lots of users of sbackup are getting more and more confused, annoyed and frustrated (and quit using sbackup). Unfortunately, I can understand why. SBackup is nearly unmaintained since 3 years now and does lack some features. Unfortunately, I was not able to get everything done till the Maverick feature freeze (this was my personal deadline for the merge). Release 0.11 will be identical with nssbackup 0.3. You can find the source of nssbackup here https://launchpad.net/nssbackup The current trunk (where I do the renaming and required modifications) of sbackup is located here https://launchpad.net/sbackup though I'm not sure whether the most recent revision runs flawless. In the case you do not know nssbackup's features, here's a brief summary: * proper error handling * log files * compressed and uncompressed snapshots * OOP * Fuse plugins (sshfs, curlftpfs) and GIO/GVFS backend * multiple tar volumes * support for multiple backup profiles * scheduled backups * runs also without superuser rights (schedules not yet supported) * revamped GUI incl. progress bars, improved interactivity (threading) * Help * desktop notifications * status indicator (status icon) which presents errors and stats * progress is displayed during a backup And yes, we do support multi-volume backups and it works well (backup and restore). Regarding the snapshot format: we will preserve compatibility all time between sbackup and nssbackup, as stated on the nssbackup homepage. The upgrade code in nssbackup is still yours. I hope this was informative for you and that you keep supporting Oumar, all contributors and me. I think the latest release is quite cool and deserves to replace the aged sbackup code. Of course, any contributions, suggestions or constructive discussions are welcome. Kind regards, Jean-Peer Am Mittwoch, den 04.08.2010, 23:20 -0400 schrieb Aigars Mahinovs: > Hello there, > > I saw that you are planing to release sbackup 0.11 with some bugfixes. > I thank you very much for that. Where can I see the code for it? > > BTW: does nssbackup do multifile backups? Like when you backup to > FAT32 no single file can be larger than 4Gb so there needs to be a way > to split the backup archive up. Have you guys solved this problem > already? I have coded a solution that writes multi-file backups > (separate tar.gz files, new file is started when the filesize of > uncompressed files is larger than 2Gb), but don't have the code yet > for the restore part. It would be nice if we could keep nssbackup able > to read sbackup backups even after this change, so I wanted to give > you a heads up. >
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
_______________________________________________ Mailing list: https://launchpad.net/~nssbackup-team Post to : nssbackup-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~nssbackup-team More help : https://help.launchpad.net/ListHelp
