Install integrates changesets with files having execute permissions

the jcheck+mercurial0.9.5 on the server isn't rejecting those changesets due to a bug in Mercurial0.9.5. But newer Mercurials being used by the developers are operating properly, and jcheck is refusing to pull these changesets into your local clones.

Most install work is done on windows, windows tends to turn on the execute bit

The workarounds are not ideal

Option 1: Toss the repo and reclone it (heavy and dangerous)
Option 2: Comment out the pretxnchangegroup hook that runs jcheck in ~/.hgrc, do the pull, and turn the hook back on



How do we prevent changesets from having the x bit o?
1) Look at pre commit hook modification assuming you can do this without another changeset
2) Have a make target that changes the xbit
3) precuedure added to the install post a review process to verify x bits are off

This is a well known problem that others experience and work around, edited post from Kelly.