oreowide.blogg.se - Tortoisehg push command returned code 1

TORTOISEHG PUSH COMMAND RETURNED CODE 1 HOW TO
TORTOISEHG PUSH COMMAND RETURNED CODE 1 WINDOWS

I cloned the remote repository onto my local machine.

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. The random letters/numbers behind the filename changed, because I put some more changes into the file. I've also updated the statements above to add the -debug outputs. 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.

TORTOISEHG PUSH COMMAND RETURNED CODE 1 HOW TO

So if Mercurial blocks any files/directories, there might be some block in place, though I wouldn't know how to verify/fix that. I was working with VPN from home, and that sort of thing can happen. 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 may have violated some conventions when changing permissions. 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) Since was asked: The permissions for the. hg/wlock (or anything named similarly) in the repo folder. I have found this answer on this site, but I do not have a file. I also tried cloning the repo to a different location, then pushing to the new repo, but that changes nothing.

I made sure to have hidden files shown in the file manager, and I've also looked from Linux, just to make sure. There is only a file called _g_e_m.py.i in that directory. Now, an interesting thing is that the file that Mercurial complains about does not seem to exist in the first place. I also tried editing the changed file in the main repo and committing there: % hg commit -verbose "-message=GEM.py: " -user - "Z:\\GEM.py"Ībort: Permission denied: Z:\\.hg/store\data\._g_e_m.py.i-kbxvue I have not changed permissions on the main repo, I am owner of all data and have also tried assigning myself "full control" (by default I have only read and write - not sure what the difference is, actually), to no avail. I am sure that I have not run out of quota.

TORTOISEHG PUSH COMMAND RETURNED CODE 1 WINDOWS

The main repo is on a (Windows) file server, and I am submitting from a Windows machine. I made a small change to one file in my project, committed locally with no problem, but the push to the main repo fails: % hg -debug push "Z:\"Ībort: Permission denied: Z:\\.hg/store\data\._g_e_m.py.i-dmz4wn I cannot push or commit to my main repository. I've been using Tortoisehg for a while now, with little to no problems but have just run into the following problem: