CVS checkout aborted..permission denied to rename file - makefile

Hi
i have been running a make file to get the source code from the repository but there has been an error in the process it says:
"cvs [checkout aborted]: cannot rename file xxxx.MSBuild.Interop.dll to xxxx.MSBuild.Interop.dll: Permission denied"
i have searched for this problem but i haven't been able to find some good answer or solution of this problem...
if you have cvs knowledge i ll be grateful if u can help me here.
Thanks

I have the same problem with VirtualBox mount points.
Filesystem vboxsf doesn't allow to checkout with CVS, my error was:
cvs [checkout aborted]: cannot rename file .new.FILE1. to FILE1.php: No such file or directory
Try to play users groups, permissions and even symbolic link on local VM, no way to get it works. Same thing with permissions on Windows (host) side.
I have to checkout on local directory and then copy to vboxsf mount point, from host or local VM.

Related

Permission denied on directory with specific name

This is a weird one... On Ubuntu 14.04 I have a directory called /lib. As root, or on the server as a user with group privileges, I can write to this directory. Over FTP as the same user with group privileges I cannot, I get a Permission Denied error...
If I rename the /lib directory to anything else (in this case /lib-new) I can write to the directory over FTP.
What could be causing a Permission Denied error based purely on the name of the directory?
I've checked and tested the permissions of the directory (777, 775, 755, 664 and 644) as well as the directory above (/public_html - the root directory for the server) and nothing helps, unless I rename the directory something other than lib.
Please help, as SSH-ing into the server to make changes to anything within /lib is time consuming!
EDIT: The FTP server I'm using is ProFTP if it helps.
Try adding RLimitChroot off to /etc/proftpd.conf. May need to restart X for this change to take affect. By default, I think it will do the same thing to /etc directory as well.

Boot2Docker: Can't create directory: Protocol Error

