View Single Post
Old 01-03-2016, 12:37 AM   #3
kovidgoyal
creator of calibre
kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.
 
kovidgoyal's Avatar
 
Posts: 45,440
Karma: 27757438
Join Date: Oct 2006
Location: Mumbai, India
Device: Various
That's a very strange error, as far as I can tell it should be impossible, unless some other process is modifying the installation directory simultaneously with the calibre installer. Or the lstat system call is failing for files in the installation directory.

@eschwartz: The presence of symlinks should not matter, since python's rmtree implementation does not call itself with symlinks as arguments. The only way it can happen is if os.lstat fails for a path. Then the rmtree() implementation just assumes the path is a directory. I dont know why rmtree was designed to ignore lstat failures.
kovidgoyal is offline   Reply With Quote