[Nssbackup-team] [Bug 471385] Re: simple backup restore error in 9.10

2009-12-17 Thread Sense Hofstede
Thank you for helping with making Ubuntu and sbackup better by reporting this bug. I've found a similar report and am linking this report to it. However, unfortunately it seems there is no active development going on upstream; the last time a new download was offered was June 2008 and there hasn

[Nssbackup-team] [Bug 471385] Re: simple backup restore error in 9.10

2009-12-17 Thread Sense Hofstede
Apologises. The upstream I referred to in my last comment was the sbackup project at SourceForge. Apparently sbackup has moved to Launchpad, which explains why everything seemed dead at SF. I've opened an sbackup task so the developers can take a look at the problem. -- simple backup restore er

[Nssbackup-team] [Bug 471385] Re: simple backup restore error in 9.10

2010-02-09 Thread jage
With 10.4 I have the same bug, it does not appear to be triaged in Lucid. -- simple backup restore error in 9.10 https://bugs.launchpad.net/bugs/471385 You received this bug notification because you are a member of NSsbackup team, which is subscribed to sbackup in ubuntu. ___

[Nssbackup-team] [Bug 471385] Re: simple backup restore error in 9.10

2010-02-09 Thread jage
** Changed in: sbackup Status: New => Confirmed -- simple backup restore error in 9.10 https://bugs.launchpad.net/bugs/471385 You received this bug notification because you are a member of NSsbackup team, which is subscribed to sbackup in ubuntu. __

[Nssbackup-team] [Bug 471385] Re: simple backup restore error in 9.10

2010-02-09 Thread Sense Hofstede
Thank you for letting know this is still and issue in Ubuntu 10.04 Lucid Lynx. However, please don't change the status of the upstream project as they may be using the statuses differently and no developer has looked at the bug yet, which means they cannot confirm it yet. ** Changed in: sbackup

[Nssbackup-team] [Bug 471385] Re: simple backup restore error in 9.10

2010-02-09 Thread Sense Hofstede
jage: I cannot know that someone at IRC told you to change the status if you don't say so. A guideline of the Bug Control team is to always say why they changed a status when they do so, this makes it easier for people to follow the bug's life and to understand what has been happening with it durin

[Nssbackup-team] [Bug 471385] Re: simple backup restore error in 9.10

2010-02-10 Thread Jean-Peer Lorenz
As one of the contributors of the nssbackup project I want to give some information on the state of sbackup/nssbackup: * the project sbackup is not actively maintained since more than 2 years now (the current version sticks to 0.10.5) and it is very likely (in fact it is pretty sure) that the orig

[Nssbackup-team] [Bug 471385] Re: simple backup restore error in 9.10

2010-02-10 Thread Sense Hofstede
Thank you for your extensive reply! I suspect that this makes the bug Won't Fix for the sBackup project since the code base is completely different. I'm marking the bug in Ubuntu as a Won't Fix as well to reflect situation. ** Changed in: sbackup (Ubuntu) Status: Triaged => Won't Fix --

[Nssbackup-team] [Bug 471385] Re: simple backup restore error in 9.10

2010-09-19 Thread Jean-Peer Lorenz
Please re-test with our latest release which can be found at https://edge.launchpad.net/~nssbackup-team/+archive/ppa and post log output etc. if the error is still alive. Thanks. ** Changed in: sbackup Status: New => Incomplete -- simple backup restore error in 9.10 https://bugs.launchpad

[Nssbackup-team] [Bug 471385] Re: simple backup restore error in 9.10

2011-01-16 Thread Jean-Peer Lorenz
I'm closing this because there has been no activity for more than 120 days. ** 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 in ubuntu. https://bugs.launchpad.ne

Re: [Nssbackup-team] [Bug 471385] Re: simple backup restore error in 9.10

2010-02-09 Thread jage
Yes, that will teach me to rely on the IRC channels for advice as they specifically instructed me not only that it was necessary to change the upstream status, but how (considering it isn't labeled). Anyway, I apologize for being a dupe, and wasting your time... at least take heart that I knew eno