I am trying to commit to my local repository but it keeps saying "The working copy “Project” failed to commit files.
warning: unable to access '/Users/me/.config/git/attributes': Permission denied"
I tried this Unable to access 'git/attributes'
It worked for a while but after about an hour of working on my project the error comes back.
I don't know if this is related but some storyboard files are randomly marked for Deletion (with the D beside their file name) when trying to commit.
Sicne that .config folder is supposed to be owned by the user, check, whenever you see again this error:
the new owner of that .config folder (to see of it is root)
the process running at that time (like a local BitBucket server running as root),
or your command history (to see if it involved a command like sudo htop)
Related
I delete my unity project which has a .git folder and ask me to create an encryption key I don't know why it asks me to do that, now when I try to add files in git it refuses to add any things and it prompts this error
The file will have its original line endings in your working directory
error: open("Temp/UnityLockfile"): Permission denied
error: unable to index file 'Temp/UnityLockfile'
fatal: adding files failed
Any suggestion
In general the Temp folder is one of the things you do NOT want to be under version control! It should be ignored as mentioned by the first comment! Use this .gitignore file in the root folder of your git project!
Also see Cleaning up and Migrating existing Unity project into new one or another PC where I explained it a bit more in detail and also how to copy your project with only the necessary files.
As said if there is no such file yet simply create it, otherwise adopt the content accordingly.
Also refer to How can I make Git "forget" about a file that was tracked, but is now in .gitignore?.
In your specific case here the error itself is caused because you currently have your project opened in Unity.
In that case there is the - as the name says - LOCK file which ensures you cannot open the same project twice in a second Unity instance.
This file is locked/owned by the Unity Editor process itself and therefore can't be overwritten/accessed by git at the same time.
Now if for some reason after adding the .gitignore file mentioned above this issue still persists you can close Unity, manually delete the Temp folder, make your git merge and reopen Unity.
This is really weird.
I am trying a clean Teamcity 9.1.1 install but the Data Directory is nowhere to be found.
if I access the Global Settings tab under Administration, it lists "C:\Windows\System32\config\systemprofile.BuildServer" - a folder that doesn't exist.
if I try to browse to that folder, it shows me a range of files; uploading a specific file there instead uploads it to C:\Windows\SysWOW64\config\systemprofile.BuildServer.
there is no teamcity-startup.properties file anywhere - I am unable to customize the location of the data directory.
when I restore a backup, the backup files are instead restored to C:\Users\[user name]\.BuildServer rather than in the correct data directory.
Does anyone has any suggestions on how to regain control of the situation? How can I tell TeamCity which data folder to use?
I resolved the situation by:
stopping TC services;
creating a teamcity-startup.properties in [install folder]\conf with the following content:
teamcity.data.path=D:\\[install folder]\\config
restarting TC services;
restoring my backup.
This restored the 9.1.1 install as well as stabilizing the location of the data directory. After this was done, the subsequent installation of 9.1.7 prompted me to uninstall 9.1.1 first (which it hadn’t done the first time around) and the upgrade succeeded.
I believe the system was already compromised at the beginning, unknown to me, due to the data folder being all over the place. Once that was resolved, everything else fell into place.
I am creating openshift application during application creation it will give error mention below....
When I see my open shift account application is created.
An exception occurred while creating local git repository.
Clone operation failed, with failed cleanup: Could not delete file C:\Program Files (x86)\Git\y. Manual cleanup may be required.
So how i do manual clean up git respository
It's most likely because that C:\Program Files (x86)\Git\y might already exist and can't automatically be removed. You'll need to remove that file manually.
I'm guessing that you're trying to clone your application into your C:\Program Files (x86)\Git\ which I wouldn't recommend since this is the binary folder for GIT. Try running the rhc app create in your home folder C:\Users\<yourusername and see if that gives you better results.
Recently I started getting this error everytime I commit to my local Xcode git.
fatal: Not a git repository (or any parent up to mount point /Volumes/xxx)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
I have partitioned my HDD into 2 drives and my source code is on one of them. All my source is local and I'm just using the built in Git with Xcode. Any clues why I get this error?
Check this. You must be missing git init. This is the first command to start with. This command creates an empty Git repository - basically a .git directory
When Xcode makes it's auto-snapshots, prior to a global find-and-replace for instance, the snapshot is created without error. When I select File -> Create Snapshot the machine chugs away for 10-15 minutes (this is posted without hyperbole), and then fails with an error message similar to:
**Unable to create a snapshot**
fatal: unable to stat 'Users/{me}/Library/Caches/Google/Chrome/Default/Cache/f_00476e': No such file or directory
Yes, that's the cache file for my browser. No, it's not explicitly included in my project. How can I tell Xcode to not do this? I am using the default Snapshot folder, which is
/Users/{me}/Documents/Development/KissQuest/Snapshots
PS -> I don't have the courage to test whether or not the Xcode--auto-generated snapshots are valid.
I'll answer my own question for posterity.
For some reason, there was a .git and .gitK lurking in /users/{me}; I killed those and then git init in the project folder and voila, re-initialized and running git.
git init was not enough; I had to purge the folder tree of bad .gits.