Currently, stow defines a "conflict" by a name clash. I think that checking for name clashes only isn't enough. Wrong file access permissions should also be considered as "conflicts". Maybe the admin has modified the permissions of files in the target directory, or -- what is more probable -- some of the files in the package directory have wrong permissions because of a wrong installation. So I suppose to insert these checks into the "-n" option. I am using Debian 2.0, but I know that the current unstable Debian uses the same code base (1.3.2). Greetings, Michael