(Didn't have coffee yet.) It resolves the dependency issue but not the
rb-site upgrade issue.
The log was done after installing django evolution from epel-testing
(otherwise it broke on version dependency before ever attempting to run the
upgrade)
On Tuesday, December 8, 2015 at 10:00:18 AM
Should've mentioned running exactly that got me past this error already.
On Monday, December 7, 2015 at 5:21:16 PM UTC+1, Stephen Gallagher wrote:
>
> Hmm, I thought I fixed that version. I'll push an update immediately. If
> you manually run `yum update python-django-evolution
>
It's reviewboard 2.0.1, we are using Git version 1.9.5. I am not the
review board administrator, but I have access to the linux box. If you can
point me to where the logs are that'd be really helpful.
Thanks!
On Monday, December 7, 2015 at 5:02:33 PM UTC-5, David Trowbridge wrote:
>
> What
Hi All,
I am newbie to reviewboard, I have one small question. Does reviewboard has
the functionality of automatic merging the pull request after successfull
code review?
Thanks,
Harshal
--
Supercharge your Review Board with Power Pack:
https://www.reviewboard.org/powerpack/
Want us to
Also the server log is here:
2015-12-08 14:49:54,420 - ERROR - None - rdejournett -
/api/review-requests/5110/diffs/ - Error uploading new diff: Not Found
Traceback (most recent call last):
File
On Monday, December 7, 2015 at 10:55:42 PM UTC-5, Stephen Gallagher wrote:
>
> Did you run this with the recent django-evolution 0.7.6 update? That
> specifically addresses some upgrade issues unique to MySQL.
>
Yes, I am using python-django-evolution-0.7.6-1.el7.noarch with your fix
from Dec
Hi Christian,
Thanks, that was exactly the problem. After switching to InnoDB, the
upgrade to 2.5.2 completes, and I have a working install.
The one other change I had to make was the memcached backend name in
settings_local.py (CacheClass -> MemcacheCache).
I did notice a difference in the
So I got this reviewboard 1.7.12 server assigned to me. We have the need
for some new features from newer versions of reviewboard. So I simply did
easy_install -U ReviewBoard and rb-site upgrade. It failed. I did not have
a recent backup, but luckily rolling back the ReviewBoard python package
Hi Weibo,
There should be a note right before the log output saying to ignore those
errors unless the upgrade fails. It looks like it was completely successful.
What I'd do now is check the Apache error log and the reviewboard.log (if
enabled), and look at the errors there. There should be a
Hi Rob,
We've made a lot of improvements to Bitbucket support since we released
2.0.1 in May of last year. You might find 2.0.21 to work better for you.
Christian
--
Christian Hammond - christ...@beanbaginc.com
Review Board - https://www.reviewboard.org
Beanbag, Inc. -
Hi Harshal,
Review Board does not handle the merging of code into a codebase. Many
companies have different policies on when something is ready to merge, and
many different setups for how code ends up in the codebase, and on top of
that, there's different sets of problems for different SCMs (git,
Hi,
You'll need to reach out to the Bitnami support group. They have a custom
way that Review Board is installed, and it looks like issuing an
easy_install command is not sufficient to update the version Apache is
using. Unfortunately, I don't know the answer to that, but they would.
Christian
Hi Ralph,
Glad to hear it!
The condensediffs savings should definitely be better in 2.5.x.
In 2.0, we condensed by de-duplicating diffs (if you uploaded 3 revisions
of a diff, but a diff for a file remained the same between revisions, we no
longer store multiple copies of it).
In 2.5.x, we
13 matches
Mail list logo
