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
--
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
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
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
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
5 matches
Mail list logo