#3175: No changeset xxx in the repository
---------------------+------------------------------------------------------
 Reporter:  sven     |       Owner:  jonas                  
     Type:  defect   |      Status:  new                    
 Priority:  high     |   Milestone:                         
Component:  browser  |     Version:  0.9.4                  
 Severity:  major    |    Keywords:  no changeset repository
---------------------+------------------------------------------------------
 running linux fedora core 5, apache 2.0.54, trac 0.9.4, subversion
 1.2.3.-2.1
 current subversion revision: 1400
 database using for svn: FSFS

 Subversion (is / seems to be) working just perfectly fine, When I do a
 checkout / update, I get the entire tree as I should. Yet when I try to
 access part of my repository tree with trac using browse source, I get
 this following error:

 No changeset 360 in the repository

 If I check the parent directory in TRAC (..), and change the revision I am
 viewing to 360, I dont get an error, it shows a revision tree, only the
 specific directory is missing. This is correct, since this directory used
 to be in a different location until revision 650 or so.

 in bash, svn list .. -r360 (same as viewing the parent directory in trac)
 also does NOT show me the directory, which is correct.

 svn list . -r360 in that specific directory returns content, showing me it
 to actually should exist.

 now, is this a subversion error or trac error? Obviously, this directory
 didnt exist before, it was moved in place there aournd r650.. so if didnt
 exist in r360, right..  but why r360? svn log doesnt show any commit at
 all in that area of the tree on r360, and even so, trac will NOT show me
 the HEAD tree because r360 doesnt exist.. but it so does! In bash, an ls
 in the repos/db/revs directory also shows file 360 to be there, as it
 should.

 I just started to use trac, and I really like it, but Im directly stuck at
 this one. any help please? Dunho if the severity and priority is set ok,
 but to me it is. TRAC is pretty much unusable to me if I cant browse
 source,

-- 
Ticket URL: <http://projects.edgewall.com/trac/ticket/3175>
The Trac Project <http://trac.edgewall.com/>
_______________________________________________
Trac-Tickets mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac-tickets

Reply via email to