diffs for?
Christian
--
Christian Hammond - chi...@chipx86.com javascript:
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Mon, Aug 27, 2012 at 9:36 AM, mxbraun
matthew.bra...@gtempaccount.comjavascript:
wrote:
Hmmm...Thanks for the data point. It's
Do you happen to recall if you stripped out the new 1.7 stuff from the
diff, or did you modify pysvn or RB to handle the new content? We're about
to try something to handle these as well, and are considering the pros/cons
of both approaches.
(I'd prefer the latter, but suspect implementing
*From:* revie...@googlegroups.com javascript: [mailto:
revie...@googlegroups.com javascript:] *On Behalf Of *mxbraun
*Sent:* 27 August 2012 16:29
*To:* revie...@googlegroups.com javascript:
*Subject:* Re: SVN 1.7 support
Do you happen to recall if you stripped out the new 1.7 stuff from
Yesterday, I updated our Reviewboard (1.5.x) to SVN 1.7.6 and pysvn-1.7.6.
It did not have any effect on this issue--the problem is still there. So:
updating to the latest pysvn does *not* solve the problem.
m@
On Tuesday, March 6, 2012 6:01:46 AM UTC-6, daniel@googlemail.com wrote:
I
I'm trying to evolve a very old database (Beta 0.8) to version 1.5,
and running into a problem. When I try the command: rb-site manage /
site/www/legacyrb evolve -- --execute
I get the message:
The stored evolutions do not completely resolve all model changes.
Run `./manage.py
django_evolution.__version__
Let me know what that says.
Is this the same system that ran the old Review Board instance?
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board -http://www.reviewboard.org
VMware, Inc. -http://www.vmware.com
On Mon, Oct 25, 2010 at 12:07 AM, mxbraun
, it seems to work. My
concern is that I'm just not testing thoroughly enough.
If Congratulations--you're done is the answer, hey, I'm all for
that. Just trying to figure out if I understand and should believe
what I'm seeing. :-)
Thanks again,
m@
On Oct 25, 9:54 am, mxbraun matthew.br...@intel.com
Just to clarify: yes, this is on creating a rreview draft, so there
should be no email involved. The user's browser is shown the Server
Error (code 500) page, and the following entry is made in the Transfer/
Apache log:
10.xx.yy.29 - - [11/Oct/2010:20:03:22 -0700] POST /r/new/
HTTP/1.1
exposed).
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board -http://www.reviewboard.org
VMware, Inc. -http://www.vmware.com
On Mon, Oct 11, 2010 at 8:42 PM, mxbraun matthew.br...@intel.com wrote:
Jon,
Did this really do what you wanted? I find myself in much the same
exposed).
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board -http://www.reviewboard.org
VMware, Inc. -http://www.vmware.com
On Mon, Oct 11, 2010 at 8:42 PM, mxbraun matthew.br...@intel.com wrote:
Jon,
Did this really do what you wanted? I find myself in much the same
As recommended by the installation guide, yes. I could torpedo that
next time the problem pops up, and see what happens...
m@
On Oct 12, 12:50 pm, Jon Stevens latch...@gmail.com wrote:
Are you using memcached? Maybe something with that?
On Tue, Oct 12, 2010 at 10:41 AM, mxbraun matthew.br
5) Anyone have any suggestions as to how to proceed with debugging
this, aside from rolling up my sleeves, and tucking in with GDB?
So, I rolled up my sleeves, and tucked in with GDB...The problem
proved to be the issue documented here at the Django project under the
section, If you get a
Hi folks.
Short description: Trying to set up new install of RB 1.0.9 on SLES
10.3. After creating a reviewboard, httpd is crashing, apparently
during user authentication. I doubt the problem is RB directly--more
likely an issue with python interfacing to MySQL. Anyone seen this,
or know how
13 matches
Mail list logo
