[Gitec] Checkout no subversion

Paulo Fernandes de Souza Jr. paulofernandes at interlegis.gov.br
Fri Feb 18 09:07:44 BRST 2005


Luciano e Helder,

 Isto aí tá parecendo um problema de proxy. Provavelmente algum proxy na
sua rede (ou pior, no meio do caminho até o Interlegis) não está
aceitando os comandos do svn. Veja o que diz o FAQ do svn:

What if I'm behind a proxy?
The Subversion client can go through a proxy, if you configure it to do
so. First, edit your "servers" configuration file to indicate which
proxy to use. The files location depends on your operating system. On
Linux or Unix it is located in the directory "~/.subversion". On Windows
it is in "%APPDATA%\Subversion". (Try "echo %APPDATA%", note this is a
hidden directory.)

There are comments in the file explaining what to do. If you don't have
that file, get the latest Subversion client and run any command; this
will cause the configuration directory and template files to be created.

Older versions of Subversion, including the 0.14.3 bootstrap tarball,
use the file ~/.subversion/proxies to define the proxy settings. This
file is ignored by the current version of Subversion.

Next, you need to make sure the proxy server itself supports all the
HTTP methods Subversion uses. Some proxy servers do not support these
methods by default: PROPFIND, REPORT, MERGE, MKACTIVITY, CHECKOUT. In
general, solving this depends on the particular proxy software. For
Squid, the config option is

   #  TAG: extension_methods
   #       Squid only knows about standardized HTTP request methods.
   #       You can add up to 20 additional "extension" methods here.
   #
   #Default:
   # none
   extension_methods REPORT MERGE MKACTIVITY CHECKOUT

(Squid 2.4 and later already knows about PROPFIND.)

See also "What are all the HTTP methods Subversion uses?" for advice on
additional HTTP methods to allow through your proxy.

If it's difficult or impossible to get the proxy to allow Subversion
traffic, but you want to check out the Subversion sources, you may be
able to go around the proxy. Some proxies that filter port 80
nevertheless allow anything on port 81. For this reason, the
svn.collab.net repository server listens on port 81 as well as on port
80. Try:

   svn checkout http://svn.collab.net:81/repos/svn/trunk subversion

and maybe the proxy will let you through. Another strategy is to attempt
the checkout over SSL, which many proxies allow:

   svn checkout https://svn.collab.net/repos/svn/trunk subversion

Of course, your svn client will have to have been built with ssl
support; just pass --with-ssl to subversion's ./configure script. You
can check to see whether the 'https' schema is supported by running svn
--version.


[]s,

Paulo.



Em Qui, 2005-02-17 às 17:29, Luciano De Fázio escreveu:
> Portal COLAB, o ponto de encontro da Comunidade de Desenvolvimento do
> Interlegis.
> http://genesis.interlegis.gov.br
> 
> _______________________________________________________________________________
> Jean,
> 
> A versão instalada é subversion-1.1.0-70738cl
> 
> 
> Jean Rodrigo Ferri escreveu:
> 
> > Portal COLAB, o ponto de encontro da Comunidade de Desenvolvimento do
> > Interlegis.
> > http://genesis.interlegis.gov.br
> >
> > _______________________________________________________________________________ 
> >
> > Luciano De Fázio escreveu:
> >
> > Olá Luciano,
> >
> >> Não consigo baixar os pacotes:
> >>
> >> [root at informatica Products]# svn co 
> >> http://repositorio.interlegis.gov.br/saal/ILSAAL/trunk/ ILSAAL
> >> svn: Requisição REPORT falhou em '/saal/!svn/vcc/default'
> >> svn: REPORT de '/saal/!svn/vcc/default': 400 Bad Request 
> >> (http://repositorio.interlegis.gov.br)
> >
> >
> > O comando está correto!
> >
> > O Helder reportou algo parecido que ocorreu com ele a alguns dias. Eu 
> > testei de casa e consegui baixar normalmente. Talvez seja a versão do 
> > cliente subversion que você está usando, qual é?
> >
> > Testamos com o Conectiva 9 e tb ocorreram problemas parecidos no 
> > commit, mas era porque ele instala a versão 0.algumacoisa do 
> > subversion. Fizemos um upgrade de versão e funcionou.
> >



Mais detalhes sobre a lista de discussão Gitec