:
Field 'extra_data' has been added
Field 'hosting_account' has been added
*Error: Your models contain changes that Django Evolution cannot resolve
automatically.*
-Chris Eagan
--
Want to help the Review Board project? Donate today at
http://www.reviewboard.org/donate/
Happy user
://www.beanbaginc.com
On Mon, Apr 8, 2013 at 8:35 AM, Chris Eagan cea...@gmail.comjavascript:
wrote:
I attempted to perfom an upgrade of one of our ReviewBoard installations
and I have run into a problem. The first server upgraded fine, but this one
is not working. I folloed some
processing dependencies for django-evolution
On Monday, April 8, 2013 1:57:20 PM UTC-4, Christian Hammond wrote:
Try upgrading to 0.6.9. There were a lot of fixes that went in since your
version.
Christian
On Apr 8, 2013, at 10:53, Chris Eagan cea...@gmail.com javascript:
wrote:
0.6.7
database?
It's complaining about fields that already existed in 1.6.11, which
shouldn't be correct. It's also showing that those evolutions were already
applied.
At any point did you ever downgrade or wipe an evolution?
Christian
On Apr 8, 2013, at 10:59, Chris Eagan cea...@gmail.com
schema history). If all fails, you can restore
the database backup and we can try again.
Christian
--
Christian Hammond - chi...@chipx86.com
Review Board - http://www.reviewboard.org
Beanbag, Inc. - http://www.beanbaginc.com
On Mon, Apr 8, 2013 at 11:17 AM, Chris Eagan cea...@gmail.com
://www.beanbaginc.com
On Tue, Apr 9, 2013 at 6:16 AM, Chris Eagan cea...@gmail.comjavascript:
wrote:
Christian,
Is it possible for me to make manual changes to the database that would
allow this operation to complete? If I understood more about what the error
is describing, I might be able to make
eone else. :)
On Friday, March 24, 2017 at 9:16:05 AM UTC-4, Chris Eagan wrote:
>
> When attempting to perform an rb-site upgrade from version 2.0.18 to
> 2.5.9, I get the following output, ending in an error. If I continue,
> further table creation issues occur and the result is a corrup
eone else. :)
On Friday, March 24, 2017 at 9:16:05 AM UTC-4, Chris Eagan wrote:
>
> When attempting to perform an rb-site upgrade from version 2.0.18 to
> 2.5.9, I get the following output, ending in an error. If I continue,
> further table creation issues occur and the result is a corrup
We recently migrated from Review Board 2.0.x to 2.5.x and I noticed that
there is a new feature for loading information from Bugzilla using the
Bugzilla API. We require authentication on our Bugzilla instance and we are
seeing a lot of errors in our Review Board logs related to Bugzilla
When attempting to perform an rb-site upgrade from version 2.0.18 to 2.5.9,
I get the following output, ending in an error. If I continue, further
table creation issues occur and the result is a corrupted database. I do
have a backup of the database, which I have been using to restore and test
between the two releases I am trying to install?
On Friday, March 24, 2017 at 9:16:05 AM UTC-4, Chris Eagan wrote:
>
> When attempting to perform an rb-site upgrade from version 2.0.18 to
> 2.5.9, I get the following output, ending in an error. If I continue,
> further table creation
That worked, thanks!
On Wednesday, April 5, 2017 at 4:37:44 PM UTC-4, Chris Eagan wrote:
>
> I am trying to trigger a Jenkins Job using WebHooks in Review Board and I
> need to submit a custom payload as form data. After installing the
> https://plugins.jenkins.io/build-token-ro
I am trying to trigger a Jenkins Job using WebHooks in Review Board and I
need to submit a custom payload as form data. After installing
the https://plugins.jenkins.io/build-token-root plugin, I tried using the
following settings.
URL:
nd that's where this is
> failing. It sounds like this only happens periodically, and not every time
> someone authenticates?
>
> Christian
>
> On Tue, Jun 6, 2017 at 12:33 PM, Chris Eagan <cea...@gmail.com
> > wrote:
>
>> I am planning to upgrade our version soon
Sometimes our Review Board server sends emails to the Administrator email
account to report errors. I don't see a setting anywhere to control what
gets sent to the administrators, but some of these issues are ones that we
aren't particularly interested in receiving. For instance, the following
the user who tried to log
> in. Generally speaking, you should only get such e-mails if we have a crash
> bug.
>
> I did a bunch of work to improve the LDAP support in 2.5.12, which should
> also better catch exceptions. Upgrading might prevent those errors from
> showing up.
>
16 matches
Mail list logo
