repo.or.cz being not well???

repo.or.cz being not well???

[Junio C Hamano]

Has something changed recently at repo.or.cz, accepting pushes over
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.

Re: repo.or.cz being not well???

[Junio C Hamano]

Junio C Hamano <gitster@pobox.com> writes:

> Has something changed recently at repo.or.cz, accepting pushes over
> 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.

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.

Re: repo.or.cz being not well???

[Andreas Schwab]

Junio C Hamano <gitster@pobox.com> writes:

> Has something changed recently at repo.or.cz, accepting pushes over
> 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.

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

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Re: repo.or.cz being not well???

[Kyle McKay]

My apologies.

repo.or.cz recently had some updates to support:

1) smart HTTP fetch
2) smart HTTP push (over https)
3) user removal of projects

Along with those updates it started doing more validation on paths.

I believe all the paths listed on http://repo.or.cz/w/alt-git.git are  
accepted as shown.

I was not previously aware that URLs not shown on that page were  
accepted, thank you for bringing it to my attention.

Do you feel that it's important to accept these alternate URL versions  
that are not listed on the project page:

1) Optional trailing '/'
2) For the ssh scp form, optional leading '/'

Regards,
Kyle

On Jul 1, 2013, at 15:21, Junio C Hamano wrote:
> Junio C Hamano <gitster@pobox.com> writes:
>
>> Has something changed recently at repo.or.cz, accepting pushes over
>> 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.
>
> 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.

Re: repo.or.cz being not well???

[Junio C Hamano]

Kyle McKay <mackyle@gmail.com> writes:

> I was not previously aware that URLs not shown on that page were
> accepted, thank you for bringing it to my attention.
>
> Do you feel that it's important to accept these alternate URL versions
> that are not listed on the project page:
>
> 1) Optional trailing '/'
> 2) For the ssh scp form, optional leading '/'

I am on the fence.  As long as the accepted URL forms are advertised
clearly (which you guys do indeed do), I do not think there is much
reason to spend effort to "loosen" it again.  People can adjust.  On
the other hand, loosening _might_ reduce the cost of "support calls"
(like the one I just did) from long-time users.  I dunno.

I just (1) was curious, as getting "error 403" when I didn't mean to
talk to an HTTP server was strange, and (2) wanted to make sure I am
talking with the same repo.or.cz without a funny MITM.  If I sounded
like complaining, that wasn't intended, and I am sorry.

Thanks for serving the community for all those years.

Re: repo.or.cz being not well???

[Andreas Schwab]

Kyle McKay <mackyle@gmail.com> writes:

> Do you feel that it's important to accept these alternate URL versions
> that are not listed on the project page:
>
> 1) Optional trailing '/'
> 2) For the ssh scp form, optional leading '/'
3) Optional trailing .git

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Re: repo.or.cz being not well???

[Kyle McKay]

On Jul 2, 2013, at 09:55, Andreas Schwab wrote:
> Kyle McKay <mackyle@gmail.com> writes:
>
>> Do you feel that it's important to accept these alternate URL  
>> versions
>> that are not listed on the project page:
>>
>> 1) Optional trailing '/'
>> 2) For the ssh scp form, optional leading '/'
> 3) Optional trailing .git

Thank you for your patience.

The 3 URL variants listed above should all be working again now.

On Jul 1, 2013, at 16:10, Junio C Hamano wrote:
> I just (1) was curious, as getting "error 403" when I didn't mean to
> talk to an HTTP server was strange,

The '403' prefix has also been removed from ssh protocol error  
messages to reduce confusion.

Regards,
Kyle