![]() ![]() I also tried cloning the repo to a different location, then pushing to the new repo, but that changes nothing. I have found this answer on this site, but I do not have a file. hg/wlock (or anything named similarly) in the repo folder. Since was asked: The permissions for the. hg directory, probably as consequence of me messing with permissions while trying to solve the problem alone, there's this: store\data \:(OI)(CI)(F) I may have violated some conventions when changing permissions. I'm okay with Posix permissions but this is a bit opaque to me.Ī potential clue: It's quite possible that tortoisehg crashed before the problem appeared, or lost network connection. I was working with VPN from home, and that sort of thing can happen. So if Mercurial blocks any files/directories, there might be some block in place, though I wouldn't know how to verify/fix that. All machines which might have been responsible for blocking the dir have rebooted since the problem appeared - except of course for the file server hosting the data. I've also updated the statements above to add the -debug outputs. The random letters/numbers behind the filename changed, because I put some more changes into the file. I'm not quite sure what the reason for my problem was but here is how I bypassed it: That would indicate that it's really not that particular file (which does not exist anyway) but the directory which mercurial attempts to write into.I cloned the remote repository onto my local machine.I opened my local repo, clicked the "synchronize" button and changed the default path from the dysfunctional remote repo to the newly cloned one. ![]() I cloned the "localized" remote repo back to the network drive.I changed the default path on my local repo again, to the new remote clone. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |