I have a developer in another country who is accessing svn from there.
Now we had an issue with the firewall, and he could not access the repository for a while. The firewall error should be fixed now, and it works again for others. This devs gets the error "Error:access to '/svn/path/lots-of-numbers' forbidden" though.
When I tried to find the cause, I found this: link to similar case
However, he sent me the repository link he uses, and it is all in lower case, just as it should be. The permissions are also correct, I just double checked them.
Could the problem lie in the firewall somehow, or does anyone have another suggestion?
Figured it out some time ago, but I guess I should post this here too in case someone else has a similar issue. My problem was actually with permission settings.
What I have now that works, are the exact same settings I had in the svn server previously, only now they are inherited from the root. Sooo...yeah. I have no idea why that actually made a difference.
I've had the same issue for a while and figured out what was wrong. I had a capital where I shouldn't have. My repository was svn/dave, but i had it in the URL as svn/Dave. It let me log in without any issues, but I couldn't actually do anything. Changing it to lower case cleared everything up.
I faced similar situation and I also had changed the permission in the server to inherit from the root.
My problem got solved after I issued the command svn update
Usually it is a practice that I always follow - I run svn status . and then svn update . before firing svn commit.
I skipped svn update this time and caught the error.
It looks like svn update does much more than just update the files.
Related
Can't open file '/svn/p/thegreatwar/svn/db/txn-current-lock': Permission denied
Hello. Me and my mod team have been using an SVN repository created by a now long-since gone mod member. It has been working flawlessly until today, when, just after attempting to commit changes to a file, the system threw the above error. I've been accessing the repository through svn+ssh.
As with everything that keeps working in spite of a general ignorance on HOW it works, I find myself at a complete loss. Indeed I have no coding knowledge and although I've made a few attempts to copy-paste suggested code snippets from this site into the file settings/subversion/properties thing I'm still no closer to solving the issue.
For what it's worth the only user on this computer has full read/write/etc permissions on the folders involved.
I can't seem to access the file that is causing the issue, either. Someone suggested deleting it in another thread but I can't find the /p folder.
I have the same problem modulo project name difference. It seems that mine is caused by the ongoing sourceforge.net transfer to the new datacenter, see https://twitter.com/sfnet_ops
If your svn server is also on SF, this might explain your issue.
I have an existing solution that has previously had no problems. I added two new projects to the solution, completing my dev work with no problem, however when I try to check the solution in I get an error similar to the following:
C:\Project1Path\Project1.csproj: Download of item $/Project1/Project1/Project1.csproj was not completed. Perform a get operation to correct.
I get the same when I try to check in just this project. I have not tried checking in the other new project yet as ideally I want to check everything in together.
I did a Get Latest on the solution on the outside chance that that was what the error was telling me to do but to no avail.
Any help appreciated as sooner or later someone else is going to want to work on the solution.
Many thanks
Simon
I had this issue and when I ran get latest in source control it picked up a non version controlled file with the same name and asked to overwrite it.
If you get that conflict make sure you overwrite the local file.
If you don't get a conflict maybe delete local file manually and then get latest.
I'm not sure that'll work but you could try.
If this isn't resolved with a get latest, go to the actual file in team explorer. If it has a small diagonal icon next to it then right click to resolve the conflict manually. Here you can override the changes.
This is here for anyone else who may run into the problem.
In my case the file was deleted in the TFS. Undo pending changes for this file (undelete it) then try to check in again.
Note: you cannot tell if the file is delete just by looking at solution explorer.
It happened to me as well when I tried to checkin the code from TRUNK after merging from feature branch.
What I did is rolling back the change from TRUNK and merging it again.
I have this issue with Xcode 5 where I'm trying to commit a file to a remote git repository (BitBucket) and getting a pop up window with the following error: "The repository "project_name" could not be reached. Please verify that the repository is online and reachable and try again."
I've been working with this setup for awhile now (since Xcode 4) and didn't have any problems with it. Under Xcode->Preferences->Accounts->Repositories I saw the correct repository, but duplicated. I deleted and added it again, but it didn't help. I tried closing the project and rebooting the computer and it didn't help either. I can see the project's history under Source Control->History. I can access the repository on BitBucket.
Any idea where this is coming from and how to solve this issue?
Not sure if this helps in the tracking down of this problem, but here goes anyway:
I have been connecting to a local network git repository perfectly well for a number of months, but I encountered this problem later yesterday and nothing I did seemed to improve the situation. That included:
Rebooting both the development machine and the server;
Reinstalling Xcode from the App Store;
Re-cloning the project from the git command line (which could see the repository perfectly well);
Checking out the repository from Xcode (I was able to check out but every other operation, such as , Commit, Refresh Status etc. seemed to cause the problem...)
Manipulation the repository with SourceTree (which could also see it fine).
Eventually I stumbled across a solution to my local issue. If I launch Xcode with a wired and wireless network enabled then I can't see the repository. If I close it, disable wifi and relaunch it then I can.
I've not had much opportunity to work out what the difference is (especially as the wifi connects to the same network and is the secondary choice for networking) but it does seem to fix it.
Hope that might help others and hopefully I can find a real explanation soon!
Dave,
Well it seems this had nothing to do with Bitbucket.
The problem was a messed up .git folder on my machine.
My project resides in a Dropbox folder. Somehow, perhaps because of accessing it from different machines, it created copy/duplicate files in the .git folder and it messed up Git. After fixing all the conflicts Git returned to working as usual and I was able to commit from Xcode to the remote repository.
Now, if you encounter this issue, you might not have the same setup as mine or work on Dropbox or any similar service, but I strongly recommend checking your Git folder thoroughly. Good chance something is messed up there.
Check internet connection of system.also quit xcode and reopen it.
I've reinstalled, uninstalled, restarted but "Clone in Mac' on any repository page fails and takes me to the GitHub download page every time.
It was working fine earlier this week but today won't do anything useful.
Any idea why?
It appears not only do you have to log in to the website, you have to log in to the application once as well so it knows you've got it installed. Then refresh the git repo page and the links will automagically change from the download page to an open-application page.
I tried the above suggestions of making sure I was logged in to both the site and the Github-Mac application (which I already was) and installing the CLI tools. This didn't fix it for me. After some digging I found this article which explains how it works.
There should be a server listening on your localhost with https://ghconduit.com:25035/status and it should return a json string that looks something like this:
{"capabilities":["status","unique_id","url-parameter-filepath"],"running":true,"server_version":"5"}
In my case I did not get a result so I tried 127.0.0.1 instead of ghconduit.com and that fixed it.
TL;DR: Add an entry for 127.0.0.1 ghconduit.com to your /etc/hosts file and refresh the github page you are on and the clone on desktop function will work.
As was noted in the comments: You must be logged in to Github for the "Clone on Mac" button work.
(This answer serves mostly to remove this question from the "unanswered" list, since the asker does not seem to be closing it)
Even doing all the above failed for me, but here's what did work:
Open a new tab.
Paste this in the address bar (without quotes):
"github-mac://openRepo/"
On the repo you want to clone, copy the HTTPS clone URL, and paste it after the link above. Press enter.
If the server is listening on your Mac #rjason-lindberg mentioned, then it should open up in GutHub for Mac.
I just had this problem, and I found two steps necessary to get it working: the "log in" answer above, and to open GitHub.app, got to Preferences > Advanced > Install Command Line Tools.
This took no time. I then refreshed the github page, and saw that the link now led to something like: "github-mac://openRepo/https://github.com/......"
Click it and it worked.
I have answered my own question: the trick is TO BE LOGGED IN on the GitHub website. As stated by Neil above, you need to be logged into the application too.
I just tried this and it seemed to work.
Go to Keychain Access and delete all stored passwords (Internet,
application, Web form) with reference to GitHub.
Login in fresh on to the site as well as from the Mac OS desktop application
Store the passwords this time
None of the other answers did the trick for me. But seeing that neither https://ghconduit.com:25035/status nor https://localhost:25035/status was able to connect I realized that the Conduit process wasn't running. It's in "GitHub.app/Contents/Library/LoginItems/GitHub Conduit"
open that, and clone to desktop finally works again.
Don't know why GitHub.app didn't start it by itself, but at least it works now.
edit: After each reboot the GitHub Conduit process needs to be manually started again.
None of the other answers worked for me. I tried logging out (both GitHub and GitHub for Mac), revoking the application access key, quitting the application, reinstalling the GitHub command-line tools (via the Preferences pane), etc.
What did work for me:
Clone (Edit: I think I might have meant "Fork"?*) the repository on github.com. (Yes, through the web interface)
In the GitHub for Mac application, access File > New Repository... and choose "Clone". Select the repo you just created on github.com and clone on, my friend! Clone on.
*It has been a while since I wrote this answer, so I'm not sure if I actually did mean "Clone"... I understand that forking and cloning are certainly not the same thing. I'll leave this answer here in case it happens to inspire a thought for someone!
I had branched out from our QA branch on TFS, mapped it locally and tried making changes to the code locally. When trying to save my code changes, it gives me a warning saying that " the file is write-protected(read only). This has never happened before to me. We tried doing the same thing on my teammates workstation and it works fine for him.
Is it a permissions issue....am I doing something wrong while branching out? I am connected to the right tfs server. I'm not sure what might be causing the files in the branch to be read only.
I'd highly appreciate your help on this.
Thanks
The reason could be that your solution went offline.
What you can try is connect to your main TFS server, Load the solution then just goto File->SourceControl->go online.
Hope this will solve your problem as it solved mine.. :-)
Sorry guys...I'm going to have to answer my own question.
It was the connection to our main tfs server. I connected to the backup tfs server and it works just fine. However, what is baffling is that my teammates can work with the main tfs server just fine.Only I can't.Still puzzled.