Trying to learn Docker in a windows machine. When I was trying create a new directory inside the shared User folder (/c/Users) by executing sudo mkdir sample but getting an error saying Can't create directory 'sample': Protocol Error.
Any pointers to resolve this issue would be helpful.
VirtualBox does mount automatically C:\users (see VirtualBox Guest Additions), but that does not mean you can create anything directly in C:\Users (not without Administrative privilege, and sudo don't apply here)
You can create anything you want in your own folder: C:\Users\mylogin

ssh and GIT: couldn't resolve hostname

Using Win7, Gitolite, and TortoiseGIT
today I updated my GIT to version 2.6.1, therefore I had to deinstall the old version.
Long time ago I created a ssh-config file to have easier access to my repositories and all was working fine since today.
After the update I tried to clone an existing repository and got following error:
ssh: couldn't resolve hostname gitbox: Name or service not known
fatal: Could not read from remote repository.
Please make sure you have the correct access rights and the repository exists.
Seems to me like GIT doesn't know where the ssh-config file is located.
Following helped but I'm not very happy with that solution:
Starting GIT GUI
Trying to clone a repository -> Same error as before
figured out that GIT created a new folder at /c/Users/newUser/
Inside the folder I found .gitconfig
Create .ssh folder here
Copy rsa key and config file here
All working as before
Can someone explain what happened here? Or how can I tell GIT/ssh where my config file was initially located?
Thank you very much!
Can someone explain what happened here?
You need to make sure that HOME is properly set to %USERPROFILE%: by default, git will look for the global config and for .ssh settings in %HOME%.
By default, calling c:\path\to\PortableGit-2.6.1-64-bit\git-cmd.exe would initiate a CMD session with HOME correctly set.
c:\path\to\PortableGit-2.6.1-64-bit\git-bash.exe would do the same for $HOME, in a bash session.

Vagrant SSH Permissions

I am new to Vagrant and get the following error on vagrant up or vagrant ssh:
The private key to connect to this box via SSH has invalid permissions
set on it. The permissions of the private key should be set to 0600, otherwise SSH will
ignore the key. Vagrant tried to do this automatically for you but failed. Please set the
permissions on the following file to 0600 and then try running this command again:
[...]/.vagrant/machines/default/virtualbox/private_key
I have run:
$ sudo chmod 666 [...]/.vagrant/machines/default/virtualbox/private_key
I also tried (600, 777) but still get the same error.
Please can someone tell me what is wrong and how to fix it?
I just had this issue, and I worked around it moving the private_key file to another place, changing its permission, and then creating a symbolic link at the original place.
So,
$ mv [...]/.vagrant/machines/default/virtualbox/private_key /some/path/where/you/can/change/permissions
$ ln -s /some/path/where/you/can/change/permissions [...]/.vagrant/machines/default/virtualbox/private_key
If you're using the Windows Subsystem for Linux (WSL), this error can occur when you're trying to vagrant up in a directory that is outside the user's home directory.
From the Vagrant docs:
If a Vagrant project directory is not within the user's home directory on the Windows system, certain actions that include permission checks may fail (like vagrant ssh). When accessing Vagrant projects outside the WSL Vagrant will skip these permission checks when the project path is within the path defined in the VAGRANT_WSL_WINDOWS_ACCESS_USER_HOME_PATH environment variable.
Changing the VAGRANT_WSL_WINDOWS_ACCESS_USER_HOME_PATH to the current working directory (or a directory above it) can fix this. For example, if your project is in /mnt/c/www, then set the environment variable accordingly:
export VAGRANT_WSL_WINDOWS_ACCESS_USER_HOME_PATH="/mnt/c/www"
I got the same error now. The problem happened because i was trying to do vagrant up in an NTFS partition, just like the error message tell me.
So i created an directory link in my ext4 partition and an simbloc link in my NTFS to solve this. Works Fine now!
Thanks!
I had this same problem and turns out chmod seems to be working fine but is not actually changing permissions, my files where at an NTFS partition, try changing them to an ext4 or similar.
Got this error using otto (which layers on vagrant)
It is def filesystem related, have a fat partition to allow use with windows (used to, no longer). When the permissions couldn't be set on the partition I just copied the whole directory over to my user directory (as I always should have).
Was using git so I just reset to head to get back to my starting place... re-ran:
otto compile
otto dev
up and running now.

GitHub: ssh -T git#github.com -> Permission denied (publickey). [Windows 7]

I have a problem and didn't find anything on stackoverflow or google.
When i run ssh -T git#github.com I get the error Permission denied (publickey).
The helps in the Git Help guide doesn't help.
Can someone help me?
OK i got the solution, maybe someone needs it so here we go:
Ok, i got it finally.
First of all it is to say I am running here the Windows 7 OS in German 64bit! I don't know if this is important.
Well, in this guide: http://help.github.com/win-set-up-git/ they say, that the files where create in C:/Users/[PC-Name]/.ssh/
So in this folder there shall be the files id_rsa and id_rsa.pub. When i looked them up, i wasn't able to find even the folder. So where are the necessary files?
I run the search and i find them in: C:\Users[yourpcname]\AppData\Local\VirtualStore\Windows\SysWOW64
I don't know why or how they get there. I never typed in this path.
Ok, so now just copy the files and create the .ssh folder in C:/Users/[PC-Name]/ move to the directory .ssh and paste the two files id_rsa and id_rsa.pub.
Then don't run ssh -T git#github.com
but:
ssh -T git#github.com -i <path-to-id_rsa>
and rly take care that you use C:/.../.../ and NOT C:\...\...\..
This solved my problem. Maybe you have the same problem.
Another SO post contains the solution:
Permission denied (publickey) when deploying heroku code. fatal: The remote end hung up unexpectedly
Try to copy id_rsa and id_rsa.pub into the Git Installation folder.
Something like this: C:\users\user\.ssh to C:\Program Files (x86)\Git\.ssh
I wasn't able to find even the folder
That folder can be any folder you want, as long as you define an HOME user environment variable (which isn't defined by default on Windows Xp or Seven)
If you define HOME to C:\path\to\folder, then id_rsa and id_rsa.pub need to be stored in:
C:\path\to\folder\.ssh

Resources