TortoiseSVN Access to trunk forbidden when trying to create branch - tortoisesvn

I am trying to create a branch off of trunk in my project and Tortoise tells me that "access to '/svn/el_dev/!svn/bc/4656/trunk' forbidden". Does anyone have a clue about what this means and what I am doing wrong? I have verified that none of my colleagues are comitting and I have tried to create the branch at a number of different occasions with the same result.
Thank you!

I had exactly the same kind of error today (that is why I found this question on StackOverflow). It turned out that I did not have read access to one of the subdirectories I wanted to branch, after an accidental change to authz.
So probably you do not have read access to one of the trunk directories.

Related

Error: Commit and push configuration files to Platform.sh

enter image description here
I tried this, but there's an error
enter image description here
Error message says
No .platform/services.yaml file found in the repository.
No .platform/routes.yaml file found in the repository.
enter image description here
but It's definitely there.
i don't understand...
Without seeing your repository, my guess is that those two files haven't been committed to the repository (the ! next to each of them in your third image). You can double-check by doing git status. If they are definitely committed, hop into our slack workspace and/or submit a support ticket so we can take a look at what's happening.
It sounds like you use visual studio and you need to:
add the files to git
commit the files to git
push the file to platform.sh
If you have trouble with this, you may want to use one of the existing template https://docs.platform.sh/development/templates.html and the modify these files.
In general, it is easier to start from a functional solution than a non working one ;-)

Gitlab repository time length and size of of file storage

I am not sure this is the right forum for this question.
I use Gitlab for storing all my codes, version control, etc. since I don' trust my PC. It suddenly dawned on me, will my account get deleted if I don't access it for a while or is there a limit to size of project that I can push there, etc. Basically use Gitlab for file storage also.
I didn't find any relevant answers on google. Can you please point me to these answers?
Gitlab has a maximum auf 10G/repo. If you have larger files you should use Git LFS otherwise git is for small code files. So i don't think that your account is deleted if you are inactive. Otherwise you should get an e-mail with a notification.
https://about.gitlab.com/blog/2015/04/08/gitlab-dot-com-storage-limit-raised-to-10gb-per-repo/
https://docs.gitlab.com/ee/administration/lfs/manage_large_binaries_with_git_lfs.html

GitLab: include branches from a similar project to local repo

i am pretty new to GitLab and have a question concerning branches and updating the local repo.
Around two weeks ago i cloned a project and did a bit of work on it (mainly added one branch). Other people also have local repositories of that same project (hope that makes sense). Now I would like to clone only a single branch of one of those local repos made by other people and include it into my local repo.... How do i do this? Ofc I can clone the branch into a different directory, but my goal is only having one directory with only one name in which that branch is contained, so that I can switch between the branches I had from the beginning and the new branch I cloned.
Basically, in order to be more clear: There is a project called a_proj. Me and another person have cloned a_proj and therefore have local repos on which we do work. The other person added a branch called a_branch which I don't have. I want to include a_branch into my version of a_proj.
Additionally i have a different question concerning updating a branch. What if some person does some work on their local version of a branch I also have on my Local and I want to include their changes, or even change my branch to their version. How could I do that?
Thank you a lot for any helpful answers on this topic. If there is constructive critic about this post or the way I think about GitLab I am happy to hear it, as already mentioned, this is a pretty new topic to me and I want to learn wherever i can!
Okay, i figured it out. Was pretty easy actually once one knows what to do. For information, i am using GitKraken so it might be different for different environments but essentially the idea is to add the other person's project as remote, (where ones own project should also be a remote named origin). Then one can add any branch of those remotes to the Local project, simply by checking out the wanted branch. It then gets added to the Local repository on which work can be done.
I guess that isn't anything new to anybody who uses GitLab but i'll just leave it here in case some noob (Like me) also has this question.

Git - All files have lost executable permission after checkout

I wanted to checkout an older commit to my working directory to mess around with something so I did the following command in the root of my repo:
git checkout 2aa2c5 .
But nothing happened, the # prompt simply came back. I did the command a few more times, but nothing seemed to happen. I then did:
git status
Which showed that I was still on master. I then did:
git checkout master
As I wasn't sure what was happening and just wanted to get back to where I was. It came back with Already on master
However now my website is not accessible, every single file now seems to have the permission 644? I am really not sure what has happened? It looks like although my original attempt to checkout a commit didn't do anything, it has messed with my file permissions, and/or file ownership.
UPDATE: I don't think it is the permission that is the problem. I think the problem is that all the files have changed to root for the owner and group? I was logged in as root when I did the checkout, will that have caused this?
I am new to git and Linux file permission in general, if anyone could shed some light on this I would really appreciate it.
Thanks
Permissions and ownership are really critical for web servers. If you get this wrong, the wrong people (= crackers) can read or modify your files. So make sure you understand what you're doing.
As a rule of thumb, never work as root. One silly mistake (like a flacky mouse that cut&pastes too much) can cost you the work of many hours.
In your case, it seems that the ownership of the files was changed. To fix this, you will have to delete all the files (as root; be careful - if you make a mistake, a lot more that you might ever want will be gone!)
Try to keep the Git repo (i.e. delete everything except for the .git folder) but I fear that running git as root has already messed with some permissions in that folder as well.
So your best bet might be to delete the whole tree (including the .git folder) and clone it again with the correct user.
Related:
http://www.linux.org/threads/file-permissions-chmod.4094/
http://www.linuxquestions.org/linux/answers/Security/Quick_and_Dirty_Guide_to_Linux_File_Permissions

SVN status..how to use that function

In linux, how do I check if someone has not yet committed something?
I remember I made changes on a server once..but forgot to commit. Now, I don't know which server I used to make those changes.
It isn't possible to tell if someone else has uncommitted changes in their working copy, because the status of the working copy of each user isn't sent to the repository.
SVN servers/repositories don't keep track of changes made on clients. You'd need to locate all the possible places where the client changes might be and check for modifications there.
This is one of the tradeoffs of not having the server keep track of everything like Perforce does. On the other hand, having the server keep track of everything can be a pain at times.
A local working copy is just that, local. The Subversion repository can't know which client has uncommitted changes.
FWIW, you can check a local working copy status using svn st
svn help st
There is no way to tell if anyone other than yourself has checked out a revision and made changes which have not been committed. The only way to find out is to login as each user and execute svn status in the appropriate directory.

Resources