hg 5.2.2: abort: Permission denied: '..../.hg/wcache/.manifestfulltextcache-gc3hkx8o~'

[Augie Fackler]

> On Apr 29, 2020, at 3:01 AM, Alan Mackenzie <acm at muc.de> wrote:
> 
> Hello again, Augie.
> 
> On Thu, Apr 02, 2020 at 16:14:48 -0400, Augie Fackler wrote:
>> It looks like someone did something to that repo as root, and that was
>> the first time hg sniffed some of the disk contents. It's safe to blow
>> away the entire .hg/wcache directory, and hopefully that'll have you on
>> your way.
> 
> I've worked out what it is.  It is the hg log that my regular backup
> script does as root.  This wcache directory keeps coming back.
> 
> hg log, even as root, should surely not corrupt a repository.  It is
> doing so here.

Nothing is corrupt. You’re getting some permission errors, which should probably be fixed using a sticky bit or something.

> 
> Now that I know what it is, I can implement workarounds.  But this is
> ugly; it would be nice if it could be fixed properly.

Can you reproduce this and add --traceback to the command? I’d be happy to try and patch hg so this doesn’t happen (we shouldn’t choke on permission errors when trying to read/write cache	files), but also know that this isn’t corruption - no data is at risk.

> 
> Thanks!
> 
>>> On Apr 2, 2020, at 15:52, Alan Mackenzie <acm at muc.de> wrote:
> 
>>> Hello, mercurial.
> 
>>> I'm currently running mercurial 5.2.2 on Gentoo GNU/Linux.
> 
>>> On attempting, as a normal user, to apply a tag to a repository, I
>>> get the error message in the subject line.  Both the repository and
>>> the script which applies the tag are many years old, and have usually
>>> worked flawlessly.  I think the change to the latest version of hg
>>> coincided with the appearance of this error message.
> 
>>> ..../.hg/wcache looks like this:
> 
>>> drwxr-xr-x 2 root root 4096 Apr 26  2019 .hg/wcache/
> 
>>> , and the contents of ..../.hg/wcache look like this:
> 
>>> -rwx--x--x 1 root root  0 Mar 22  2019 checkisexec
>>> lrwxrwxrwx 1 root root 16 Apr 26  2019 checklink -> checklink-target
>>> -rw-r--r-- 1 root root  0 Apr 26  2019 checklink-target
>>> -rw-r--r-- 1 root root  0 Mar 29  2019 checknoexec
> 
>>> .  It seems strange that this directory and its contents are owned by
>>> root.  It seems an altogether strange directory in any case.
> 
>>> What is going on here that produces this error message?
> 
>>> Please help me get this repository working again.  Thanks!
> 
> -- 
> Alan Mackenzie (Nuremberg, Germany).