This bug is marked as Fix Released and noted as fixed upstream, but the
problem persists in sbackup svn on sourceforge (and so in gutsy and
hardy). The latest revision (79) of /trunk/data/sbackup.conf.example
contains:
hello,
FYI, I don't support Sbackup anymore.
But, as I was the one to close this bug I shall answer your question. This bug
is solved. You were looking at the wrong place in sbackup svn. The right one
was /branches/stable-0.10/sbackup.conf.example.
you could have looked at
Oumar,
Thank you for you quick response. My apologies--I had installed
sbackup when I was running feisty but didn't notice the problem until
after I upgraded to gutsy. You are of course correct that problem is
fixed in gutsy. I must have brought the feisty config file forward when
I
** Changed in: sbackup (Ubuntu)
Status: Fix Committed = Fix Released
--
Sbackup should exclude browser cache files by default?
https://bugs.launchpad.net/bugs/46015
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs
Fixed upstream. all cache dir are excluded by default.
** Changed in: sbackup (Ubuntu)
Assignee: Aigars Mahinovs = Ouattara Aziz
Status: Confirmed = Fix Committed
--
Sbackup should exclude browser cache files by default?
https://bugs.launchpad.net/bugs/46015
You received this bug
