nssbackup-team team mailing list archive

[Bernd Wurst <980786@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

On one of my desktop systems, the folder ~/.gvfs is inaccessable from time to time. That means, the directory entry looks like that:
  d?????????  ? ?     ?         ?                ? .gvfs

The reason for this is out of scope here and the file is excluded (by
default in sbackup config).

But sbackup complains about this on every run:
2012-04-13 14:23:12,209 - WARNING: File '/home/xxxxx/.gvfs' does not exist.

I have had a look in the code and I think in file src/util/filecollect.py, in _check_for_excludes(), the first if-elif-conditions should be interchanged. For the moment, sbackup first looks if the file *can* be accessed and after that, it looks if the file *should* be accessed.
If this would be the other way round, There won't be complains about my .gvfs not being accessable.

As far as I can see, 0.11.4 and trunk are nearly identical (in this
scope).

** Affects: sbackup
     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.net/bugs/980786

Title:
  Don't complain about non-accessable excluded files

To manage notifications about this bug go to:
https://bugs.launchpad.net/sbackup/+bug/980786/+subscriptions