** Also affects: sbackup/0.11
Importance: Undecided
Status: New
** Also affects: sbackup/trunk
Importance: Medium
Status: Fix Committed
** Changed in: sbackup/0.11
Status: New => Fix Committed
** Changed in: sbackup/0.11
Importance: Undecided => Medium
** Changed i
** Also affects: sbackup/0.11
Importance: Undecided
Status: New
** Also affects: sbackup/trunk
Importance: Medium
Status: Fix Committed
** Changed in: sbackup/trunk
Milestone: 0.11.5 => None
** Changed in: sbackup/0.11
Milestone: None => 0.11.5
** Changed in: sbackup
** Also affects: sbackup/0.11
Importance: Undecided
Status: New
** Also affects: sbackup/trunk
Importance: Medium
Status: Fix Committed
** Changed in: sbackup/0.11
Milestone: None => 0.11.5
** Changed in: sbackup/trunk
Milestone: 0.11.5 => None
** Changed in: sbackup
** Also affects: sbackup/0.11
Importance: Undecided
Status: New
** Also affects: sbackup/trunk
Importance: Low
Status: Fix Committed
** Changed in: sbackup/trunk
Status: Fix Committed => Triaged
** Changed in: sbackup/0.11
Status: New => Fix Committed
** Change
** Also affects: sbackup/0.11
Importance: Undecided
Status: New
** Also affects: sbackup/trunk
Importance: Wishlist
Status: Fix Committed
** Changed in: sbackup/trunk
Status: Fix Committed => Triaged
** Changed in: sbackup/0.11
Status: New => Fix Committed
** C
** Also affects: sbackup/0.11
Importance: Undecided
Status: New
** Also affects: sbackup/trunk
Importance: Medium
Status: Fix Committed
** Changed in: sbackup/0.11
Status: New => Fix Committed
** Changed in: sbackup/0.11
Importance: Undecided => Medium
** Changed i
I finished converting my old backups. While doing so, I logged times and
snar file size as usual. During the last conversion, I observed that the
behaviour had changed from an exponential to a quadratic one, so that
generating a 9MB snar file required 20 days rather than the 60 that were
needed bef
Question #216105 on sbackup changed:
https://answers.launchpad.net/sbackup/+question/216105
Anton posted a new comment:
Just one additional note, as general 'good practice' regarding backups.
A backup is intended as a *fallback* option in case your primary data
gets lost. In the situation you des
Thank you for using sbackup and reporting this issue.
In order to track down the cause of your problem please answer following
questions:
* What version of sbackup do you use? Installed from?
* What distribution do you use?
* Do backups work basically?
* Do you run as superuser or regular user?
Thanks for this report and your suggestion. I've modified the order of checks.
This should fix your issue.
Best regards.
** Also affects: sbackup/0.11
Importance: Undecided
Status: New
** Also affects: sbackup/trunk
Importance: Undecided
Status: New
** Changed in: sbackup/0.
Thank you for using sbackup and reporting this issue.
In order to track down the cause of your problem please answer following
questions:
* What version of sbackup do you use? Installed from?
* What distribution do you use?
* Do local backups work?
* Do you run as superuser or regular user?
* Can
Thank you for using sbackup and reporting this issue.
In order to track down the cause of your problem please answer following
questions:
* What version of sbackup do you use? Installed from?
* What distribution do you use?
* Do local backups work?
* Do you run as superuser or regular user?
* Can
Bug #1000171 status changed in 0.11:
New => Won't Fix
https://bugs.launchpad.net/sbackup/0.11/+bug/1000171
"sbackup-upgrade-backups incredibly slow"
This bug is linked to #129584.
Snapshot version not supported
https://answers.launchpad.net/sbackup/+question/129584
--
You received this que
Bug #1000171 status changed in trunk:
New => Triaged
https://bugs.launchpad.net/sbackup/trunk/+bug/1000171
"sbackup-upgrade-backups incredibly slow"
This bug is linked to #129584.
Snapshot version not supported
https://answers.launchpad.net/sbackup/+question/129584
--
You received this que
Hello Francesco,
thank you for using sbackup and reporting this issue!
You are absolutely right! Performance of the upgrading process is a
total nightmare and, also, touching existing snapshots is a BAD idea.
Therefore, upgrading is highly not recommended.
I am working on making the restore back
*** This bug is a duplicate of bug 1000171 ***
https://bugs.launchpad.net/bugs/1000171
** This bug has been marked a duplicate of bug 1000171
[Feature request] make it backwards compatible because upgrade-backups is
incredibly slow and not reliable
--
You received this bug notification b
** Also affects: sbackup/0.11
Importance: Undecided
Status: New
** Also affects: sbackup/trunk
Importance: Medium
Assignee: Martin Schaaf (mascha)
Status: Fix Committed
** Also affects: sbackup/0.10
Importance: Undecided
Status: New
** Changed in: sbackup/trunk
Oh, that was a while ago. Let's see what I can answere of this:
2013-01-03 14:44, Jean-Peer Lorenz skrev:
> Thank you for using sbackup and reporting this issue.
>
> In order to track down the cause of your problem please answer following
> questions:
>
> * What version of sbackup do you use? Ins
** Also affects: sbackup/0.10
Importance: Undecided
Status: New
** Also affects: sbackup/trunk
Importance: Undecided
Assignee: Martin Schaaf (mascha)
Status: Fix Committed
** Changed in: sbackup/0.10
Status: New => Fix Committed
** Changed in: sbackup/trunk
** Also affects: sbackup/0.10
Importance: Undecided
Status: New
** Changed in: sbackup/0.10
Status: New => Fix Committed
** Changed in: sbackup/0.10
Importance: Undecided => Medium
** Changed in: sbackup
Status: Fix Committed => New
** Also affects: sbackup/trunk
I
** Also affects: sbackup/0.10
Importance: Undecided
Status: New
** Also affects: sbackup/trunk
Importance: Undecided
Assignee: Martin Schaaf (mascha)
Status: Fix Committed
** Changed in: sbackup/trunk
Assignee: Martin Schaaf (mascha) => (unassigned)
** Changed in: s
** Also affects: sbackup/0.10
Importance: Undecided
Status: New
** Also affects: sbackup/trunk
Importance: High
Assignee: Martin Schaaf (mascha)
Status: Fix Committed
** Changed in: sbackup/0.10
Status: New => Fix Committed
** Changed in: sbackup/0.10
Importanc
Happens the same thing to me in the same context.
In my case I have an enormous quantity of jar files that I want to exclude.
I'm on version 0.11.4 on Ubuntu 12.04 LTS 64 bits up to date.
--
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscr
The destination is accessed using sftp
I get this in the end of the log:
2013-01-03 14:21:08,796 - INFO: Summary of backup
2013-01-03 14:21:08,796 - INFO: Number of directories: 21974.
2013-01-03 14:21:08,796 - INFO: Total number of files: 56033.
2013-01-03 14:21:08,796 - INFO: Number of symlinks
** Also affects: sbackup/0.10
Importance: Undecided
Status: New
** Also affects: sbackup/0.11
Importance: Undecided
Status: New
** Also affects: sbackup/trunk
Importance: Wishlist
Status: Confirmed
** Changed in: sbackup/0.11
Status: New => Won't Fix
** Chan
** Also affects: sbackup/0.10
Importance: Undecided
Status: New
** Also affects: sbackup/0.11
Importance: Undecided
Status: New
** Also affects: sbackup/trunk
Importance: Wishlist
Status: In Progress
** Changed in: sbackup/0.10
Status: New => Won't Fix
** Ch
** Also affects: sbackup/0.10
Importance: Undecided
Status: New
** Also affects: sbackup/trunk
Importance: Undecided
Status: Fix Committed
** Changed in: sbackup/trunk
Status: Fix Committed => Invalid
** Changed in: sbackup/0.10
Status: New => Fix Committed
**
** Changed in: sbackup/trunk
Status: In Progress => Triaged
** Changed in: sbackup/trunk
Importance: Low => Medium
--
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
Titl
** Also affects: sbackup/0.11
Importance: Undecided
Status: New
** Also affects: sbackup/trunk
Importance: Wishlist
Assignee: Jean-Peer Lorenz (peer.loz)
Status: In Progress
** Changed in: sbackup/0.11
Status: New => Won't Fix
--
You received this bug notificatio
** Changed in: sbackup
Status: Confirmed => Triaged
** Also affects: sbackup/0.11
Importance: Undecided
Status: New
** Also affects: sbackup/trunk
Importance: Wishlist
Status: Triaged
** Changed in: sbackup/0.11
Status: New => Won't Fix
--
You received this bu
** Also affects: sbackup/0.11
Importance: Undecided
Status: New
** Also affects: sbackup/trunk
Importance: Medium
Status: Fix Committed
** Changed in: sbackup/trunk
Status: Fix Committed => Triaged
** Changed in: sbackup/0.11
Importance: Undecided => Medium
** Chan
** Also affects: sbackup/0.11
Importance: Undecided
Status: New
** Also affects: sbackup/trunk
Importance: Wishlist
Status: Triaged
** Changed in: sbackup/0.11
Status: New => Won't Fix
--
You received this bug notification because you are a member of Simple
Backup Mai
** Changed in: sbackup/trunk
Status: New => Invalid
--
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to sbackup.
https://bugs.launchpad.net/bugs/290237
Title:
No backup created when allowing GNOME to prompt for password
To
Thank you for using sbackup and reporting this issue.
Please note, the "error message" you have encountered is a warning and
can be safely ignored. In case there are more issues please provide more
comprehensive information.
Thank you in advance.
** Changed in: sbackup (Ubuntu)
Status: Ne
Thank you for using sbackup and reporting your problem.
Did you checked the permissions of your destination folder? Does the
problem still exists?
Thanks for further information in case your problem is still valid.
** Changed in: sbackup (Ubuntu)
Status: New => Incomplete
--
You receive
A fix for this issue was pushed into repository series 0.11.
** Changed in: sbackup (Ubuntu)
Status: New => Fix Committed
--
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/
Thank you for using sbackup and reporting this issue. Can you please
test whether the problem still exists when using the latest version of
sbackup 0.11.4? Thank you so much.
** Changed in: sbackup (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a
Thank you for using sbackup and reporting this issue. Can you please
test whether the problem still exists when using the latest version of
sbackup 0.11.4? Thank you so much.
** Changed in: sbackup (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a
Thank you for using sbackup and reporting this issue. Can you please
test whether the problem still exists when using the latest version of
sbackup 0.11.4? Thank you so much.
** Changed in: sbackup (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a
Thank you for using sbackup and reporting this issue. Can you please
test whether the problem still exists when using the latest version of
sbackup 0.11.4? Thank you so much.
** Changed in: sbackup (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a
I am closing this report since it is fixed in latest version of sbackup
0.11.x. Please upgrade to the latest version.
** Changed in: sbackup (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Simple
Backup Maintainers, which is sub
I'm setting the status of this report to confirmed since it affects
multiple users.
Unfortunately, I was not able to reproduce the error so far.
@cuby: Would you mind to post your full log file (debug mode) please?
I start to think it is related to some timing issue...help in tracking
this down
Thank you for using sbackup and reporting this issue. Can you please
test whether the problem still exists when using the latest version of
sbackup 0.11.4? Thank you so much.
** Changed in: sbackup (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you
The issue was fixed in sbackup series 0.11.x
Please upgrade. Thank you.
** 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 in Ubuntu.
https://bugs
Thank you for using sbackup and reporting this issue. Can you please
test whether the problem still exists when using the latest version of
sbackup 0.11.4? Thank you so much.
** Changed in: sbackup (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you
The issue was fixed in sbackup series 0.11.x
Please upgrade. Thank you.
** 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 sbackup in Ubuntu.
https://bugs.lau
The issue was fixed in sbackup series 0.11.x
Please upgrade. Thank you.
** 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 sbackup in Ubuntu.
https://bugs.lau
Thank you for using sbackup and reporting this issue. Can you please
test whether the problem still exists when using the latest version of
sbackup 0.11.4? Thank you so much.
** Changed in: sbackup (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you
The issue was fixed in sbackup series 0.11.x
Please upgrade. Thank you.
** Changed in: sbackup (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: sbackup/0.10
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Simple
Backup
Thank you for using sbackup and reporting this issue. Can you please
test whether the problem still exists when using the latest version of
sbackup 0.11.4? Thank you so much.
** Changed in: sbackup (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you
50 matches
Mail list logo