NTFS Permissions Changing

[Stephen Reece]

> FYI, the current version is 3.5.1. The future sends its regards.

I'm just a Caveman. I fell in some ice and later got thawed out by your scientists. Upgrading Mercurial on a build server with so many moving parts frightens and confuses me. 

That being said, I suppose we should do so.

> That particular file is only written to once in the lifetime of a repository, at creation. What is the date on that file?

It was created on March 1, 2012, and modified on March 1, 2011. This didn't change even after I reset the permissions on it again. We had it happen again today with an extremely nested .vb.1 file located way under .hg/store/data/etc.etc. All access is done via TortoiseHG using HTTPS, so I'm not sure why the NTFS permissions would change.

Thanks,
Stephen


-----Original Message-----
From: Matt Mackall [mailto:mpm at selenic.com] 
Sent: Monday, September 28, 2015 6:19 PM
To: Stephen Reece
Cc: mercurial at selenic.com
Subject: Re: NTFS Permissions Changing

On Mon, 2015-09-28 at 21:58 +0000, Stephen Reece wrote:
> Hello,
> 
> We are running Mercurial 1.8.4

FYI, the current version is 3.5.1. The future sends its regards.

>  Everything has been fine until this morning. For some reason, NTFS permissions on certain random files are being changed, and when users try to push, they get an Access Denied error. All access is done via HTTP rather than directly on a share.
> 
> We use a Mercurial Committers and Viewers security group in Active 
> Directory to control access, and NTFS permissions are supposed to be 
> inherited from the top directory. An example file that this happened 
> to is .hg/requires.

That particular file is only written to once in the lifetime of a repository, at creation. What is the date on that file?

--
Mathematics is the supreme nostalgia of our time.