Question #186812 on sbackup changed:
https://answers.launchpad.net/sbackup/+question/186812
Jean-Peer Lorenz posted a new comment:
Hello Bill,
sorry for the delay.
Yes, you should be able to extract file using just plain TAR.
Could you provide the error message of Archive manager? Maybe your
Thanks for your help. I've applied the fix to 0.11.4 and committed it to
lp:sbackup/0.11. I'll prepare a bugfix release asap. Any help would be
appreciated.
** Changed in: sbackup
Status: Incomplete = Fix Committed
--
You received this bug notification because you are a member of Simple
** Changed in: sbackup
Status: New = Confirmed
--
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to sbackup.
https://bugs.launchpad.net/bugs/875634
Title:
sbackup's tar very slow due to erroneous backup size calculation
To
Thanks for reporting this issue and helping to make sbackup better.
Could you please test whether this bug is still valid using the latest release
of sbackup (0.11.4)?
If this issue still exists please feel free to reopen it. Thank you.
** Changed in: sbackup (Ubuntu)
Status: New =
** Changed in: sbackup (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to sbackup in Ubuntu.
https://bugs.launchpad.net/bugs/221603
Title:
sbackupd.py crashed with error in _compile()
To
Thanks for reporting this issue and helping to make sbackup better.
Could you please test whether this bug is still valid using the latest release
of sbackup (0.11.4)?
If this issue still exists please feel free to reopen it. Thank you.
** Changed in: sbackup (Ubuntu)
Status: New =
Thanks for reporting this issue and helping to make sbackup better.
Could you please test whether this bug is still valid using the latest release
of sbackup (0.11.4)?
If this issue still exists please feel free to reopen it. Thank you.
** Changed in: sbackup (Ubuntu)
Status: New =
Thanks for reporting this issue and helping to make sbackup better.
Could you please test whether this bug is still valid using the latest release
of sbackup (0.11.4)?
If this issue still exists please feel free to reopen it. Thank you.
** Changed in: sbackup (Ubuntu)
Status: New =
Thanks for reporting this issue and helping to make sbackup better.
Could you please test whether this bug is still valid using the latest release
of sbackup (0.11.4)?
If this issue still exists please feel free to reopen it. Thank you.
** Changed in: sbackup (Ubuntu)
Status: New =
Thanks for reporting this issue and helping to make sbackup better.
Could you please test whether this bug is still valid using the latest release
of sbackup (0.11.4)?
If this issue still exists please feel free to reopen it. Thank you.
** Changed in: sbackup (Ubuntu)
Status: New =
Thanks for reporting this issue and helping to make sbackup better.
Could you please test whether this bug is still valid using the latest release
of sbackup (0.11.4)?
If this issue still exists please feel free to reopen it. Thank you.
** Changed in: sbackup (Ubuntu)
Status: New =
Thanks for reporting this issue and helping to make sbackup better.
This is a valid feature request, comments are welcome.
Thank you.
** Changed in: sbackup (Ubuntu)
Status: New = Opinion
** Summary changed:
- annoying modal dialog pops up if destination directory does not exist
+
Thanks for reporting this issue and helping to make sbackup better.
This bug was introduced in version 0.11.3 which is packaged in Ubuntu
10.10. It is fixed in sbackup 0.11.4 in current Ubuntu releases. Please
update. (Altenatively, you can use sbackup's latest version from our
PPA, have a look
Valid for sbackup series 0.10. However, needs verification of both bug
and patch. Anyhow, setting the status to confirmed.
** Summary changed:
- sbackup ignores maxsize setting
+ sbackup 0.10.5 ignores maxsize setting
** Changed in: sbackup (Ubuntu)
Status: New = Confirmed
--
You
** Changed in: sbackup (Ubuntu)
Status: New = Opinion
--
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to sbackup in Ubuntu.
https://bugs.launchpad.net/bugs/108317
Title:
[Wishlist] Sbackup should be able to revert my
Thanks for reporting this issue and helping to make sbackup better.
Could you please test whether this bug is still valid using newer releases of
sbackup (0.10.5 in Lucid/0.11.4)?
If this issue still exists please feel free to reopen it. Thank you.
** Changed in: sbackup (Ubuntu)
Status:
Thanks for reporting this issue and helping to make sbackup better.
Could you please test whether this bug is still valid using the latest release
of sbackup (0.11.4)?
If this issue still exists please feel free to reopen it. Thank you.
** Changed in: sbackup (Ubuntu)
Status: New =
** Changed in: sbackup (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to sbackup in Ubuntu.
https://bugs.launchpad.net/bugs/312945
Title:
sbackupd lock file generation is not atomic
To
Does this still happen with newer releases of sbackup (0.10.5 resp. 0.11.4)?
Please feel free to reopen it if it still exists. Thanks.
** Changed in: sbackup (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Simple
Backup
*** This bug is a duplicate of bug 697386 ***
https://bugs.launchpad.net/bugs/697386
** Changed in: sbackup
Status: Incomplete = Fix Released
** This bug has been marked a duplicate of bug 697386
RemoteMountFailedError 'Max. number of password inputs reached' not handled
properly
*** This bug is a duplicate of bug 768080 ***
https://bugs.launchpad.net/bugs/768080
** This bug has been marked a duplicate of bug 768080
improper incremental on fat32
--
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to
Please upgrade to our latest release. Thanks.
** Changed in: sbackup/0.10
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to sbackup in Ubuntu.
https://bugs.launchpad.net/bugs/609814
Title:
Thanks for reporting this issue and helping to make sbackup better.
Could you please test whether this bug is still valid using the latest release
of sbackup (0.11.4).
Thanks in advance.
** Changed in: sbackup (Ubuntu)
Status: New = Incomplete
--
You received this bug notification
** Changed in: sbackup (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to sbackup in Ubuntu.
https://bugs.launchpad.net/bugs/231841
Title:
simple-restore-gnome.py crashed with OSError in
This problem is fixed in sbackup 0.11.x. Please update. Thanks.
** Changed in: sbackup (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to sbackup in Ubuntu.
Question #172404 on sbackup changed:
https://answers.launchpad.net/sbackup/+question/172404
Status: Open = Needs information
Jean-Peer Lorenz requested more information:
Hi,
could you please post your log file?
Thank you.
Jean-Peer
--
You received this question notification because you
Thanks for your quick answers.
One question remains: how do you run daily backups as regular user?
sbackup does not support automated backups for non-priviliged users, at
the moment.
Your issue is caused by file permissions of the according log directory
specified for the profile. You have no
** Changed in: sbackup/0.11
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to sbackup.
https://bugs.launchpad.net/bugs/808011
Title:
Cannot send report by mail
To manage
Thanks for reporting this issue. Meanwhile sbackup 0.10.5 and 0.11.4 (via PPA)
is available. Does this problems still encounters with the latest release of
sbackup?
Thanks.
** Changed in: sbackup (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a
Thanks for reporting this bug and helping to make sbackup better.
The bug you're encountering is already fixed in sbackup 0.11.4. Try to
install it from our PPA https://edge.launchpad.net/~nssbackup-
team/+archive/ppa.
The original bug report was:
LP: #588578 Email notification/reporting doesn't
Thanks for reporting this issue and helping to make sbackup better.
Does this still happens with the latest release of sbackup 0.11.4?
Please consider to update, if you are on Lucid you can use our PPA at
https://edge.launchpad.net/~nssbackup-team/+archive/ppa.
Thanks.
** Changed in: sbackup
Thanks for reporting this issue and helping to make sbackup better.
At the moment this is not possible. Therefore I'm setting the status of
this bug to Wishlist in order to keep it in mind.
Thanks.
** Summary changed:
- Status indicator information greyed out
+ Text of status indicator has
*** This bug is a duplicate of bug 789835 ***
https://bugs.launchpad.net/bugs/789835
** This bug has been marked a duplicate of bug 789835
Menu option View all help topics failed
--
You received this bug notification because you are a member of Simple
Backup Maintainers, which is
Thank you for using sbackup and for taking the time reporting this bug.
In order to track down the cause of the problem, please add a log file
(debug mode).
Thanks for your help.
** Changed in: sbackup
Status: New = Incomplete
--
You received this bug notification because you are a
Thank you for choosing sbackup and for taking the time reporting this
bug.
Currently it is not possible to implement such feature due to
limitations regarding automated backups. This bug won't fix in sbackup
0.11.x.
It is eventually planned to enable such feature in future releases. Any
help is
Thank you for using sbackup and for taking the time reporting this bug.
In order to track down the cause of the problem some more information
are required. Please answer the following questions:
* Is the bug reproducible; does it happen every time?
* is your backup destination on a local drive
Hello Anton,
I fully agree with you and there is already something in the pipeline to
handle such usecases. I've started to implement a more generic filter
function in order to display snapshots, since the calendar view is
indeed quite useless and inconvinient.
I'd be very happy if someone could
Thank you for using sbackup and for taking the time reporting this bug.
Confirmed. Looking forwards for any comments.
Thanks.
** Changed in: sbackup
Importance: Undecided = Wishlist
** Changed in: sbackup
Status: New = Opinion
--
You received this bug notification because you are a
Thank you for using sbackup and for taking the time reporting this bug.
In order to track down the cause of the problem some more information
are required. Please answer the following questions:
* Is the bug reproducible; does it happen every time?
* is your backup destination on a local drive
Still valid? How is the status?
** Changed in: sbackup
Status: New = Incomplete
--
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to sbackup.
https://bugs.launchpad.net/bugs/710585
Title:
Slow transfer over sftp connection
Thank you for using sbackup and for taking the time reporting this bug.
Confirmed and added as feature request.
Thanks again.
** Changed in: sbackup
Importance: Undecided = Wishlist
** Changed in: sbackup
Status: New = Confirmed
--
You received this bug notification because you are
Question #171291 on sbackup changed:
https://answers.launchpad.net/sbackup/+question/171291
Status: Open = Answered
Jean-Peer Lorenz proposed the following answer:
Thanks for your hint and helping to make sbackup better.
From now, blueprints are enable in launchpad. Please feel free to post
Thank you for using sbackup and for reporting this issue. Unfortunately,
I am unable to reproduce your error. I use Ubuntu 10.04.2, sbackup
0.11.4 from PPA, yelp 2.30.0 (basically a default Ubuntu installation
quite similar to yours).
In order to find the cause for your error could you please
I'm closing this bug because is was fixed in package gtk-update-icon-
cache and has no longer impact on sbackup. Thanks to everyone reporting
and commenting.
** Changed in: sbackup (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 742348 ***
https://bugs.launchpad.net/bugs/742348
** This bug has been marked a duplicate of bug 742348
package sbackup-gtk 0.11.4-0ubuntu2 failed to install/upgrade: subprocess
installed post-installation script returned error exit status 1
* You can
*** This bug is a duplicate of bug 742348 ***
https://bugs.launchpad.net/bugs/742348
** This bug has been marked a duplicate of bug 742348
package sbackup-gtk 0.11.4-0ubuntu2 failed to install/upgrade: subprocess
installed post-installation script returned error exit status 1
* You can
I guess this issue is related to
https://bugs.launchpad.net/ubuntu/+source/ubuntu-mono/+bug/741387.
--
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to sbackup in Ubuntu.
https://bugs.launchpad.net/bugs/742348
Title:
package
*** This bug is a duplicate of bug 567965 ***
https://bugs.launchpad.net/bugs/567965
I've also observed some issues when modifying profile settings between
two snapshots. Thus, I'm marking this bug report as duplicate. Please
reopen if new information are available.
** This bug has been
*** This bug is a duplicate of bug 742348 ***
https://bugs.launchpad.net/bugs/742348
** This bug has been marked a duplicate of bug 742348
package sbackup-gtk 0.11.4-0ubuntu2 failed to install/upgrade: subprocess
installed post-installation script returned error exit status 1
* You can
*** This bug is a duplicate of bug 742348 ***
https://bugs.launchpad.net/bugs/742348
** This bug has been marked a duplicate of bug 742348
package sbackup-gtk 0.11.4-0ubuntu2 failed to install/upgrade: subprocess
installed post-installation script returned error exit status 1
* You can
Agreed, an *expert* option to change process priorities should be
available.
Did you tried to renice the backup process manually?
** Changed in: sbackup
Importance: Undecided = Wishlist
** Changed in: sbackup
Status: New = Opinion
--
You received this bug notification because you
*** This bug is a duplicate of bug 742348 ***
https://bugs.launchpad.net/bugs/742348
** This bug has been marked a duplicate of bug 742348
package sbackup-gtk 0.11.4-0ubuntu2 failed to install/upgrade: subprocess
installed post-installation script returned error exit status 1
* You can
*** This bug is a duplicate of bug 742348 ***
https://bugs.launchpad.net/bugs/742348
** This bug has been marked a duplicate of bug 742348
package sbackup-gtk 0.11.4-0ubuntu2 failed to install/upgrade: subprocess
installed post-installation script returned error exit status 1
* You can
*** This bug is a duplicate of bug 742348 ***
https://bugs.launchpad.net/bugs/742348
** This bug has been marked a duplicate of bug 742348
package sbackup-gtk 0.11.4-0ubuntu2 failed to install/upgrade: subprocess
installed post-installation script returned error exit status 1
* You can
*** This bug is a duplicate of bug 742348 ***
https://bugs.launchpad.net/bugs/742348
** This bug has been marked a duplicate of bug 742348
package sbackup-gtk 0.11.4-0ubuntu2 failed to install/upgrade: subprocess
installed post-installation script returned error exit status 1
* You can
*** This bug is a duplicate of bug 742348 ***
https://bugs.launchpad.net/bugs/742348
** This bug has been marked a duplicate of bug 742348
package sbackup-gtk 0.11.4-0ubuntu2 failed to install/upgrade: subprocess
installed post-installation script returned error exit status 1
* You can
Thank you for choosing sbackup and reporting this issue. The problem
that you describe is fixed in sbackup's latest release 0.11.4. Please
consider to upgrade sbackup (e.g. by using our PPA at
https://edge.launchpad.net/~nssbackup-team/+archive/ppa). Moreover,
there is a feature request for
Thank you for choosing sbackup and reporting this issue. Is this bug
still valid when using sbackup's latest release 0.11.4?
** Changed in: sbackup (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Simple
Backup Maintainers, which is
I'm closing this bug report because this issue is fixed in sbackup's
latest release (0.11.4).
** Changed in: sbackup (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to nssbackup.
I'm closing this bug report because this issue was fixed in sbackup's
latest release (0.11.x).
** Changed in: sbackup (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to sbackup
Thanks for choosing sbackup and reporting this issue. In order to track
down your problem please answer following questions:
Does this happens everytime? Is it reproducable?
Does a minimal setup (just a few files for test purpose) work?
Does the error also encounter with 'No compression'
Thank you for choosing sbackup and reporting this issue. I agree with
your comments and'll mark this as feature request.
Patches welcome :-)
Regarding to your specific email report: What log level setting do you
use? Error? If so, this is intended - only errors are being reported.
Thanks again.
Question #147281 on sbackup changed:
https://answers.launchpad.net/sbackup/+question/147281
Status: Open = Answered
Jean-Peer Lorenz proposed the following answer:
Hello Vlad,
thanks for choosing sbackup and asking this question. I suppose you use
sbackup 0.11.x? No, purge is performed only
Thanks for your comment. I've modified the used version as proposed and
removed superflous changelog entries from the Debian changelog.
--
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to sbackup in ubuntu.
** Attachment added: Debian directory
https://bugs.launchpad.net/ubuntu/+source/sbackup/+bug/719264/+attachment/1868705/+files/sbackup_0.11.4-0ubuntu1.debian.tar.gz
--
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to sbackup in
Thanks for choosing sbackup and reporting this issue. I can confirm that
something's going wrong here. This is an excerpt from your log (2nd
incr. backup):
2011-02-20 11:15:06,608 - DEBUG in filecollect.collect_files(616): Creation of
the complete exclude list.
2011-02-20 11:15:06,608 - DEBUG in
Did you tried to change theme to default Clearlooks?
--
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to sbackup.
https://bugs.launchpad.net/bugs/715924
Title:
Simple Backup won't start
*** This bug is a duplicate of bug 709338 ***
https://bugs.launchpad.net/bugs/709338
Thank you for reporting this bug. It is already reported and a fix was
released in 0.11.4. Don't panic. At the moment release 0.11.4 awaits
inclusion in Natty and I'll prepare packages for our PPA very soon.
The error was introduced in lp:sbackup/0.11 r211. This means solely sbackup
0.11.3 is affected.
Workarounds: restore top-level folders, install from source, install 0.11.2
--
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to sbackup
Public bug reported:
Binary package hint: sbackup
binary package hint: sbackup
A new upstream release for sbackup is available. It does not introduce
new feature but fixes several bugs.
The buildlog (build on Natty) and upstream changelogs are attached. Plus
source package files and debdiff.
** Attachment added: sbackup_0.11.4ubuntu1.tar.gz
https://bugs.launchpad.net/ubuntu/+source/sbackup/+bug/719264/+attachment/1851229/+files/sbackup_0.11.4ubuntu1.tar.gz
--
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to sbackup
Please sponsor.
** Changed in: sbackup (Ubuntu)
Status: New = Confirmed
** Description changed:
Binary package hint: sbackup
binary package hint: sbackup
A new upstream release for sbackup is available. It does not introduce
- new feature but fixes several bugs.
+ new
Question #145477 on sbackup changed:
https://answers.launchpad.net/sbackup/+question/145477
Status: Open = Answered
Jean-Peer Lorenz proposed the following answer:
Hi PJO,
thanks for choosing sbackup and asking this question.
Q: Is there a repository from which 0.11.4 can be installed
*** This bug is a duplicate of bug 671785 ***
https://bugs.launchpad.net/bugs/671785
Thanks for choosing sbackup and reporting this issue. It is a duplicate
of LP #671785 for which a fix is already committed and will be released
soon. Thanks again. Best regards.
** This bug has been marked a
I've updated translations in series 0.11.
** Changed in: sbackup/0.11
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to Simple Backup.
https://bugs.launchpad.net/bugs/507177
Title:
Bug #709338 status changed in 0.11:
Fix Committed = Fix Released
https://bugs.launchpad.net/sbackup/0.11/+bug/709338
Restore/revert of non-toplevel items produces only empty folders
This bug is linked to #140592.
restore/revert produces only empty folders
Bug #709338 status changed in trunk:
Fix Committed = Fix Released
https://bugs.launchpad.net/sbackup/trunk/+bug/709338
Restore/revert of non-toplevel items produces only empty folders
This bug is linked to #140592.
restore/revert produces only empty folders
Bug #701403 status changed in 0.11:
Fix Committed = Fix Released
https://bugs.launchpad.net/sbackup/0.11/+bug/701403
Unable to use remote target without giving a password
This bug is linked to #142198.
PB with backup and SSH
https://answers.launchpad.net/sbackup/+question/142198
--
You
Bug #701403 status changed in trunk:
Fix Committed = Fix Released
https://bugs.launchpad.net/sbackup/trunk/+bug/701403
Unable to use remote target without giving a password
This bug is linked to #142198.
PB with backup and SSH
https://answers.launchpad.net/sbackup/+question/142198
--
You
Bug #714916 status changed in 0.11:
Fix Committed = Fix Released
https://bugs.launchpad.net/sbackup/0.11/+bug/714916
Unhandled error in gio backend when looking up verbose error message
This bug is linked to #144478.
KeyError: 39
https://answers.launchpad.net/sbackup/+question/144478
--
Bug #714916 status changed in trunk:
Confirmed = Fix Released
https://bugs.launchpad.net/sbackup/trunk/+bug/714916
Unhandled error in gio backend when looking up verbose error message
This bug is linked to #144478.
KeyError: 39
https://answers.launchpad.net/sbackup/+question/144478
--
** Changed in: sbackup/0.11
Status: Fix Committed = Fix Released
** Changed in: sbackup/trunk
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to Simple Backup.
** Changed in: sbackup/0.11
Status: Fix Committed = Fix Released
** Changed in: sbackup/trunk
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to sbackup in ubuntu.
** Changed in: sbackup/0.11
Status: Fix Committed = Fix Released
** Changed in: sbackup/trunk
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to sbackup in ubuntu.
** Changed in: sbackup/0.11
Status: Fix Committed = Fix Released
** Changed in: sbackup/trunk
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to nssbackup.
** Changed in: sbackup/0.11
Status: Fix Committed = Fix Released
** Changed in: sbackup/trunk
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to Simple Backup.
** Changed in: sbackup/0.11
Status: Fix Committed = Fix Released
** Changed in: sbackup/trunk
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to sbackup in ubuntu.
** Changed in: sbackup/0.11
Status: Fix Committed = Fix Released
** Changed in: sbackup/trunk
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to Simple Backup.
** Changed in: sbackup/0.11
Status: Fix Committed = Fix Released
** Changed in: sbackup/trunk
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to sbackup in ubuntu.
** Changed in: sbackup/0.11
Status: Fix Committed = Fix Released
** Changed in: sbackup/trunk
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to Simple Backup.
** Changed in: sbackup/0.11
Status: Fix Committed = Fix Released
** Changed in: sbackup/trunk
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to Simple Backup.
** Changed in: sbackup/0.11
Status: Fix Committed = Fix Released
** Changed in: sbackup/trunk
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to sbackup in ubuntu.
Please post the traceback of the exception as stored in log file and
your (anonymized) configuration files used when experiencing this bug.
Thanks for your help.
--
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to Simple Backup.
Thanks for reporting this issue. Please note that nssbackup is no longer
maintained. Please use sbackup 0.11.x instead. You can find more
information at our website https://launchpad.net/sbackup.
Regarding your questions:
1. Help in nssbackup and sbackup is not yet fully available.
2. Browse
** Changed in: nssbackup
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to nssbackup.
https://bugs.launchpad.net/bugs/587911
Title:
Logarithmic purge disabled/does not work
Setting to invalid because there has been no activity for a long time.
** Changed in: nssbackup
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to nssbackup.
Setting to invalid because there has been no activity for a long time.
** Changed in: nssbackup
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to nssbackup.
Please use sbackup 0.11 and report bugs there. nssbackup is no longer
maintained.
** Also affects: sbackup
Importance: Undecided
Status: New
** Changed in: sbackup
Importance: Undecided = Wishlist
** Changed in: nssbackup
Status: Confirmed = Won't Fix
** Changed in: sbackup
** Changed in: nssbackup
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to nssbackup.
https://bugs.launchpad.net/bugs/622512
Title:
No updated packages available for Ubuntu pre-Lucid
Setting status to invalid because there has been no activity for more
than 90 days.
** Changed in: nssbackup
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to nssbackup.
101 - 200 of 666 matches
Mail list logo
