Re: Upgrading from 1.0.6 to 2.0.x - suggestions and recommendations?
-Original Message- From: Srinidhi B S srinidhi...@gmail.com Reply: Srinidhi B S srinidhi...@gmail.com Date: March 8, 2015 at 1:52:41 AM To: Christian Hammond christ...@beanbaginc.com Cc: reviewboard@googlegroups.com reviewboard@googlegroups.com Subject: Re: Upgrading from 1.0.6 to 2.0.x - suggestions and recommendations? Wow! Thanks a lot for the quick response, Christian! Really appreciate it! On Sun, Mar 8, 2015 at 2:58 PM, Christian Hammond wrote: Okay, I guess I was a bit confused here by which versions you're trying when. The Django Evolution is too new issue would apply if upgrading to a 1.7.x release. If you're upgrading to 2.0.13, then you *do* want/need the latest Django Evolution. I'm directly upgrading from ReviewBoard 1.0.6 to 2.0.13 (on a different server) Let's sort of start over here. With a clean, upstream Review Board release, and the latest Django Evolution, can you show a complete 'rb-site upgrade' attempt? Sounds like a plan. The output of 'rb-site upgrade' in my first post contains exactly this info (since I saw you asked for the same details in a different thread). Anyway, since we are starting over Yeah, it's hard to keep track of things across threads. This is one advantage for companies with support contracts -- all information is in one place, so we can easily look it all up, merge related discussions, store additional information on your setup, etc. Plus, we have a better system in place for ensuring all communication occurs quickly, and confidentially, which makes these kinds of issues easier to sort out. Thanks for the info. I'm also going to need dumps (with data) for the django_project_version and django_evolution tables. (It's past 3AM here, so I'm unlikely to be up much longer tonight, but will take a look if I am.) Christian -- Supercharge your Review Board with Power Pack: https://www.reviewboard.org/powerpack/ Want us to host Review Board for you? Check out RBCommons: https://rbcommons.com/ Happy user? Let us know! https://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Upgrading from 1.0.6 to 2.0.x - suggestions and recommendations?
Thank you so much David and Christian for your responses! I was almost
losing hope once again and hence, didn't check back for the last 4
days. :)
On Wed, Mar 4, 2015 at 8:43 AM, Christian Hammond chip...@chipx86.com wrote:
The problem is that your django_evolution you too new. We didn't have strict
enough dependency version range requirements back in 1.7.6, so you'll run
into some of this. You'll need to grab django_evolution 0.6.9 at the newest.
I was going to run a final test with downgrading django_evolution
since I read a couple of issues on the issue tracker that mention
problems with changing the field type. Your response confirms what I
was planning to try out this weekend. :)
So this is what I followed:
1. easy_install django_evolution==0.6.9
2. Modify ReviewBoard-2.0.13-py2.6.egg/EGG-INFO/requires.txt to use
django_evolution 0.6.9
3. Reload the mysql dump
4. rb-site upgrade /srv/www/htdocs/reviewboard/ -- --debug
Rebuilding directory structure
Updating database. This may take a while.
The log output below, including warnings and errors,
can be ignored unless upgrade fails.
-- begin log output --
Creating tables ...
Upgrading Review Board from 1.0.6 to 2.0.13
There are unapplied evolutions for auth.
There are unapplied evolutions for sessions.
There are unapplied evolutions for accounts.
There are unapplied evolutions for attachments.
There are unapplied evolutions for changedescs.
There are unapplied evolutions for diffviewer.
There are unapplied evolutions for hostingsvcs.
There are unapplied evolutions for reviews.
There are unapplied evolutions for scmtools.
There are unapplied evolutions for site.
Adding baseline version for new models
Evolutions in attachments baseline: file_attachment_orig_filename,
file_attachment_file_max_length_512, file_attachment_repo_info,
file_attachment_repo_path_no_index,
file_attachment_repo_revision_max_length_64
Evolutions in site baseline: localsite_public
Evolutions in hostingsvcs baseline: account_hosting_url,
account_hosting_url_max_length_255, account_unique_together_baseline
Project signature has changed - an evolution is required
Installing custom SQL ...
Installing indexes ...
Installed 0 object(s) from 0 fixture(s)
Registering new SCM Tool Plastic SCM
(reviewboard.scmtools.plastic.PlasticTool) in database
CommandError: Error: Failed to find an SQL or Python evolution named
unique_together_baseline
But this file is available -
/usr/local/lib64/python2.6/site-packages/ReviewBoard-2.0.13-py2.6.egg/reviewboard/accounts/evolutions/unique_together_baseline.py
Turns out, this is the problem:
from django_evolution.mutations import ChangeMeta
From the NEWS file of django_evolution, this was introduced in 0.7.0.
Anyway to move forward from here?
Regards,
Srinidhi.
On Tuesday, March 3, 2015, David Trowbridge trowb...@gmail.com wrote:
Hi,
So I'm by far not an expert on the evolutions, but that change looks like
it's likely to break things pretty badly (in particular, file-attachment
only review requests). Christian, any thoughts on what's causing the errors?
-David
On Fri, Feb 27, 2015 at 7:40 AM Srinidhi B S srinidhi...@gmail.com
wrote:
Hi,
On Thu, Jan 29, 2015 at 10:39 PM, Srinidhi B S srinidhi...@gmail.com
wrote:
Hello Everyone,
I'm (finally!) preparing to upgrade our very old ReviewBoard instance
from 1.0.6 to 2.0.12. I've been worried / concerned about the upgrade
path.
snip/
The following are the changes that could not be resolved:
The application markup has been deleted
In model reviews.DefaultReviewer:
In field 'repository':
Property 'null' has changed
In model reviews.ReviewRequest:
In field 'repository':
Property 'null' has changed
CommandError: Your models contain changes that Django Evolution cannot
resolve automatically.
--- % ---
We had almost given up with the direct upgrade method and deciding to
go with an upgrade plan of ReviewBoard 1.0.6 to 1.7.6 and then
upgrading to 2.0.12. We still had to manually handle some of the
apache and django configurations, which weren't too difficult to
figure out - but it would have been easier if this information was
available in a single location.
Yesterday, I decided to take a look at the above django-evolution
errors. I was able to successfully resolve the above Property 'null'
has changed errors after making the following changes:
diff --git a/reviewboard/reviews/evolutions/null_repository.py
b/reviewboard/reviews/evolutions/null_repository.py
index 4320d03..e7c460c 100644
--- a/reviewboard/reviews/evolutions/null_repository.py
+++ b/reviewboard/reviews/evolutions/null_repository.py
@@ -4,5 +4,5 @@ from django_evolution.mutations import ChangeField
MUTATIONS = [
-ChangeField('ReviewRequest', 'repository', initial=None, null=True)
+ChangeField('ReviewRequest', 'repository', initial=None)
]
diff --git
Re: Upgrading from 1.0.6 to 2.0.x - suggestions and recommendations?
Wow! Thanks a lot for the quick response, Christian! Really appreciate it! On Sun, Mar 8, 2015 at 2:58 PM, Christian Hammond christ...@beanbaginc.com wrote: Okay, I guess I was a bit confused here by which versions you're trying when. The Django Evolution is too new issue would apply if upgrading to a 1.7.x release. If you're upgrading to 2.0.13, then you *do* want/need the latest Django Evolution. I'm directly upgrading from ReviewBoard 1.0.6 to 2.0.13 (on a different server) Let's sort of start over here. With a clean, upstream Review Board release, and the latest Django Evolution, can you show a complete 'rb-site upgrade' attempt? Sounds like a plan. The output of 'rb-site upgrade' in my first post contains exactly this info (since I saw you asked for the same details in a different thread). Anyway, since we are starting over I cleaned up ReviewBoard (since I had modified some files) and django_evolution (multiple versions). Re-installed ReviewBoard using: easy_install -U ReviewBoard Imported the database dump from my 1.0.6 server. # rb-site upgrade /srv/www/htdocs/reviewboard/ Rebuilding directory structure Updating database. This may take a while. The log output below, including warnings and errors, can be ignored unless upgrade fails. -- begin log output -- Creating tables ... Upgrading Review Board from 1.0.6 to 2.0.13 There are unapplied evolutions for auth. There are unapplied evolutions for contenttypes. There are unapplied evolutions for sessions. There are unapplied evolutions for accounts. There are unapplied evolutions for attachments. There are unapplied evolutions for changedescs. There are unapplied evolutions for diffviewer. There are unapplied evolutions for hostingsvcs. There are unapplied evolutions for reviews. There are unapplied evolutions for scmtools. There are unapplied evolutions for site. Adding baseline version for new models Evolutions in attachments baseline: file_attachment_orig_filename, file_attachment_file_max_length_512, file_attachment_repo_info, file_attachment_repo_path_no_index, file_attachment_repo_revision_max_length_64 Evolutions in site baseline: localsite_public Evolutions in hostingsvcs baseline: account_hosting_url, account_hosting_url_max_length_255, account_unique_together_baseline Project signature has changed - an evolution is required Installing custom SQL ... Installing indexes ... Installed 0 object(s) from 0 fixture(s) Registering new SCM Tool Plastic SCM (reviewboard.scmtools.plastic.PlasticTool) in database The stored evolutions do not completely resolve all model changes. Run `./manage.py evolve --hint` to see a suggestion for the changes required. The following are the changes that could not be resolved: The application markup has been deleted In model reviews.DefaultReviewer: In field 'repository': Property 'null' has changed In model reviews.ReviewRequest: In field 'repository': Property 'null' has changed CommandError: Your models contain changes that Django Evolution cannot resolve automatically. I'm also going to need the results of: rb-site manage /path/to/site list-evolutions # rb-site manage /srv/www/htdocs/reviewboard/ list-evolutions /usr/lib64/python2.6/site-packages/setuptools/package_index.py:7: DeprecationWarning: the md5 module is deprecated; use hashlib instead from md5 import md5 Applied evolutions for 'attachments': file_attachment_orig_filename file_attachment_file_max_length_512 file_attachment_repo_info file_attachment_repo_path_no_index file_attachment_repo_revision_max_length_64 Applied evolutions for 'diffviewer': add_parent_diffs filediff_filenames_1024_chars Applied evolutions for 'hostingsvcs': account_hosting_url account_hosting_url_max_length_255 account_unique_together_baseline Applied evolutions for 'reviews': change_descriptions last_review_timestamp shipit_count Applied evolutions for 'scmtools': bugzilla_url_charfield Applied evolutions for 'site': localsite_public And a full SQL schema database dump (without any data). Schema dump is attached. Regards, Srinidhi. -- Supercharge your Review Board with Power Pack: https://www.reviewboard.org/powerpack/ Want us to host Review Board for you? Check out RBCommons: https://rbcommons.com/ Happy user? Let us know! https://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. rb-schema.sql Description: application/sql
Re: Upgrading from 1.0.6 to 2.0.x - suggestions and recommendations?
Okay, I guess I was a bit confused here by which versions you're trying when. The Django Evolution is too new issue would apply if upgrading to a 1.7.x release. If you're upgrading to 2.0.13, then you *do* want/need the latest Django Evolution. Let's sort of start over here. With a clean, upstream Review Board release, and the latest Django Evolution, can you show a complete 'rb-site upgrade' attempt? I'm also going to need the results of: rb-site manage /path/to/site list-evolutions And a full SQL schema database dump (without any data). Christian -- Christian Hammond - christ...@beanbaginc.com Review Board - https://www.reviewboard.org Beanbag, Inc. - https://www.beanbaginc.com -Original Message- From: Srinidhi B S srinidhi...@gmail.com Reply: reviewboard@googlegroups.com reviewboard@googlegroups.com Date: March 8, 2015 at 1:24:40 AM To: reviewboard@googlegroups.com reviewboard@googlegroups.com Subject: Re: Upgrading from 1.0.6 to 2.0.x - suggestions and recommendations? Thank you so much David and Christian for your responses! I was almost losing hope once again and hence, didn't check back for the last 4 days. :) On Wed, Mar 4, 2015 at 8:43 AM, Christian Hammond wrote: The problem is that your django_evolution you too new. We didn't have strict enough dependency version range requirements back in 1.7.6, so you'll run into some of this. You'll need to grab django_evolution 0.6.9 at the newest. I was going to run a final test with downgrading django_evolution since I read a couple of issues on the issue tracker that mention problems with changing the field type. Your response confirms what I was planning to try out this weekend. :) So this is what I followed: 1. easy_install django_evolution==0.6.9 2. Modify ReviewBoard-2.0.13-py2.6.egg/EGG-INFO/requires.txt to use django_evolution 0.6.9 3. Reload the mysql dump 4. rb-site upgrade /srv/www/htdocs/reviewboard/ -- --debug Rebuilding directory structure Updating database. This may take a while. The log output below, including warnings and errors, can be ignored unless upgrade fails. -- -- Creating tables ... Upgrading Review Board from 1.0.6 to 2.0.13 There are unapplied evolutions for auth. There are unapplied evolutions for sessions. There are unapplied evolutions for accounts. There are unapplied evolutions for attachments. There are unapplied evolutions for changedescs. There are unapplied evolutions for diffviewer. There are unapplied evolutions for hostingsvcs. There are unapplied evolutions for reviews. There are unapplied evolutions for scmtools. There are unapplied evolutions for site. Adding baseline version for new models Evolutions in attachments baseline: file_attachment_orig_filename, file_attachment_file_max_length_512, file_attachment_repo_info, file_attachment_repo_path_no_index, file_attachment_repo_revision_max_length_64 Evolutions in site baseline: localsite_public Evolutions in hostingsvcs baseline: account_hosting_url, account_hosting_url_max_length_255, account_unique_together_baseline Project signature has changed - an evolution is required Installing custom SQL ... Installing indexes ... Installed 0 object(s) from 0 fixture(s) Registering new SCM Tool Plastic SCM (reviewboard.scmtools.plastic.PlasticTool) in database CommandError: Error: Failed to find an SQL or Python evolution named unique_together_baseline But this file is available - /usr/local/lib64/python2.6/site-packages/ReviewBoard-2.0.13-py2.6.egg/reviewboard/accounts/evolutions/unique_together_baseline.py Turns out, this is the problem: from django_evolution.mutations import ChangeMeta From the NEWS file of django_evolution, this was introduced in 0.7.0. Anyway to move forward from here? Regards, Srinidhi. On Tuesday, March 3, 2015, David Trowbridge wrote: Hi, So I'm by far not an expert on the evolutions, but that change looks like it's likely to break things pretty badly (in particular, file-attachment only review requests). Christian, any thoughts on what's causing the errors? -David On Fri, Feb 27, 2015 at 7:40 AM Srinidhi B S wrote: Hi, On Thu, Jan 29, 2015 at 10:39 PM, Srinidhi B S wrote: Hello Everyone, I'm (finally!) preparing to upgrade our very old ReviewBoard instance from 1.0.6 to 2.0.12. I've been worried / concerned about the upgrade path. The following are the changes that could not be resolved: The application markup has been deleted In model reviews.DefaultReviewer: In field 'repository': Property 'null' has changed In model reviews.ReviewRequest: In field 'repository': Property 'null' has changed CommandError: Your models contain changes that Django Evolution cannot resolve automatically. --- % --- We had almost given up with the direct
Re: Issue 3750 in reviewboard: The review request draft banner overlays lines in diffs when scrolling to anchors
Updates: Status: Fixed Comment #1 on issue 3750 by chip...@gmail.com: The review request draft banner overlays lines in diffs when scrolling to anchors https://code.google.com/p/reviewboard/issues/detail?id=3750 Fixed in 2.0.13. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard-issues+unsubscr...@googlegroups.com. To post to this group, send email to reviewboard-issues@googlegroups.com. Visit this group at http://groups.google.com/group/reviewboard-issues. For more options, visit https://groups.google.com/d/optout.
How to create post-commit Review request using ereviewboard plug-in in Eclipse
Dear, I am able to create pre-commit Review request from ereviewboard plug-in in Eclipse. This is the one which I am doing before check-in my code to the SVN. Is there any way by which we can create Review request after checking-in code into SVN (Post-commit) ? Thanks, Tapas -- Supercharge your Review Board with Power Pack: https://www.reviewboard.org/powerpack/ Want us to host Review Board for you? Check out RBCommons: https://rbcommons.com/ Happy user? Let us know! https://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Upgrading from 1.0.6 to 2.0.x - suggestions and recommendations?
Hey Christian, On Sun, Mar 8, 2015 at 3:45 PM, Christian Hammond christ...@beanbaginc.com wrote: snip/ This is one advantage for companies with support contracts -- all information is in one place, so we can easily look it all up, merge related discussions, store additional information on your setup, etc. Plus, we have a better system in place for ensuring all communication occurs quickly, and confidentially, which makes these kinds of issues easier to sort out. Thanks for the info. I'm also going to need dumps (with data) for the django_project_version and django_evolution tables. Attached is the dump of data for the two tables you requested. (It's past 3AM here, so I'm unlikely to be up much longer tonight, but will take a look if I am.) I really appreciate your patience and assistance, Christian! :) Regards, Srinidhi. -- Supercharge your Review Board with Power Pack: https://www.reviewboard.org/powerpack/ Want us to host Review Board for you? Check out RBCommons: https://rbcommons.com/ Happy user? Let us know! https://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. rb-django_prjv_evolution.sql Description: application/sql
Re: Issue 3262 in reviewboard: Add repository page shows confusing note about SSH public key
Comment #4 on issue 3262 by raav...@gmail.com: Add repository page shows confusing note about SSH public key https://code.google.com/p/reviewboard/issues/detail?id=3262 I have observed the same message in RB version 2.0.13. Is this fix already ported to 2.0.x? Thanks -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard-issues+unsubscr...@googlegroups.com. To post to this group, send email to reviewboard-issues@googlegroups.com. Visit this group at http://groups.google.com/group/reviewboard-issues. For more options, visit https://groups.google.com/d/optout.
Configuring GitLab in RB 2.0.13
Hi, Greetings. What are requirements/procedure to configure GitLab repositories in RB 2.0.13? Reason to post this question is: 1. Unable to find the specific perquisites to be fulfilled before using GitLab + RB (both are not under same service account/ also not as root). 2. GitLab process documentation isn't clear to find the perquisites. 3. Baisc Git repository configuration works fine but GitLab procedure doesn't work. 4. GitLab RB services are owned and hosted by difference teams and service account. 5. What is the process we need to follow in this kind of environment? Error produced - refer attachment GitLab hosting account linking is successful in RB PS: I am able to access (clone, commit) repositories using the same link and credentials mentioned in RB repository configuration). Please suggest. Thanks, Ravi -- Supercharge your Review Board with Power Pack: https://www.reviewboard.org/powerpack/ Want us to host Review Board for you? Check out RBCommons: https://rbcommons.com/ Happy user? Let us know! https://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
