Your message dated Tue, 1 Nov 2011 16:51:09 +0300
with message-id
<CAFFwCaRkyLekYvaCN2Za+u5XqV_6iQSrf-JUqWdZ=HYFJGcv=q...@mail.gmail.com>
and subject line merged with sbackup
has caused the Debian Bug report #511118,
regarding ITP: nssbackup -- a simple backup solution intended for desktop use.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
511118: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=511118
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
* Package name : nssbackup
Version : 0.2 RC2
Upstream Author : Jean-Peer Lorenz <[email protected]>
* URL : https://launchpad.net/nssbackup
* License : GPL v3
Programming Lang: Python
Description : a simple backup solution intended for desktop use.
NSsbackup (Not So Simple Backup suite ) is a fork of sbackup (Simple Backup
suite ) .
The main reason for the creation of this fork is the difference between the two
actual developers of sbackup
behavior.While the sbackup author seems not very able to spend some time on
sbackup, there were some job being done by
the other developpers on bugs and features. This was fine till we happen to get
to some point where we need a work on
both side ( project keys decision, packaging, distributing ).
NSsbackup is a OOP (Object Oriented Programing) version of sbackup I have
started in Sbackup svn repository. The
project has the same intend of sbackup, but with new features (handling of
logs, plugins architecture ... )
So basically, it's up to you to choose either NSsbackup or Sbackup (they are
doing the same job with some little
changes ).
-- System Information:
Debian Release: 5.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
--- End Message ---
--- Begin Message ---
--- End Message ---
