top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

repo.or.cz being not well???

0 votes
364 views

Has something changed recently at repo.or.cz, accepting pushes ove ssh, in the past few days? I am getting this:

 $ git push -n -v repo.or.cz:srv/git/alt-git.git/
 403 forbidden
 fatal: Could not read from remote repository.

Please make sure you have the correct access rights and the repository exists.

posted Jul 1, 2013 by anonymous

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

2 Answers

0 votes

Nevermind, I figured it out.

$ git push repo.or.cz:/srv/git/alt-git.git

seems to be the new way to spell the scp style push.
Two points to note, just in case it would help other users, are

(1) The repository hierarchy is no longer under your initial directory and you have to explicitly ask for /srv/$path; and
(2) You used to be able to, but no longer are allowed, to have a trailing slash in your repository URL.

answer Jul 1, 2013 by anonymous
0 votes

Seems like repo is being more picky about the exact path. Have you tried leaving off the trailing slash?

answer Jul 1, 2013 by anonymous
Similar Questions
0 votes
Pushing files to remote repo I get merge errors on files I have not changed in GIT?

I work on some files and push/merge them to the remote server. Sometimes I get merge conflicts on those files and have to fix them. That's completely fine. I get that.

What I don't understand is that sometimes during this process I will get merge conflicts in files _I have never touched_. In fact they are in a completely different series of directories to the one I am working on and someone else project entirely. How am I meant to know how to fix these? I dont know what the other developer wanted to do and if they have done it right.

I thought git only merged/pushed the files you have changed? If someone else has changed Group A files on the remote repo, why must I change my local Group A files when I am _pushing _completely different set of Group B files?

Sure, Id understand if I were pulling files down to my local and had to resolve merge conflicts then, but this isn't happening when I push the files up.

Any help or advice is much appreciated. Sorry if I sound frustrated - I am really trying hard to get my head round this whole git thing but its just so weird.

0 votes
How to change the filetype from binary to text after the file is committed to a git repo?

I have a problem with an already committed file into my repo. This git repo was converted from svn to git some years ago. Last week I have change some lines in a file and I saw in the diff that it is marked as binary (it's a simple .cpp file). I think on the first commit it was detected as an utf-16 file (on windows). But no matter what I do I can't get it back to a "normal text" text file (git does not detect that), but I is now only utf-8. I also replace the whole content of the file with just 'a' and git say it's binary.

Is the only way to get it back to text-mode?:
* copy a utf-8 version of the original file
* delete the file
* make a commit
* add the old file as a new one

I think that will work but it will also break my history.

Is there a better way to get these behavior without losing history?

+3 votes
Git: How to clear history of all repo url that has been accessed from local machine?

My company is upgrading the laptops and so, they're selling the old ones. The problem is, we've been using the old laptops to access remote git repos and the employer would like to clean all possible traces of repo URLs that have been accessed in these laptops. How do I do this? We used Git Bash and Conemu. Will uninstalling Git Bash and Conemu be enough to delete all repo URL history in the laptops? or are these repo URL never been saved to local disk in the first place?

...