You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Christian Vogt <ch...@ticket-international.com> on 2004/09/03 09:42:27 UTC

Subversion bug FOLLOWUP

P:\>svn info
Path: .
URL:  <http://192.168.x.y/repository/>
/prg">http://192.168.x.y/repository/<z>/prg
Repository UUID: e3151fa9-60da-0310-9d9d-eb0e57c2254e
Revision: 2444
Node Kind: directory
Schedule: normal
Last Changed Author: tatjana
Last Changed Rev: 2409
Last Changed Date: 2004-09-01 18:56:16 +0200 (Mi, 01 Sep 2004)
 
 
Maybe I misunderstand this info but why is the revision number 2444 and the
last changed revision 2409 2 days ago. I've checked in yesterday lot of
sourcecode and I'm not "tatjana" ;-)
 
 
cu
 
Christian
 
  _____  


Christian Vogt
Head of development
ticket international GmbH & Co.KG
TechnicPark
D-54550 Daun
fon + 49 6592 9599 - 0
fax  + 49 6592 9599 - 99
christian.vogt@ticket-international.com

-----Ursprüngliche Nachricht-----
Von: Christian Vogt [mailto:christian.vogt@ticket-international.com] 
Gesendet: Freitag, 3. September 2004 11:27
An:       '
Betreff: Subversion bug


Hi,
 
with "svn update"  (and also TortoiseSVN)  I get following message:
 
svn: REPORT request failed on '/repository/!svn/vcc/default'
svn: REPORT of '/repository/!svn/vcc/default': Could not read response body:
connection timed out. (http://192.168.x.y)

Trying to repair it I've done
a) svnadmin verify
b) svnadmin recover
c) svnadmin hotcopy --clean-logs
 
and on clients side
a) svn cleanup
 
several times.
But doesn't work
 
 
System: 
 
Server: Suse 9.1, svn 1.0.6 via Apache 2.0.
Clients: WinXP  svn and TortoiseSVN 1.0.8
 
Is the repository corrupted?
 
cu
 
Christian
 
 
  _____  


Christian Vogt
Head of development
ticket international GmbH & Co.KG
TechnicPark
D-54550 Daun
fon + 49 6592 9599 - 0
fax  + 49 6592 9599 - 99
christian.vogt@ticket-international.com

 

Re: Subversion bug FOLLOWUP

Posted by Greg Hudson <gh...@MIT.EDU>.
When you commit changes, your directory is not automatically updated to
the new revision, only the files you committed.  Do an "svn update" to
update the directory (and all the other files and subdirs) to the most
recent rev. 
http://subversion.tigris.org/project_faq.html#wc-out-of-date discusses
this in slightly greater detail.

Questions like this are more appropriate for
users@subversion.tigris.org.  Can you explain what led you to send your
questions to the dev list, so that we might improve our documentation?


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org