** Also affects: sbackup/0.11
Importance: Undecided
Status: New
** Also affects: sbackup/trunk
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to sbackup.
https://bugs.launchpad
Hello Thomas,
thank you for using sbackup and reporting this issue!
You are absolutely right! Touching existing snapshots is a BAD idea and
upgrading them is highly not recommended.
> PLEASE MAKE THE RESTORE BACKWARDS COMPATIBLE!!!
I am working on this and there is basic support for reading and
** Changed in: sbackup
Importance: Undecided => High
** Changed in: sbackup
Status: New => Won't Fix
--
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to sbackup.
https://bugs.launchpad.net/bugs/1000896
Title:
Upgrade of
Thank you for using sbackup and reporting this issue!
In order to track down your problem please post a full log (debug mode)
recorded when the error happens. Please also answer following questions:
* do you run as superuser or regular user?
* do you use scheduled backups?
* does manual snapshot
** Also affects: sbackup/0.10
Importance: Undecided
Status: New
** Also affects: sbackup/trunk
Importance: Medium
Assignee: Martin Schaaf (mascha)
Status: Fix Committed
** Changed in: sbackup/0.10
Status: New => Fix Committed
** Changed in: sbackup/0.10
Importa
Bug #1000896 status changed in sbackup:
New => Won't Fix
https://bugs.launchpad.net/sbackup/+bug/1000896
"Upgrade of snapshot not possible due to problem with files.snar (Errno 2 -
file not found) + SOLUTION"
This bug is linked to #129584.
Snapshot version not supported
https://answers.laun
** Changed in: sbackup/trunk
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to sbackup.
https://bugs.launchpad.net/bugs/311967
Title:
sbackupd mistreats the hostname part of the backup directo
** Changed in: sbackup
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to sbackup.
https://bugs.launchpad.net/bugs/662404
Title:
wrong base for incremental backup
To manage notifications about
** Changed in: sbackup
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to sbackup.
https://bugs.launchpad.net/bugs/955602
Title:
Different backup jobs can not be started individually
To manage
A fix for this issue was pushed to repository (sbackup/0.11):
revno: 245
committer: Jean-Peer Lorenz
branch nick: 0.11
timestamp: Wed 2012-12-19 20:45:07 +0100
message:
* added exception handling in case of not implemented 'attach_to_status_icon'
method (e.g. Debian Wheezy)
Please feel fre
** Changed in: sbackup/trunk
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to sbackup.
https://bugs.launchpad.net/bugs/455377
Title:
sbackup crashes at backup -->Zombie
To manage notificatio
** Changed in: sbackup
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to nssbackup.
https://bugs.launchpad.net/bugs/622496
Title:
Config might get lost when starting config-gui while destinati
Fix for this issue was pushed to repository (sbackup/0.11): ignore
ValueError when parsing port.
** Changed in: sbackup
Status: In Progress => Fix Committed
** Changed in: sbackup
Milestone: None => 0.11.5
--
You received this bug notification because you are a member of Simple
Backu
I've pushed a possible fix for this to the repository (sbackup/0.11):
avoid using the ConfigParser interpolation feature when checking added
directories. Hopefully this will fix the issue, I was not able to
reproduce the bug so far.
Please feel free to re-open this bug if the issue is still valid!
** Changed in: sbackup
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to sbackup.
https://bugs.launchpad.net/bugs/888367
Title:
sbackup crashes when trying to add a directory to backup
Thank you for using sbackup and reporting this issue.
I guess your described behaviour is actually not a bug rather a
limitation of the underlying TAR command: it is not possible to use
compression and to split snapshots at the same time.
Can you please check whether it works as expected when set
** Changed in: sbackup
Importance: Undecided => Medium
** 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/888367
Title:
sbackup c
*** This bug is a duplicate of bug 888367 ***
https://bugs.launchpad.net/bugs/888367
** This bug has been marked a duplicate of bug 888367
sbackup crashes when trying to add a directory to backup
--
You received this bug notification because you are a member of Simple
Backup Maintainers,
*** This bug is a duplicate of bug 888367 ***
https://bugs.launchpad.net/bugs/888367
** This bug has been marked a duplicate of bug 888367
sbackup crashes when trying to add a directory to backup
--
You received this bug notification because you are a member of Simple
Backup Maintainers,
*** This bug is a duplicate of bug 888367 ***
https://bugs.launchpad.net/bugs/888367
** This bug has been marked a duplicate of bug 888367
sbackup crashes when trying to add a directory to backup
--
You received this bug notification because you are a member of Simple
Backup Maintainers,
Closing this bug since it no longer appears. Feel free to re-open it if
the issue is still valid. Thanks.
** Changed in: sbackup
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to sbackup.
https
** Changed in: sbackup/trunk
Assignee: Martin Schaaf (mascha) => (unassigned)
--
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to nssbackup.
https://bugs.launchpad.net/bugs/632605
Title:
Error while closing snapshot file over
Fixed in sbackup 0.11.0
** Changed in: sbackup
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/585769
Title:
default backup directory doesn
** Changed in: sbackup
Importance: Low => Wishlist
--
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to nssbackup.
https://bugs.launchpad.net/bugs/601476
Title:
Help and documentation is incomplete/outdated
To manage notificati
*** This bug is a duplicate of bug 622496 ***
https://bugs.launchpad.net/bugs/622496
** This bug has been marked a duplicate of bug 622496
Config might get lost when starting config-gui while destination drive is
not present
--
You received this bug notification because you are a member
*** This bug is a duplicate of bug 345379 ***
https://bugs.launchpad.net/bugs/345379
** This bug has been marked a duplicate of bug 345379
[Feature request] Scheduled backups for regular users and distinct profiles
--
You received this bug notification because you are a member of Simple
B
** Changed in: sbackup/trunk
Importance: Undecided => High
--
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to nssbackup.
https://bugs.launchpad.net/bugs/567965
Title:
Problems with incr. snapshots if configuration was modified
Confirmed as feature request.
Every profile created by either admins or regular users should allow
scheduling, i.e. distinct profiles should be independend from each other
and therefore allow the setting of different schedules.
** Summary changed:
- [Feature request] Scheduled backups for regula
Reminder to keep track of this: To make sure no zombie will stay around,
it is necessary to detach the backup process from its parent process
(i.e. sbackup-config-gtk).
This is properly implemented in trunk (but not yet released).
Since this is minor issue, it won't get fixed in sbackup 0.11 seri
** Changed in: sbackup
Status: Fix Committed => Fix Released
** Changed in: sbackup
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to sbackup.
https://bugs.launchpad.net/bugs/489107
Title
Fixed in sbackup 0.11.0
** Changed in: sbackup
Importance: Undecided => Medium
** Changed in: sbackup
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.launchp
This was fixed in sbackup 0.11.0.
** Changed in: sbackup
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/331551
Title:
Wrong original Engli
OK, thanks. Marking bug as invalid.
For future reference, I think it is a bad idea to have two different
schedules and/or users back up to the same backup location, and it
actually seems to be not supported. It would be nice if this was
signalled and reported back to the user in a more transparent
33 matches
Mail list logo