#2404: added file missing from changeset
------------------------------------+---------------------------------------
 Reporter:  [EMAIL PROTECTED]  |        Owner:  mgood   
     Type:  defect                  |       Status:  assigned
 Priority:  normal                  |    Milestone:  0.9.3   
Component:  changeset view          |      Version:  0.9     
 Severity:  major                   |   Resolution:          
 Keywords:  dot, hidden             |  
------------------------------------+---------------------------------------
Comment (by cboos):

 Sorry, but "same here" comments aren't going to help make any progress on
 this topic.
 What we need is a way to reproduce the problem, like a small dump of a
 repository
 which exhibits the issue...

 As I said above, when I tried to reproduce the issue with a mirror of
 the initial reporter's repository, ''I couldn't'' reproduce the problem,
 which makes me believe that it's an authz issue, because of that line:
 source:trunk/trac/versioncontrol/[EMAIL PROTECTED]

 To [EMAIL PROTECTED]: can you please instrument your code
 and do a `resync` once again?
 {{{
 #!diff
 Index: svn_fs.py
 ===================================================================
 --- svn_fs.py   (revision 2633)
 +++ svn_fs.py   (working copy)
 @@ -468,8 +468,10 @@
          for path, change in editor.changes.items():
              if not self.authz.has_permission(path):
                  # FIXME: what about base_path?
 +                print 'XXX no permission for', path
                  continue
              if not (path+'/').startswith(self.scope[1:]):
 +                print 'YYY stupid bug involving', path, self.scope
                  continue
              action = ''
              if not change.path and change.base_path:
 }}}

-- 
Ticket URL: <http://projects.edgewall.com/trac/ticket/2404>
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