[Bug 4162] New: How to clone Mercurial repos on the server and change clone permissions

mercurial-bugs at selenic.com mercurial-bugs at selenic.com
Fri Feb 7 15:35:34 CST 2014


          Priority: normal
            Bug ID: 4162
                CC: mercurial-devel at selenic.com
          Assignee: bugzilla at selenic.com
           Summary: How to clone Mercurial repos on the server and change
                    clone permissions
          Severity: bug
    Classification: Unclassified
                OS: Windows
          Reporter: philip.w.mcadams at intel.com
          Hardware: PC
            Status: UNCONFIRMED
           Version: 2.5.4
         Component: Mercurial
           Product: Mercurial

In our Windows Server 2008 environment we have received requests from several
developers that have had a desire to clone a Mercurial repo but change the
permissions on the clone.  Our typical usage model had been to clone a parent
repo but keep the permissions the same which has worked over the past year with
no issues. Last week is when we first saw this issue: I cloned a repo and went
into the Advanced Security properties to change the permissions. Upon doing so
users from the parent started complaining that they could no longer access the
parent repo.  Long story short I eventually fixed the issue and attempted to do
it again: clone a repo on the server and then change the permissions.  The
issue happened again.  Got this issue fixed but kept the new clone in tact. 
Everything appeared fine for a couple of days an then I received a report that
the faceless account on the clone did not have R/W access.  I went out to the
server and checked it and sure enough the faceless account did have R/W.  I
thought this was odd but nonetheless I removed the account and added it back. 
The user stated that that had fixed his issue on the clone.  But later I
received a message from a user of the parent that they couldn't access the
parent.  This was repeated today with a totally different set of repos that had
been cloned on the server but needed different permissions.  In doing some
research I found info on Mercurial hardlinking:
http://mercurial.selenic.com/wiki/HardlinkedClones and wondered if that had
something to do with this issue. And also this link:
http://selenic.com/pipermail/mercurial/2011-March/037424.html which discusses
the best way to clone repos on the server.  Today when this issue happened
again on a production repo I went into the two clones and made sure all of the
permissions matched the main repo and that the permissions inherented all the
way down through the repo.  This fixed the issue.  Can you shed some some light
on this issue?

You are receiving this mail because:
You are on the CC list for the bug.

More information about the Mercurial-devel mailing list