://www.vmware.com
On Sun, Mar 28, 2010 at 7:06 PM, plumpy plu...@gmail.com wrote:
When you try to submit a diff, you get this:
'NoneType' object has no attribute 'path2id'
This is the change that broke it:
http://github.com/reviewboard/reviewboard/commit/2f5b56e1f7cd33fd3644...
I reverted
When you try to submit a diff, you get this:
'NoneType' object has no attribute 'path2id'
This is the change that broke it:
http://github.com/reviewboard/reviewboard/commit/2f5b56e1f7cd33fd364481312a9ef078a2741dbe
I reverted scmtools/bzr.py back to the old version and it works fine.
I'm not sure
In the dashboard, the rightmost column is If you click on that,
you get a list of other available columns to display. One of them is
Review ID, which will show you what you want.
I think it's not displayed by default because there's nothing you can
really DO with this number. If there was a
The way we have it set up here is that the repository configured in
Review Board is the URL that contains the .bzr directory. In your
case, this looks like probably
http://a.org/~lead/projects/my_proj_mainline
Now if you're diffing against that directory directly, you'd use '/'
as your base diff
Because a diff file isn't very useful if you can't find the original
files to apply it to. In order to get those, you need the repository
and the base diff path.
On Mar 11, 8:53 am, lzhu lucinda...@hotmail.com wrote:
What is the repository information used for since user needs to
manually post
We use it at Tripwire. I think a lot of people use it internally at
various companies. Did you have some specific question? The
configuration certainly shouldn't be any different than normal.
On Feb 23, 10:54 pm, Rohit rohit7...@gmail.com wrote:
Hi,
Consider me a novice with review board.
I can't speak for the maintainers, since I'm not one, but I wrote the
SVN UUID code. Basically you want to fetch and store the UUID for an
SVN repository any time you create or edit one, correct? That seems
perfectly reasonable to me. I say go for it.
On Feb 20, 8:52 am, Gary M. Josack
Last night I did an easy_install upgrade from the 01/25 build to the
01/29 build. Now no one can leave comments. Clicking on lines of code
on the diff does nothing. Clicking the Review button at the top puts
a little Ship It button and a text entry box at the very bottom of
the page... not in a
why downgrading Review Board doesn't fix it. Hmm.
On Jan 30, 11:17 am, plumpy plu...@gmail.com wrote:
Last night I did an easy_install upgrade from the 01/25 build to the
01/29 build. Now no one can leave comments. Clicking on lines of code
on the diff does nothing. Clicking the Review button
Yeah, both Review Board and Djblets are version 20090130.
On Jan 30, 2:25 pm, Christian Hammond chip...@chipx86.com wrote:
Did you upgrade Djblets and restart Apache?
Christian
--
Christian Hammond - chip...@chipx86.com
VMware, Inc.
On Fri, Jan 30, 2009 at 11:24 AM, plumpy plu
if any javascript files are 404s?
Christian
--
Christian Hammond - chip...@chipx86.com
VMware, Inc.
On Fri, Jan 30, 2009 at 2:41 PM, plumpy plu...@gmail.com wrote:
Yeah, both Review Board and Djblets are version 20090130.
On Jan 30, 2:25 pm, Christian Hammond chip...@chipx86.com wrote
I think you need to bump the djblets required version again. When I
upgraded tonight, I got an error when viewing a review request:
'invalid filter: range'. I did an 'easy_install --upgrade djblets' and
it was fixed.
--~--~-~--~~~---~--~~
You received this message
I used to run the 20081231 build. When I tried to upgrade to 20090107,
I get this when viewing the dashboard. Other pages seem to work fine.
The line in question was added on 12/31, but I'm surprised no one else
has bumped into this?
Environment:
Request Method: GET
Request URL:
That is pretty much exactly what I did last week... Dumped my mysql
database without the table definitions, created a clean database,
loaded it with './manage.py syncdb', and then loaded my old data into
that database (after massaging a few things, like deleting the
permissions table and a few
14 matches
Mail list logo
