On Mon, Sep 07, 2009 at 03:07:19PM +0200, Arthur Lutz wrote:
> Package: inosync
> Version: 0.2-1
> Severity: normal
> 
> 
> On a inosync I get a bunch of 
> 
> inosync[18003]: ignoring IN_ISDIR|IN_OPEN on file
> inosync[18003]: caught IN_CLOSE_NOWRITE|IN_ISDIR on file
> inosync[18003]: ignoring IN_CLOSE_NOWRITE|IN_ISDIR on file
> 
> then it crashes on : 
> 
> Traceback (most recent call last):
>   File "/usr/bin/inosync", line 217, in <module>
>     main()
>   File "/usr/bin/inosync", line 205, in main
>     notifier.process_events()
>   File "/var/lib/python-support/python2.5/pyinotify/pyinotify.py", line 640, 
> in process_events
>     self._default_proc_fun(revent)
>   File "/var/lib/python-support/python2.5/pyinotify/pyinotify.py", line 341, 
> in __call__
>     return self.process_default(event)
>   File "/usr/bin/inosync", line 89, in process_default
>     (event.event_name, os.path.join(event.path, event.name)))
> AttributeError: 'Event' object has no attribute 'path'
> 
> 

hm, I can't reproduce this. I'll try with a lenny system later
tho. anyways, this did make me upgrade my pyinotify and notice that it
completely breaks with the new version (not the version you have). :)

Thanks for the bug report,
Ryan

-- 
_________________________
Ryan Niebur
[email protected]

Attachment: signature.asc
Description: Digital signature

Reply via email to