Re: RB migrate and upgrade from 1.6.16 to 2.0.15
Hi Christian, Tried it there on new install, import d/b and then the upgrade. Before upgrade ID 7 existed just as you say, and after the upgrade 8 exists. Output looks similar in error to the original run. Would any further d/b dumps assist you here? # rb-site upgrade site 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.6.16 to 2.0.15 There are unapplied evolutions for auth. There are unapplied evolutions for contenttypes. 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 Project signature has changed - an evolution is required Installing custom SQL ... Installing indexes ... Installed 0 object(s) from 0 fixture(s) 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 scmtools.Repository: Field 'hosting_account' has been added Field 'extra_data' has been added CommandError: Your models contain changes that Django Evolution cannot resolve automatically. - John On Thursday, 21 May 2015 16:29:27 UTC+1, John McGowan wrote: Hi, I've been trying to upgrade a RB instance that got to 1.6.16 to 2.0.15 on another node (RH6.3 vs RH6.6). I've the prereq packages on: # pip freeze Beaker==1.3.1 cas==0.15 cups==1.0 cupshelpers==1.0 decorator==3.0.1 Django==1.6.11 django-evolution==0.7.5 django-haystack==2.3.1 django-pipeline==1.3.27 Djblets==0.6.28 docutils==0.12 ecdsa==0.13 ethtool==0.6 feedparser==5.2.0 firstboot==1.110 freeipa==2.0.0a0 futures==2.2.0 glusterfs-api==3.6.0.28 iniparse==0.3.1 iotop==0.3.2 ipapython==3.0.0 iwlib==1.0 kerberos==1.1 lxml==2.2.3 M2Crypto==0.20.2 Magic-file-extensions==0.1 Mako==0.3.4 Markdown==2.4.1 MarkupSafe==0.9.2 matplotlib==0.99.1.1 mercurial==3.4 mimeparse==0.1.3 MySQL-python==1.2.5 netaddr==0.7.5 nose==0.10.4 numpy==1.4.1 p4python==2014.1.925900 paramiko==1.15.2 PIL==1.1.7 Pillow==2.8.1 pillowfight==0.2 policycoreutils-default-encoding==0.1 pycrypto==2.6.1 pycurl==7.19.0 Pygments==2.0.2 pygpgme==0.1 pyOpenSSL==0.10 python-dateutil==1.5 python-default-encoding==0.1 python-dmidecode==3.10.13 python-ldap==2.3.10 python-meh==0.11 python-memcached==1.54 python-nss==0.13 pytz===2010h pyxdg==0.18 recaptcha-client==1.0.6 ReviewBoard==2.0.15 rhnlib==2.5.22 rhsm==1.12.5 scdate==1.9.60 sckdump==2.0.5 scservices==0.99.45 scservices.dbus==0.99.45 setools==1.0 six==1.9.0 slip==0.2.20 slip.dbus==0.2.20 slip.gtk==0.2.20 smbc==1.0 SSSDConfig==1.11.6 suds==0.4.1 urlgrabber==3.9.1 virtinst==0.600.0 Whoosh==2.7.0 yum-metadata-parser==1.1.2 D/B setup exactly as the old node with the same d/b|user|pass etc. Method: # rb-site installpath Then going in and dropping the d/b and creating the empty d/b again (I've tried it without dropping the newly created one as well). Taking the latest dump.sql from the old server and loading it into the new d/b Taking the latest htdocs/media/uploaded content to the new server from old # rb-site upgrade path and getting these errors which I've seen mentioned around the web but unsure how to correct and unsure how to read the evolve --hint to fix: 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 ... There are unapplied evolutions for auth. There are unapplied evolutions for contenttypes. 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. Project signature has changed - an evolution is required Installing custom SQL ... Installing indexes ... Installed 0 object(s) from 0 fixture(s) 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 scmtools.Repository: Field
Re: RBTools 0.7.3 is released!
I just tested 0.7.3 and one of the bugs marked as fixed is showing a different error now. I added a comment to the bug with the new error, but I'm not sure if that will automatically reopen it or not. In some ways it's worse now because I had a workaround for the original problem, but not for the new one. The bug is 3864. Please let me know if I need to do anything more to get this issue reopened. Thanks! --Steve On Wednesday, May 27, 2015 at 5:48:26 PM UTC-7, Christian Hammond wrote: Hey everyone, We've put out a new release of RBTools 0.7.3, which fixes quite a number of bugs, including those annoying Unicode issues many of you have hit. It also has some new useful features you may want, like auto-stamping of commits when posting changes for review. Along with this, we've added official support for Python Wheel packages, allowing you to cleanly install with pip. We'll be extending this support to Review Board in the next release. We're also now signing all our builds with our official PGP key ( https://keybase.io/beanbag), so that you can verify anything you download from us is legit. See the news post for more information: https://www.reviewboard.org/news/2015/05/27/rbtools-0-7-3-out-unicode-fixes-and-more/ Christian -- Christian Hammond - chri...@beanbaginc.com javascript: Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com -- 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: After upgrading to ReviewBoard 2.0.15 the existing reviews do not display the diffs correctly
Ok, thank you.
If I wanted to go through and fix the paths of the existing reviews, which
tables, specifically, would I need to go through and look at?
On Wednesday, May 27, 2015 at 12:28:40 PM UTC-4, Papaswede wrote:
I upgraded ReviewBoard from 1.6.11 to 2.0.15. After doing this, I get
error messages when attempting to view the diffs of the existing reviews. I
get messages like:
The file
'('/svn/enrollment/!svn/bc/122232/trunk/4X/enrollment/trunk/trunk/4X/webapps/common/src/main/java/bf/web/common/form/AddEmployeeForm.java'
path not found, 160013)' could not be found in the repository
Where that path definitely is not a valid svn path. It should
be
/svn/enrollment/!svn/bc/122232/trunk/4X/webapps/common/src/main/java/bf/web/common/form/AddEmployeeForm.java.
So, it's like there's stuff being automatically inserted into the svn path
for the file, but I have no idea why as it was working on version 1.6.11.
Any help would be greatly appreciated.
--
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: Issue 3864 in reviewboard: rbt post //depot/path/...@r1,@r2 throws an exception in 0.7.2 and no review request gets created
Updates: Status: Confirmed Comment #4 on issue 3864 by chip...@gmail.com: rbt post //depot/path/...@r1,@r2 throws an exception in 0.7.2 and no review request gets created https://code.google.com/p/reviewboard/issues/detail?id=3864 (No comment was entered for this change.) -- 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.
Re: After upgrading to ReviewBoard 2.0.15 the existing reviews do not display the diffs correctly
Hi,
If svn/Repo1, svn/Repo2, etc. are all independent Subversion repositories, and
not subdirectories within a larger repository, then you should have a
repository entry in Review Board for each.
You shouldn't target trunk, branches, etc., because those are subdirectories.
When posting a change for review against a Subversion repository, RBTools will
send paths that are relative to the root of the repository (say,
/trunk/myproject/README). That then gets accessed relative to the repository
path, giving you something like
https://vcs.ourdomain.com/svn/Repo1/trunk/myproject/README, or, if
misconfigured, something like
https://vcs.ourdomain.com/svn/Repo1/trunk/trunk/myproject/README.
To fix things up by hand, you'll need to modify the diffviewer_filediff table
entries (or FileDiff in the database editor in the admin UI) and change the
paths shown there. The trick is associating the entries with a given review
request. For that, you can try something like:
$ rb-site manage /path/to/site shell
from reviewboard.diffviewer.models import FileDiff
print FileDiff.objects.filter(diffset__history__review_request=review
request ID).values_list('pk', 'source_file')
Where review request ID is replaced with the numeric ID of the review
reuqest. That would show you all FileDiff IDs and their paths for a given
review request.
Christian
--
Christian Hammond - christ...@beanbaginc.com
Review Board - https://www.reviewboard.org
Beanbag, Inc. - https://www.beanbaginc.com
-Original Message-
From: Papaswede papasw...@gmail.com
Reply: reviewboard@googlegroups.com reviewboard@googlegroups.com
Date: May 28, 2015 at 2:32:20 PM
To: reviewboard@googlegroups.com reviewboard@googlegroups.com
Subject: Re: After upgrading to ReviewBoard 2.0.15 the existing reviews do not
display the diffs correctly
Ok, thank you.
If I wanted to go through and fix the paths of the existing reviews, which
tables, specifically, would I need to go through and look at?
Aslo, this may be a dumb question, but I'm not the most Subversion savvy
person in the world. We have our repositories set up like
https://vcs.ourdomain.com/svn/
and then we have the Repositories within there, like
https://vcs.ourdomain.com/svn/Repo1
https://vcs.ourdomain.com/svn/Repo2
and then each repository has
https://vcs.ourdomain.com/svn/Repo1/trunk
https://vcs.ourdomain.com/svn/Repo1/branches
https://vcs.ourdomain.com/svn/Repo1/branches/2012.REL
https://vcs.ourdomain.com/svn/Repo1/branches/2013.REL
...
Are you saying we'd need to point straight to
https://vcs.ourdomain.com/svn/Repo1/ in order for Reviewboard to work
correctly, or can we target trunk or individual branches, etc.?
On Wednesday, May 27, 2015 at 12:28:40 PM UTC-4, Papaswede wrote:
I upgraded ReviewBoard from 1.6.11 to 2.0.15. After doing this, I get
error messages when attempting to view the diffs of the existing reviews. I
get messages like:
The file
'('/svn/enrollment/!svn/bc/122232/trunk/4X/enrollment/trunk/trunk/4X/webapps/common/src/main/java/bf/web/common/form/AddEmployeeForm.java'
path not found, 160013)' could not be found in the repository
Where that path definitely is not a valid svn path. It should
be
/svn/enrollment/!svn/bc/122232/trunk/4X/webapps/common/src/main/java/bf/web/common/form/AddEmployeeForm.java.
So, it's like there's stuff being automatically inserted into the svn path
for the file, but I have no idea why as it was working on version 1.6.11.
Any help would be greatly appreciated.
--
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.
--
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: RB migrate and upgrade from 1.6.16 to 2.0.15
Hey John, Sorry, haven't had time until now. So first, back up your database. I then want you to try this: DELETE FROM django_project_version WHERE id IN (7, 8); There's an issue that's come up a couple of times in django-evolution, which I have not been able to trace, where two entries get recorded for the same timestamp, but one contains the old version of the database schema while the other contains the new version. This *should* correct that. Ideally, you should do this on a copy of the database prior to your previous upgrade, if possible, just to rule out any other modifications made during the failed upgrade process. (In that case, ID #8 may not exist.) Let me know if that works for you! Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On Thu, May 28, 2015 at 3:45 AM, John McGowan john.mcgow...@gmail.com wrote: Hi Christian, Any pointers on this problem? Thanks, John On Thursday, 21 May 2015 16:29:27 UTC+1, John McGowan wrote: Hi, I've been trying to upgrade a RB instance that got to 1.6.16 to 2.0.15 on another node (RH6.3 vs RH6.6). I've the prereq packages on: # pip freeze Beaker==1.3.1 cas==0.15 cups==1.0 cupshelpers==1.0 decorator==3.0.1 Django==1.6.11 django-evolution==0.7.5 django-haystack==2.3.1 django-pipeline==1.3.27 Djblets==0.6.28 docutils==0.12 ecdsa==0.13 ethtool==0.6 feedparser==5.2.0 firstboot==1.110 freeipa==2.0.0a0 futures==2.2.0 glusterfs-api==3.6.0.28 iniparse==0.3.1 iotop==0.3.2 ipapython==3.0.0 iwlib==1.0 kerberos==1.1 lxml==2.2.3 M2Crypto==0.20.2 Magic-file-extensions==0.1 Mako==0.3.4 Markdown==2.4.1 MarkupSafe==0.9.2 matplotlib==0.99.1.1 mercurial==3.4 mimeparse==0.1.3 MySQL-python==1.2.5 netaddr==0.7.5 nose==0.10.4 numpy==1.4.1 p4python==2014.1.925900 paramiko==1.15.2 PIL==1.1.7 Pillow==2.8.1 pillowfight==0.2 policycoreutils-default-encoding==0.1 pycrypto==2.6.1 pycurl==7.19.0 Pygments==2.0.2 pygpgme==0.1 pyOpenSSL==0.10 python-dateutil==1.5 python-default-encoding==0.1 python-dmidecode==3.10.13 python-ldap==2.3.10 python-meh==0.11 python-memcached==1.54 python-nss==0.13 pytz===2010h pyxdg==0.18 recaptcha-client==1.0.6 ReviewBoard==2.0.15 rhnlib==2.5.22 rhsm==1.12.5 scdate==1.9.60 sckdump==2.0.5 scservices==0.99.45 scservices.dbus==0.99.45 setools==1.0 six==1.9.0 slip==0.2.20 slip.dbus==0.2.20 slip.gtk==0.2.20 smbc==1.0 SSSDConfig==1.11.6 suds==0.4.1 urlgrabber==3.9.1 virtinst==0.600.0 Whoosh==2.7.0 yum-metadata-parser==1.1.2 D/B setup exactly as the old node with the same d/b|user|pass etc. Method: # rb-site installpath Then going in and dropping the d/b and creating the empty d/b again (I've tried it without dropping the newly created one as well). Taking the latest dump.sql from the old server and loading it into the new d/b Taking the latest htdocs/media/uploaded content to the new server from old # rb-site upgrade path and getting these errors which I've seen mentioned around the web but unsure how to correct and unsure how to read the evolve --hint to fix: 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 ... There are unapplied evolutions for auth. There are unapplied evolutions for contenttypes. 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. Project signature has changed - an evolution is required Installing custom SQL ... Installing indexes ... Installed 0 object(s) from 0 fixture(s) 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 scmtools.Repository: Field 'hosting_account' has been added Field 'extra_data' has been added CommandError: Your models contain changes that Django Evolution cannot resolve automatically. # rb-site manage path list-evolutions Applied evolutions for 'sessions': session_expire_date_db_index Applied evolutions for 'accounts': is_private Applied evolutions for 'changedescs': fields_changed_longtext Applied evolutions for 'diffviewer': add_parent_diffs filediff_filenames_1024_chars diffset_basedir filediff_status Applied evolutions for 'reviews': change_descriptions last_review_timestamp shipit_count default_reviewer_repositories
Re: After upgrading to ReviewBoard 2.0.15 the existing reviews do not display the diffs correctly
Hi,
Review Board was never intended to work with Subversion repository paths
that point to a subdirectory. Repositories should always point to the root
of the repository, because RBTools and the New Review Request page are
going to try to generate paths that are relative to the root of the
repository. That's how those ended up with the extra trunk in the path a
couple of times.
It looks like you have a mix of changes on your server that either have the
right path or the wrong path. I don't know why it would have worked before
but not now, but we've fixed a large number of Subversion issues since
1.6.x, and rewrote the Subversion backend, so perhaps there's a behavioral
change somewhere. I'd have to know more about how those particular changes
were posted to really help diagnose that.
The right thing to do here is to switch the repository URL to not point to
a subdirectory. However, that will break existing review requests. So what
I'd recommend is archiving the current repository entry (and keeping the
path as-is), and then adding a new repository entry pointing to the root of
the server, and give it the same name. RBTools and the New Review Request
page will do the correct thing, and you won't have this sort of issue going
forward.
That won't fix existing review requests, though. For that, either the
database entries would need to be updated to point to the correct path, or
a patch to Review Board would need to be written that tries to remove that
duplicate information when normalizing the path, for misconfigured
repositories.
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
Beanbag, Inc. - http://www.beanbaginc.com
On Thu, May 28, 2015 at 6:41 AM, Papaswede papasw...@gmail.com wrote:
Oh, and I just noticed that a few of the existing reviews still do work,
but about 90% of them do not. I was clicking through some at random and
found that some do show up correctly. I'm not sure what's wrong with the
ones that aren't showing up.
On Wednesday, May 27, 2015 at 12:28:40 PM UTC-4, Papaswede wrote:
I upgraded ReviewBoard from 1.6.11 to 2.0.15. After doing this, I get
error messages when attempting to view the diffs of the existing reviews. I
get messages like:
The file
'('/svn/enrollment/!svn/bc/122232/trunk/4X/enrollment/trunk/trunk/4X/webapps/common/src/main/java/bf/web/common/form/AddEmployeeForm.java'
path not found, 160013)' could not be found in the repository
Where that path definitely is not a valid svn path. It should
be
/svn/enrollment/!svn/bc/122232/trunk/4X/webapps/common/src/main/java/bf/web/common/form/AddEmployeeForm.java.
So, it's like there's stuff being automatically inserted into the svn
path for the file, but I have no idea why as it was working on version
1.6.11.
Any help would be greatly appreciated.
--
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.
--
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: RBTools 0.7.3 is released!
Thanks, Steve, and sorry for the trouble. We'll start looking into this, and will follow up with you on the bug report. Christian -- Christian Hammond - christ...@beanbaginc.com Review Board - https://www.reviewboard.org Beanbag, Inc. - https://www.beanbaginc.com -Original Message- From: Steve seide.al...@gmail.com Reply: Steve seide.al...@gmail.com Date: May 28, 2015 at 3:23:23 PM To: reviewboard@googlegroups.com reviewboard@googlegroups.com Cc: christ...@beanbaginc.com christ...@beanbaginc.com Subject: Re: RBTools 0.7.3 is released! I just tested 0.7.3 and one of the bugs marked as fixed is showing a different error now. I added a comment to the bug with the new error, but I'm not sure if that will automatically reopen it or not. In some ways it's worse now because I had a workaround for the original problem, but not for the new one. The bug is 3864. Please let me know if I need to do anything more to get this issue reopened. Thanks! --Steve On Wednesday, May 27, 2015 at 5:48:26 PM UTC-7, Christian Hammond wrote: Hey everyone, We've put out a new release of RBTools 0.7.3, which fixes quite a number of bugs, including those annoying Unicode issues many of you have hit. It also has some new useful features you may want, like auto-stamping of commits when posting changes for review. Along with this, we've added official support for Python Wheel packages, allowing you to cleanly install with pip. We'll be extending this support to Review Board in the next release. We're also now signing all our builds with our official PGP key ( https://keybase.io/beanbag), so that you can verify anything you download from us is legit. See the news post for more information: https://www.reviewboard.org/news/2015/05/27/rbtools-0-7-3-out-unicode-fixes-and-more/ Christian -- Christian Hammond - chri...@beanbaginc.com javascript: Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com -- 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: RB migrate and upgrade from 1.6.16 to 2.0.15
Hi John, Try the process again, but instead of ID 7, try deleting ID 6. Basically, they have the same timestamp, but different content, and one is being chosen incorrectly over the other. If deleting 7 didn't fix it, 6 probably will. Christian -- Christian Hammond - christ...@beanbaginc.com Review Board - https://www.reviewboard.org Beanbag, Inc. - https://www.beanbaginc.com -Original Message- From: John McGowan john.mcgow...@gmail.com Reply: reviewboard@googlegroups.com reviewboard@googlegroups.com Date: May 28, 2015 at 2:21:05 PM To: reviewboard@googlegroups.com reviewboard@googlegroups.com Subject: Re: RB migrate and upgrade from 1.6.16 to 2.0.15 Hi Christian, Tried it there on new install, import d/b and then the upgrade. Before upgrade ID 7 existed just as you say, and after the upgrade 8 exists. Output looks similar in error to the original run. Would any further d/b dumps assist you here? # rb-site upgrade site 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.6.16 to 2.0.15 There are unapplied evolutions for auth. There are unapplied evolutions for contenttypes. 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 Project signature has changed - an evolution is required Installing custom SQL ... Installing indexes ... Installed 0 object(s) from 0 fixture(s) 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 scmtools.Repository: Field 'hosting_account' has been added Field 'extra_data' has been added CommandError: Your models contain changes that Django Evolution cannot resolve automatically. - John On Thursday, 21 May 2015 16:29:27 UTC+1, John McGowan wrote: Hi, I've been trying to upgrade a RB instance that got to 1.6.16 to 2.0.15 on another node (RH6.3 vs RH6.6). I've the prereq packages on: # pip freeze Beaker==1.3.1 cas==0.15 cups==1.0 cupshelpers==1.0 decorator==3.0.1 Django==1.6.11 django-evolution==0.7.5 django-haystack==2.3.1 django-pipeline==1.3.27 Djblets==0.6.28 docutils==0.12 ecdsa==0.13 ethtool==0.6 feedparser==5.2.0 firstboot==1.110 freeipa==2.0.0a0 futures==2.2.0 glusterfs-api==3.6.0.28 iniparse==0.3.1 iotop==0.3.2 ipapython==3.0.0 iwlib==1.0 kerberos==1.1 lxml==2.2.3 M2Crypto==0.20.2 Magic-file-extensions==0.1 Mako==0.3.4 Markdown==2.4.1 MarkupSafe==0.9.2 matplotlib==0.99.1.1 mercurial==3.4 mimeparse==0.1.3 MySQL-python==1.2.5 netaddr==0.7.5 nose==0.10.4 numpy==1.4.1 p4python==2014.1.925900 paramiko==1.15.2 PIL==1.1.7 Pillow==2.8.1 pillowfight==0.2 policycoreutils-default-encoding==0.1 pycrypto==2.6.1 pycurl==7.19.0 Pygments==2.0.2 pygpgme==0.1 pyOpenSSL==0.10 python-dateutil==1.5 python-default-encoding==0.1 python-dmidecode==3.10.13 python-ldap==2.3.10 python-meh==0.11 python-memcached==1.54 python-nss==0.13 pytz===2010h pyxdg==0.18 recaptcha-client==1.0.6 ReviewBoard==2.0.15 rhnlib==2.5.22 rhsm==1.12.5 scdate==1.9.60 sckdump==2.0.5 scservices==0.99.45 scservices.dbus==0.99.45 setools==1.0 six==1.9.0 slip==0.2.20 slip.dbus==0.2.20 slip.gtk==0.2.20 smbc==1.0 SSSDConfig==1.11.6 suds==0.4.1 urlgrabber==3.9.1 virtinst==0.600.0 Whoosh==2.7.0 yum-metadata-parser==1.1.2 D/B setup exactly as the old node with the same d/b|user|pass etc. Method: # rb-site installpath Then going in and dropping the d/b and creating the empty d/b again (I've tried it without dropping the newly created one as well). Taking the latest dump.sql from the old server and loading it into the new d/b Taking the latest htdocs/media/uploaded content to the new server from old # rb-site upgrade path and getting these errors which I've seen mentioned around the web but unsure how to correct and unsure how to read the evolve --hint to fix: 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 ... There are unapplied evolutions for auth. There are unapplied evolutions for contenttypes. There are unapplied evolutions for accounts. There are unapplied evolutions for attachments.
Re: After upgrading to ReviewBoard 2.0.15 the existing reviews do not display the diffs correctly
Ok, thank you.
If I wanted to go through and fix the paths of the existing reviews, which
tables, specifically, would I need to go through and look at?
Aslo, this may be a dumb question, but I'm not the most Subversion savvy
person in the world. We have our repositories set up like
https://vcs.ourdomain.com/svn/
and then we have the Repositories within there, like
https://vcs.ourdomain.com/svn/Repo1
https://vcs.ourdomain.com/svn/Repo2
and then each repository has
https://vcs.ourdomain.com/svn/Repo1/trunk
https://vcs.ourdomain.com/svn/Repo1/branches
https://vcs.ourdomain.com/svn/Repo1/branches/2012.REL
https://vcs.ourdomain.com/svn/Repo1/branches/2013.REL
...
Are you saying we'd need to point straight to
https://vcs.ourdomain.com/svn/Repo1/ in order for Reviewboard to work
correctly, or can we target trunk or individual branches, etc.?
On Wednesday, May 27, 2015 at 12:28:40 PM UTC-4, Papaswede wrote:
I upgraded ReviewBoard from 1.6.11 to 2.0.15. After doing this, I get
error messages when attempting to view the diffs of the existing reviews. I
get messages like:
The file
'('/svn/enrollment/!svn/bc/122232/trunk/4X/enrollment/trunk/trunk/4X/webapps/common/src/main/java/bf/web/common/form/AddEmployeeForm.java'
path not found, 160013)' could not be found in the repository
Where that path definitely is not a valid svn path. It should
be
/svn/enrollment/!svn/bc/122232/trunk/4X/webapps/common/src/main/java/bf/web/common/form/AddEmployeeForm.java.
So, it's like there's stuff being automatically inserted into the svn path
for the file, but I have no idea why as it was working on version 1.6.11.
Any help would be greatly appreciated.
--
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: Is it possible to integrate Sonar Qube Review tool with Review Board.
There's certainly no such integration today. I'm not at all familiar with SonarQube, but if it has APIs you could probably build something using Review Board's extensions framework. -David On Thu, May 28, 2015 at 10:03 AM Narayan kumar Ch narayan@gmail.com wrote: As part of Developers' self review, we are using Sonar Qube and Review Board for peer Review. Is there any way to integrate SonarQube with Review Board? -- 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. -- 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: Issue 2696 in reviewboard: Add comment missing towards the end of a review
Comment #8 on issue 2696 by issamant...@gmail.com: Add comment missing towards the end of a review https://code.google.com/p/reviewboard/issues/detail?id=2696 This is a fantastic website and I can not recommend you guys enough. Full of useful resource and great layout very easy on the eyes. http://seo-traffic.net/ -- 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.
Re: RB migrate and upgrade from 1.6.16 to 2.0.15
Hi Christian, Any pointers on this problem? Thanks, John On Thursday, 21 May 2015 16:29:27 UTC+1, John McGowan wrote: Hi, I've been trying to upgrade a RB instance that got to 1.6.16 to 2.0.15 on another node (RH6.3 vs RH6.6). I've the prereq packages on: # pip freeze Beaker==1.3.1 cas==0.15 cups==1.0 cupshelpers==1.0 decorator==3.0.1 Django==1.6.11 django-evolution==0.7.5 django-haystack==2.3.1 django-pipeline==1.3.27 Djblets==0.6.28 docutils==0.12 ecdsa==0.13 ethtool==0.6 feedparser==5.2.0 firstboot==1.110 freeipa==2.0.0a0 futures==2.2.0 glusterfs-api==3.6.0.28 iniparse==0.3.1 iotop==0.3.2 ipapython==3.0.0 iwlib==1.0 kerberos==1.1 lxml==2.2.3 M2Crypto==0.20.2 Magic-file-extensions==0.1 Mako==0.3.4 Markdown==2.4.1 MarkupSafe==0.9.2 matplotlib==0.99.1.1 mercurial==3.4 mimeparse==0.1.3 MySQL-python==1.2.5 netaddr==0.7.5 nose==0.10.4 numpy==1.4.1 p4python==2014.1.925900 paramiko==1.15.2 PIL==1.1.7 Pillow==2.8.1 pillowfight==0.2 policycoreutils-default-encoding==0.1 pycrypto==2.6.1 pycurl==7.19.0 Pygments==2.0.2 pygpgme==0.1 pyOpenSSL==0.10 python-dateutil==1.5 python-default-encoding==0.1 python-dmidecode==3.10.13 python-ldap==2.3.10 python-meh==0.11 python-memcached==1.54 python-nss==0.13 pytz===2010h pyxdg==0.18 recaptcha-client==1.0.6 ReviewBoard==2.0.15 rhnlib==2.5.22 rhsm==1.12.5 scdate==1.9.60 sckdump==2.0.5 scservices==0.99.45 scservices.dbus==0.99.45 setools==1.0 six==1.9.0 slip==0.2.20 slip.dbus==0.2.20 slip.gtk==0.2.20 smbc==1.0 SSSDConfig==1.11.6 suds==0.4.1 urlgrabber==3.9.1 virtinst==0.600.0 Whoosh==2.7.0 yum-metadata-parser==1.1.2 D/B setup exactly as the old node with the same d/b|user|pass etc. Method: # rb-site installpath Then going in and dropping the d/b and creating the empty d/b again (I've tried it without dropping the newly created one as well). Taking the latest dump.sql from the old server and loading it into the new d/b Taking the latest htdocs/media/uploaded content to the new server from old # rb-site upgrade path and getting these errors which I've seen mentioned around the web but unsure how to correct and unsure how to read the evolve --hint to fix: 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 ... There are unapplied evolutions for auth. There are unapplied evolutions for contenttypes. 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. Project signature has changed - an evolution is required Installing custom SQL ... Installing indexes ... Installed 0 object(s) from 0 fixture(s) 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 scmtools.Repository: Field 'hosting_account' has been added Field 'extra_data' has been added CommandError: Your models contain changes that Django Evolution cannot resolve automatically. # rb-site manage path list-evolutions Applied evolutions for 'sessions': session_expire_date_db_index Applied evolutions for 'accounts': is_private Applied evolutions for 'changedescs': fields_changed_longtext Applied evolutions for 'diffviewer': add_parent_diffs filediff_filenames_1024_chars diffset_basedir filediff_status Applied evolutions for 'reviews': change_descriptions last_review_timestamp shipit_count default_reviewer_repositories null_repository localsite group_incoming_request_count group_invite_only group_visible default_reviewer_local_site add_issues_to_comments file_attachments Applied evolutions for 'scmtools': bugzilla_url_charfield repository_raw_file_url repository_visible repository_path_length_255 localsite repository_access_control group_site repository_hosting_accounts repository_extra_data_null Thanks in advance for any pointers in this. - John -- 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
Re: After upgrading to ReviewBoard 2.0.15 the existing reviews do not display the diffs correctly
The URL for this one is https://vcs.ourdomain.com/svn/enrollment/trunk/4X.
That isn't the root per se, but we have multiple different repositories
under our svn so we point it directly at the folder we want as the root,
and then when we create the reviews we use / as the base path for the
review. The URL is the same as it was on Reviewboard 1.6.11 and it was
working there. Also, if I create a brand new review against this repo it
works fine. It's just when I try to navigate to reviews that existed before
the upgrade that the issue occurs.
On Wednesday, May 27, 2015 at 12:28:40 PM UTC-4, Papaswede wrote:
I upgraded ReviewBoard from 1.6.11 to 2.0.15. After doing this, I get
error messages when attempting to view the diffs of the existing reviews. I
get messages like:
The file
'('/svn/enrollment/!svn/bc/122232/trunk/4X/enrollment/trunk/trunk/4X/webapps/common/src/main/java/bf/web/common/form/AddEmployeeForm.java'
path not found, 160013)' could not be found in the repository
Where that path definitely is not a valid svn path. It should
be
/svn/enrollment/!svn/bc/122232/trunk/4X/webapps/common/src/main/java/bf/web/common/form/AddEmployeeForm.java.
So, it's like there's stuff being automatically inserted into the svn path
for the file, but I have no idea why as it was working on version 1.6.11.
Any help would be greatly appreciated.
--
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: After upgrading to ReviewBoard 2.0.15 the existing reviews do not display the diffs correctly
Here's a screenshot of the repository configuration:
https://lh3.googleusercontent.com/-XjVj3czBb1g/VWcSv6TMhPI/AL0/jCi0XFHd1kk/s1600/Change_repository___Administration___Review_Board.png
On Wednesday, May 27, 2015 at 12:28:40 PM UTC-4, Papaswede wrote:
I upgraded ReviewBoard from 1.6.11 to 2.0.15. After doing this, I get
error messages when attempting to view the diffs of the existing reviews. I
get messages like:
The file
'('/svn/enrollment/!svn/bc/122232/trunk/4X/enrollment/trunk/trunk/4X/webapps/common/src/main/java/bf/web/common/form/AddEmployeeForm.java'
path not found, 160013)' could not be found in the repository
Where that path definitely is not a valid svn path. It should
be
/svn/enrollment/!svn/bc/122232/trunk/4X/webapps/common/src/main/java/bf/web/common/form/AddEmployeeForm.java.
So, it's like there's stuff being automatically inserted into the svn path
for the file, but I have no idea why as it was working on version 1.6.11.
Any help would be greatly appreciated.
--
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.
Issue 3878 in reviewboard: command rbt status/post are hanging
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 3878 by akshayta...@gmail.com: command rbt status/post are hanging https://code.google.com/p/reviewboard/issues/detail?id=3878 *** READ THIS BEFORE POSTING! *** *** You must complete this form in its entirety, or your bug report will be *** rejected. *** *** If you have a security issue to report, please send it confidentially to *** secur...@reviewboard.org. Posting security-related issues to this bug *** tracker causes us to have to do an emergency release. *** *** For customer support, please post to reviewbo...@googlegroups.com *** *** If you have a patch, please submit it to http://reviews.reviewboard.org/ *** *** This bug tracker is public. Please check that any logs or other information *** that you include has been stripped of confidential information. What version are you running? RBTools 0.7 What's the URL of the page containing the problem? What steps will reproduce the problem? 1. I ran rbt status rbt post changenum these commands hang. What is the expected output? What do you see instead? The commands should finish successfully. I am getting below stuff. Its hung at the last line below rbt status --debug RBTools 0.7 Python 2.6.6 (r266:84292, Oct 12 2012, 14:23:48) [GCC 4.4.6 20120305 (Red Hat 4.4.6-4)] Running on Linux-2.6.32-358.el6.x86_64-x86_64-with-redhat-6.4-Santiago Home = /home/XXX Current directory = /local/home/XXX Checking for a Subversion repository... Running: svn info --non-interactive Command exited with rc 1: ['svn', 'info', '--non-interactive'] svn: '.' is not a working copy --- Checking for a Git repository... Running: git rev-parse --git-dir Command exited with rc 128: ['git', 'rev-parse', '--git-dir'] fatal: Not a git repository (or any of the parent directories): .git --- Checking for a Mercurial repository... Unable to execute hg --help: skipping Mercurial Checking for a CVS repository... Checking for a Perforce repository... Running: p4 info Running: diff --version repository info: Path: perforce-a.XXX.com:XXX, Base path: None, Supports changesets: True What operating system are you using? What browser? Red Hat Enterprise Linux Server release 6.4 (Santiago) Please provide any additional information below. -- 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.
Re: After upgrading to ReviewBoard 2.0.15 the existing reviews do not display the diffs correctly
Oh, and I just noticed that a few of the existing reviews still do work,
but about 90% of them do not. I was clicking through some at random and
found that some do show up correctly. I'm not sure what's wrong with the
ones that aren't showing up.
On Wednesday, May 27, 2015 at 12:28:40 PM UTC-4, Papaswede wrote:
I upgraded ReviewBoard from 1.6.11 to 2.0.15. After doing this, I get
error messages when attempting to view the diffs of the existing reviews. I
get messages like:
The file
'('/svn/enrollment/!svn/bc/122232/trunk/4X/enrollment/trunk/trunk/4X/webapps/common/src/main/java/bf/web/common/form/AddEmployeeForm.java'
path not found, 160013)' could not be found in the repository
Where that path definitely is not a valid svn path. It should
be
/svn/enrollment/!svn/bc/122232/trunk/4X/webapps/common/src/main/java/bf/web/common/form/AddEmployeeForm.java.
So, it's like there's stuff being automatically inserted into the svn path
for the file, but I have no idea why as it was working on version 1.6.11.
Any help would be greatly appreciated.
--
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.
Is it possible to integrate Sonar Qube Review tool with Review Board.
As part of Developers' self review, we are using Sonar Qube and Review Board for peer Review. Is there any way to integrate SonarQube with Review Board? -- 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.
