Immediately after using the web based svn import tool, the code browser starts throwing 403 errors. Subsequent changes to tool permissions don't appear to have any effect. The actual repo appears to import fine (tested via direct repo reads)
Import URLs tested:
svn://svn.berlios.de/gsmartcontrol
http://svn.berlios.de/svnroot/repos/gsmartcontrol
svn://svn.code.sf.net/p/strawhat/svn/
Closed #578.
je/42cc_7333
The problem appeared after Ming update to
Ming==0.4.4
(confirmed experimentally: 0.4.3 still works, and after 0.4.4 I've observed behavior described in this ticket)Basically, following happened:
Repository
object for given repoapp.repo
always returnsNone
, which results in 403 error during security checks in repository controllerI believe deleting
Repository
is wrong, since it gets created only when app is initially installed (none of the*clone*
tasks/methods doesn't create it). Don't sure why it was added in first place (back in 2011).Why it worked in the first place? Well, I believe it was bug in Ming that actually updated objects marked for deletion, instead of deleting them (seems like this commit fixed that)
The easiest way to fix this for repo, mentioned in ticket is to reinstall tool and run import again, after this change merged.
Thanks for the thorough report, I think you nailed it. BTW, I have found many times where big sweeping changes in 2011 had some hidden bugs that didn't surface until recently :)