Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 2007 by [email protected]: error uploading diff with post-review
0.3.2 (path resolution fail)
http://code.google.com/p/reviewboard/issues/detail?id=2007
I create a diff with the following command so that I can see the changes in
our sql scripts between iterations:
svn diff http://svn/marin/branches/iteration-0009/mscm/sql/changes
http://svn/marin/branches/iteration-0010/mscm/sql/changes > sql.diff
I then post-review that diff:
post-review -d --diff-filename=sql.diff
RBTools 0.3.2
Home = /Users/jon
svn info
diff --version
repository info: Path: http://svn/marin, Base path:
/branches/iteration-0009, Supports changesets: False
svn propget reviewboard:url /Users/jon/checkout/branches/iteration-0009
HTTP GETting api/
HTTP GETting http://rb/api/info/
Using the new web API
HTTP GETting http://rb/api/repositories/
HTTP GETting http://rb/api/repositories/1/
HTTP GETting http://rb/api/repositories/1/info/
repository info: Path: http://svn/marin, Base path:
/branches/iteration-0009, Supports changesets: False
Attempting to create review request on http://svn/marin for None
HTTP POSTing to http://rb/api/review-requests/: {'repository':
u'http://svn/marin'}
Review request created
Uploading diff, size: 14301
HTTP POSTing to http://rb/api/review-requests/11742/diffs/:
{'basedir': '/branches/iteration-0009'}
Got API Error 207 (HTTP code 400): The file was not found in the
repository
Error data: {u'stat': u'fail', u'file':
u'/branches/iteration-0009/iteration-0009/mscm/sql/changes/MARIN_COMMON/6595',
u'err': {u'msg': u'The file was not found in the repository', u'code':
207}, u'revision': u'40575'}
As you can see, iteration-0009 gets included twice in the path for some
reason.
Not sure how to work around this one. Ideas?
--
You received this message because you are subscribed to the Google Groups
"reviewboard-issues" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/reviewboard-issues?hl=en.
