Ryan Schmidt <subversion-20...@ryandesign.com> writes: > Is this loss-of-executable-bit-on-upgrade problem already known or > should file a bug report? I did not immediately see a matching ticket > in the issue tracker.
I don't think upgrade is resposible. Can you be certain that the files had the execute bit before the upgrade? Perhaps a bug in the old client caused the problem before the upgrade? What other operations did you do after the upgrade? Upgrade doesn't modify working files, it only modifies the database in the .svn directory. Upgrade doesn't even look at the working files, it never accesses them. The working files could be absent, owned by root and unreadable, replaced by directories, etc. and it doesn't affect upgrade. I don't see how upgrade could be responsible for the loss of executable bits. -- Philip Martin | Subversion Committer WANdisco // *Non-Stop Data*
