reviewboard upgrade : django.db.utils.DatabaseError: no such table: django_site
trying to upgrade reviewboard like : rb-site upgrade /home/naveen/env-review72/reviewboard got error like django.db.utils.DatabaseError: no such table: django_site How to run syncdb since there is no manage.py file in site directory? -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://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/groups/opt_out.
database error on site upgrade
On upgradin the site like :
rb-site upgrade /home/naveen/venv-review/reviewboard
got the following database error (using sqlite3) :
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 ...
Installing custom SQL ...
Installing indexes ...
Installed 0 object(s) from 0 fixture(s)
No evolution required.
--- end log output ---
Resetting in-database caches.
Traceback (most recent call last):
File /home/naveen/venv-review/bin/rb-site, line 9, in module
load_entry_point('ReviewBoard==1.7.21', 'console_scripts', 'rb-site')()
File
/home/naveen/venv-review/local/lib/python2.7/site-packages/ReviewBoard-1.7.21-py2.7.egg/reviewboard/cmdline/rbsite.py,
line 2027, in main
command.run()
File
/home/naveen/venv-review/local/lib/python2.7/site-packages/ReviewBoard-1.7.21-py2.7.egg/reviewboard/cmdline/rbsite.py,
line 1860, in run
site.run_manage_command(fixreviewcounts)
File
/home/naveen/venv-review/local/lib/python2.7/site-packages/ReviewBoard-1.7.21-py2.7.egg/reviewboard/cmdline/rbsite.py,
line 562, in run_manage_command
execute_manager(reviewboard.settings, [__file__, cmd] + params)
File
/home/naveen/venv-review/local/lib/python2.7/site-packages/Django-1.4.10-py2.7.egg/django/core/management/__init__.py,
line 459, in execute_manager
utility.execute()
File
/home/naveen/venv-review/local/lib/python2.7/site-packages/Django-1.4.10-py2.7.egg/django/core/management/__init__.py,
line 382, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File
/home/naveen/venv-review/local/lib/python2.7/site-packages/Django-1.4.10-py2.7.egg/django/core/management/base.py,
line 196, in run_from_argv
self.execute(*args, **options.__dict__)
File
/home/naveen/venv-review/local/lib/python2.7/site-packages/Django-1.4.10-py2.7.egg/django/core/management/base.py,
line 232, in execute
output = self.handle(*args, **options)
File
/home/naveen/venv-review/local/lib/python2.7/site-packages/Django-1.4.10-py2.7.egg/django/core/management/base.py,
line 371, in handle
return self.handle_noargs(**options)
File
/home/naveen/venv-review/local/lib/python2.7/site-packages/ReviewBoard-1.7.21-py2.7.egg/reviewboard/reviews/management/commands/fixreviewcounts.py,
line 16, in handle_noargs
starred_public_request_count=None)
File
/home/naveen/venv-review/local/lib/python2.7/site-packages/Django-1.4.10-py2.7.egg/django/db/models/manager.py,
line 185, in update
return self.get_query_set().update(*args, **kwargs)
File
/home/naveen/venv-review/local/lib/python2.7/site-packages/Django-1.4.10-py2.7.egg/django/db/models/query.py,
line 536, in update
rows = query.get_compiler(self.db).execute_sql(None)
File
/home/naveen/venv-review/local/lib/python2.7/site-packages/Django-1.4.10-py2.7.egg/django/db/models/sql/compiler.py,
line 988, in execute_sql
cursor = super(SQLUpdateCompiler, self).execute_sql(result_type)
File
/home/naveen/venv-review/local/lib/python2.7/site-packages/Django-1.4.10-py2.7.egg/django/db/models/sql/compiler.py,
line 818, in execute_sql
cursor.execute(sql, params)
File
/home/naveen/venv-review/local/lib/python2.7/site-packages/Django-1.4.10-py2.7.egg/django/db/backends/sqlite3/base.py,
line 344, in execute
return Database.Cursor.execute(self, query, params)
*django.db.utils.DatabaseError: attempt to write a readonly database*
the sqlite database file has been given access to server (www-data) like :
sudo chown www-data /home/naveen/venv-review/*reviewboard*
/data/reviewboard.db
Does www-data should have read/write access of site , *reviewboard*, if it
is the case ?
--
Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
---
Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
---
Happy user? Let us know at http://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/groups/opt_out.
RE: 1.7.21 + GitLab Feedback
One thing that caught my eye is that you mentioned Repository Name (without .git). Did you have to put .git in your repository name? My tests didn't require that. I didn’t use the .git. That comment was more for clarity since GitLab always has the ‘.gi’t on the end of the repo, and Review Board doesn’t like it when you put one in, since it adds it’s own ‘.git’. Thanks for the feedback. The design was modeled after GitHub's support, which was the initial service the current repository form code was built for. I know that it's not perfect, but it's consistent, and right now we're going to stay with it, as I want to minimize work being done in this area for now. This is fine. We may want to document the ‘hack-around’ for adding 3rd party individual contributor repos in the interim, as it was rather unituitive my first time. I ended up looking at the source code to figure out how to do it. Walt From: reviewboard@googlegroups.com [mailto:reviewboard@googlegroups.com] On Behalf Of Christian Hammond Sent: Monday, January 20, 2014 5:52 PM To: reviewboard@googlegroups.com Subject: Re: 1.7.21 + GitLab Feedback Hi, Glad it's working! Thanks for the feedback. The design was modeled after GitHub's support, which was the initial service the current repository form code was built for. I know that it's not perfect, but it's consistent, and right now we're going to stay with it, as I want to minimize work being done in this area for now. The plan after 2.0 ships is to completely redo repository configuration. You won't fill in these fields anymore. Instead, you'll authenticate with GitLab (or GitHub or Beanstalk or whatever) and it'll present you with all repositories associated with your account, and allow you to search and add other repositories. You'll be able to add as few or as many as you want in one go. No dealing with plans or a bunch of fields. Until that's done, I don't want to risk any big regressions in configuration, or deal with migration of hosting service account data (which there's currently no support for). Hope that makes sense, but I do appreciate your willingness to look into this! One thing that caught my eye is that you mentioned Repository Name (without .git). Did you have to put .git in your repository name? My tests didn't require that. Christian -- Christian Hammond - chip...@chipx86.commailto:chip...@chipx86.com Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On Mon, Jan 20, 2014 at 5:10 PM, Javins, Walt walt.jav...@isilon.commailto:walt.jav...@isilon.com wrote: First off, thanks so much for the native GitLab support Christian! I just upgraded our staging server to 1.7.21, and it certainly made GitLab set up a lot easier. One piece of feedback: If an admin wishes to set up RB for a repository not owned by the RB service user (the account that review board is using to access GitLab), it has to be done via the “Repository Plan: Group” option. E.g. if individual contributor ‘wjavins’ owns project ‘reviewbot’ , I’d set up review by putting ‘wjavins’ in the “GitLab group name:” field and ‘reviewbot’ in the “Repository Name” field. Given this somewhat unintuitive setup I propose the following changes to simplify Review Board + GitLab configuration: * Ditch the distinction between “Group” and “Personal” * Always require two fields for GitLab’s “Repository Information: subsection: 1) “Repository Owner:” 2) “Repository Name (without .git):” I believe this would simplify the process of setting up accounts by removing the choice between ‘group’ and ‘personal’ and unifying setup for 3 different scenarios: 1) accounts owned by the RB service account (just put the RB service account name in “Repository Owner:”) 2) those owned by other individuals 3) and those owned by a group If you like this idea, I could likely throw a patch together for it. I’m not yet familiar with django/RB’s testing architecture though, so I may need help there, if I need to add/update tests. Walt -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://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.commailto:reviewboard%2bunsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://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
Re: Review Bot: How to manually run cppcheck and pep 8?
This question came up again today from one of our users. Has anyone done a manual run of the cppcheck or pep8 bots from reviewboard? On Thursday, September 26, 2013 2:37:01 PM UTC-7, Steve wrote: I have the Review Bot extensions running and they're quick slick. On the configuration page, there's a check box for Allow run manually I have a review with a python file that doesn't have a .py extension and I'd like to manually run the pep 8 bot, but I can't figure out how to do it. I don't see any button, icon or text to trigger a manual run on the review page. How do I do that? Thanks! --Steve -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://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/groups/opt_out.
Re: database error on site upgrade
You really don't want to use SQLite. This is only intended for development,
and will not support a real user base of any size.
If you do use SQLite, the directory containing the database needs to be
writable by www-data.
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
Beanbag, Inc. - http://www.beanbaginc.com
On Tue, Jan 21, 2014 at 5:55 AM, nav...@launchyard.com wrote:
On upgradin the site like :
rb-site upgrade /home/naveen/venv-review/reviewboard
got the following database error (using sqlite3) :
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 ...
Installing custom SQL ...
Installing indexes ...
Installed 0 object(s) from 0 fixture(s)
No evolution required.
--- end log output ---
Resetting in-database caches.
Traceback (most recent call last):
File /home/naveen/venv-review/bin/rb-site, line 9, in module
load_entry_point('ReviewBoard==1.7.21', 'console_scripts', 'rb-site')()
File
/home/naveen/venv-review/local/lib/python2.7/site-packages/ReviewBoard-1.7.21-py2.7.egg/reviewboard/cmdline/rbsite.py,
line 2027, in main
command.run()
File
/home/naveen/venv-review/local/lib/python2.7/site-packages/ReviewBoard-1.7.21-py2.7.egg/reviewboard/cmdline/rbsite.py,
line 1860, in run
site.run_manage_command(fixreviewcounts)
File
/home/naveen/venv-review/local/lib/python2.7/site-packages/ReviewBoard-1.7.21-py2.7.egg/reviewboard/cmdline/rbsite.py,
line 562, in run_manage_command
execute_manager(reviewboard.settings, [__file__, cmd] + params)
File
/home/naveen/venv-review/local/lib/python2.7/site-packages/Django-1.4.10-py2.7.egg/django/core/management/__init__.py,
line 459, in execute_manager
utility.execute()
File
/home/naveen/venv-review/local/lib/python2.7/site-packages/Django-1.4.10-py2.7.egg/django/core/management/__init__.py,
line 382, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File
/home/naveen/venv-review/local/lib/python2.7/site-packages/Django-1.4.10-py2.7.egg/django/core/management/base.py,
line 196, in run_from_argv
self.execute(*args, **options.__dict__)
File
/home/naveen/venv-review/local/lib/python2.7/site-packages/Django-1.4.10-py2.7.egg/django/core/management/base.py,
line 232, in execute
output = self.handle(*args, **options)
File
/home/naveen/venv-review/local/lib/python2.7/site-packages/Django-1.4.10-py2.7.egg/django/core/management/base.py,
line 371, in handle
return self.handle_noargs(**options)
File
/home/naveen/venv-review/local/lib/python2.7/site-packages/ReviewBoard-1.7.21-py2.7.egg/reviewboard/reviews/management/commands/fixreviewcounts.py,
line 16, in handle_noargs
starred_public_request_count=None)
File
/home/naveen/venv-review/local/lib/python2.7/site-packages/Django-1.4.10-py2.7.egg/django/db/models/manager.py,
line 185, in update
return self.get_query_set().update(*args, **kwargs)
File
/home/naveen/venv-review/local/lib/python2.7/site-packages/Django-1.4.10-py2.7.egg/django/db/models/query.py,
line 536, in update
rows = query.get_compiler(self.db).execute_sql(None)
File
/home/naveen/venv-review/local/lib/python2.7/site-packages/Django-1.4.10-py2.7.egg/django/db/models/sql/compiler.py,
line 988, in execute_sql
cursor = super(SQLUpdateCompiler, self).execute_sql(result_type)
File
/home/naveen/venv-review/local/lib/python2.7/site-packages/Django-1.4.10-py2.7.egg/django/db/models/sql/compiler.py,
line 818, in execute_sql
cursor.execute(sql, params)
File
/home/naveen/venv-review/local/lib/python2.7/site-packages/Django-1.4.10-py2.7.egg/django/db/backends/sqlite3/base.py,
line 344, in execute
return Database.Cursor.execute(self, query, params)
*django.db.utils.DatabaseError: attempt to write a readonly database*
the sqlite database file has been given access to server (www-data) like :
sudo chown www-data /home/naveen/venv-review/*reviewboard*
/data/reviewboard.db
Does www-data should have read/write access of site , *reviewboard*, if
it is the case ?
--
Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
---
Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
---
Happy user? Let us know at http://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/groups/opt_out.
--
Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
---
Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
---
Happy user? Let us know at
Re: RBTools 0.5.4 questions
We're using the SVN property set at the root of the repository for the same reasons as Alexey. I can also confirm that this approach works perfectly fine even when I have only a subdirectory checked out. On Wednesday, January 15, 2014 12:38:21 AM UTC-5, Christian Hammond wrote: -- Christian Hammond - chi...@chipx86.com javascript: Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On Tue, Jan 14, 2014 at 7:47 PM, Alexey Neyman alexey...@gmail.comjavascript: wrote: Hi Chris, Thanks for a detailed response. One question on UUID - why can't it be cached in RB's database at the time of repository setup, instead of being queried from Subversion servers for each 'rbt post' as you described? On .reviewboardrc, this approach would work if the checked-out module is known. In our case, for example, we have at least: /trunk/src /trunk/docs (and a few other directories) - If a developer works purely on updating the user documentation, for example, he would just check out /trunk/docs. Which means for 'rbt post' to work, there needs to be /trunk/docs/.reviewboardrc. - Similarly, if a change does not involve anything but sources, he'd only check out /trunk/src - ergo, there must be /trunk/src/.reviewboardrc. - If a change involves both the source code modifications and user doc changes, he'd check out /trunk - so, adding /trunk/.reviewboardrc as well... I think you see where this is getting :) Putting a separate .reviewboardrc into each subdirectory is hardly maintainable, especially if we need to change it at some point. Now, imagine if we migrate the RB to a different server - in addition to updating multiple .reviewboardrc's for /trunk, we'd also need to update the .reviewboardrc in each branch - since many branches are still actively maintained. This is why we're using a property set at the top of the repository. I implore to add a repository name property to avoid the above maintenance nightmare. That makes sense, and is a valid use case for UUID matching. Caching is possible. It didn't used to be when the UUID code was written, but it's worth investigating now. I'll be honest, I don't have a lot of time to do that right now with trying to get RB 2.0 out the door, but a patch wouldn't be too difficult. I'd accept one for caching the UUID if someone wanted to write it. The problem would be if you changed the repository out from underneath Review Board, changing UUIDs. You'd need some way to reset. Maybe not worth optimizing for, but should be considered. Unfortunately, I don't believe the property isn't any more a solution than .reviewboardrc. For the current reviewboard:url property, we're just walking up the local directory stack anyway, meaning a property on / won't work if checking out from some subdirectory. You'd still need a property in every one of those directories, which is only slightly different than a .reviewboardrc in every one of those directories. (The latter at least allows for consistency with the rest of the codebase and other revision control systems.) If we were to fix that to check the property from the root of the remote server (provided / isn't checked out), then there's not much difference between that and grabbing the .reviewboardrc from the root of the remote server. I'll admit I may be missing something, as it's been a while since I've dealt with Subversion or our Subversion code on any real level. Christian -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://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/groups/opt_out.
reviewbot logging
How do I enable logging for the reviewbot tools, and where are the logs written? I'm particularly interested in the logging messages in tools/process.py. --Steve -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://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/groups/opt_out.
Bugs field and JIRA link
I know that JIRA and reviewboard do not talk to each other in a formal way, but I was wondering if you may consider to allow to define a JIRA weblink like : http://melp-jira01:8080/browse/MY-890 and associate such link to a string in the Bugs field. So far the only way that I can see to link the JIRA tickets and review board is by pasting the JIRA ticket link under description. -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://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/groups/opt_out.
Re: Bugs field and JIRA link
You can set a URL template per-repository and links will be automatically created: http://www.reviewboard.org/docs/manual/1.7/admin/configuration/repositories/#bug-tracker -David On Tue, Jan 21, 2014 at 3:24 PM, MoonWalker daniel.cabrera...@gmail.comwrote: I know that JIRA and reviewboard do not talk to each other in a formal way, but I was wondering if you may consider to allow to define a JIRA weblink like : http://melp-jira01:8080/browse/MY-890 and associate such link to a string in the Bugs field. So far the only way that I can see to link the JIRA tickets and review board is by pasting the JIRA ticket link under description. -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://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/groups/opt_out. -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://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/groups/opt_out.
Re: Bugs field and JIRA link
Hi MoonWalker, You can set the Bug Tracker field for the repository to http://melp-jira01:8080/browse/%s, and then any time you enter a bug ID in a review request, it'll generate a link replacing the %s with the bug ID. Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On Tue, Jan 21, 2014 at 3:24 PM, MoonWalker daniel.cabrera...@gmail.comwrote: I know that JIRA and reviewboard do not talk to each other in a formal way, but I was wondering if you may consider to allow to define a JIRA weblink like : http://melp-jira01:8080/browse/MY-890 and associate such link to a string in the Bugs field. So far the only way that I can see to link the JIRA tickets and review board is by pasting the JIRA ticket link under description. -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://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/groups/opt_out. -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://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/groups/opt_out.
Re: Bugs field and JIRA link
Thank you Christian it works super well :-) On Wednesday, January 22, 2014 10:55:00 AM UTC+11, Christian Hammond wrote: Hi MoonWalker, You can set the Bug Tracker field for the repository to http://melp-jira01:8080/browse/%s, and then any time you enter a bug ID in a review request, it'll generate a link replacing the %s with the bug ID. Christian -- Christian Hammond - chi...@chipx86.com javascript: Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On Tue, Jan 21, 2014 at 3:24 PM, MoonWalker daniel.c...@gmail.comjavascript: wrote: I know that JIRA and reviewboard do not talk to each other in a formal way, but I was wondering if you may consider to allow to define a JIRA weblink like : http://melp-jira01:8080/browse/MY-890 and associate such link to a string in the Bugs field. So far the only way that I can see to link the JIRA tickets and review board is by pasting the JIRA ticket link under description. -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://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...@googlegroups.com javascript:. For more options, visit https://groups.google.com/groups/opt_out. -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://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/groups/opt_out.
Incremental update required ?
I was wondering if incremental update is required or not? Lets say that I am using 1.7.21 and I do not want to update until 1.7.34 can I do that or shall update from 1.7.21 to 1.7.34 without risking any major issues. -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://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/groups/opt_out.
Re: Incremental update required ?
Theoretically, you can upgrade from 1.0 straight to 2.0. You won't need to keep up with every point release. We try hard to keep the upgrade path easy. That said, pay attention to rb-site upgrade's instructions, as we'll note if there's any manual work you need to do to complete an upgrade. Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On Tue, Jan 21, 2014 at 5:39 PM, MoonWalker daniel.cabrera...@gmail.comwrote: I was wondering if incremental update is required or not? Lets say that I am using 1.7.21 and I do not want to update until 1.7.34 can I do that or shall update from 1.7.21 to 1.7.34 without risking any major issues. -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://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/groups/opt_out. -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://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/groups/opt_out.
Re: Incremental update required ?
Nice! Thank you :-) On Wednesday, January 22, 2014 12:42:44 PM UTC+11, Christian Hammond wrote: Theoretically, you can upgrade from 1.0 straight to 2.0. You won't need to keep up with every point release. We try hard to keep the upgrade path easy. That said, pay attention to rb-site upgrade's instructions, as we'll note if there's any manual work you need to do to complete an upgrade. Christian -- Christian Hammond - chi...@chipx86.com javascript: Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On Tue, Jan 21, 2014 at 5:39 PM, MoonWalker daniel.c...@gmail.comjavascript: wrote: I was wondering if incremental update is required or not? Lets say that I am using 1.7.21 and I do not want to update until 1.7.34 can I do that or shall update from 1.7.21 to 1.7.34 without risking any major issues. -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://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...@googlegroups.com javascript:. For more options, visit https://groups.google.com/groups/opt_out. -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://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/groups/opt_out.
Re: Issue 2244 in reviewboard: API Request: Ability to determine if a review request is marked as ship it without having to iterate through reviews
Updates: Status: PendingReview Owner: chip...@gmail.com Labels: Milestone-Release2.0 Comment #2 on issue 2244 by chip...@gmail.com: API Request: Ability to determine if a review request is marked as ship it without having to iterate through reviews http://code.google.com/p/reviewboard/issues/detail?id=2244 Up for review at https://reviews.reviewboard.org/r/5284/ -- 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/groups/opt_out.
Re: Issue 2244 in reviewboard: API Request: Ability to determine if a review request is marked as ship it without having to iterate through reviews
Updates: Status: Fixed Comment #3 on issue 2244 by trowb...@gmail.com: API Request: Ability to determine if a review request is marked as ship it without having to iterate through reviews http://code.google.com/p/reviewboard/issues/detail?id=2244 (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/groups/opt_out.
Re: Issue 2179 in reviewboard: post-review hangs when using publish flag.
Updates: Status: Fixed Comment #2 on issue 2179 by trowb...@gmail.com: post-review hangs when using publish flag. http://code.google.com/p/reviewboard/issues/detail?id=2179 This is a quite old bug, and -p definitely works in both post-review and rbt post. -- 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/groups/opt_out.
Re: Issue 3075 in reviewboard: RBTools documentation should make clear that command line SVN client is a requirement for Windows
Updates: Status: Fixed Comment #2 on issue 3075 by trowb...@gmail.com: RBTools documentation should make clear that command line SVN client is a requirement for Windows http://code.google.com/p/reviewboard/issues/detail?id=3075 Fixed in rbtools master (416a728) -- 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/groups/opt_out.
Re: Issue 2792 in reviewboard: Error Uploading svn diff file with property changes or binary files
Comment #5 on issue 2792 by karl.mau...@gmx.de: Error Uploading svn diff file with property changes or binary files http://code.google.com/p/reviewboard/issues/detail?id=2792 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/groups/opt_out.
Re: Issue 2445 in reviewboard: Unable to 'View Diff' when using with RhodeCode for mercurial repositories
Comment #27 on issue 2445 by dotheb...@gmail.com: Unable to 'View Diff' when using with RhodeCode for mercurial repositories http://code.google.com/p/reviewboard/issues/detail?id=2445 Update: - 'Such revision does not exist for this repository' originated in me having a patch based on a first tested migration repo, which was recreated under the same name. - the rhodecode won't grant access to the /raw/ URLswith http-Auth-basic, but just web based cookie auth. - since I don't have access to the rhode code, plus the connection isn't fast enough anyways, I work with local clones which do polling. - while the URLs generated work well with rhode code work well in the browser (so if you use cookies everything is ok) it seems to break connection to traditional hg repositories. In general, is there a cheap way for reviewboard to keep its own clone of hg repositories in general? -- 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/groups/opt_out.
Re: Issue 3196 in reviewboard: Would be good to add support web links in the various field including the bugs field
Comment #2 on issue 3196 by jatt...@gmail.com: Would be good to add support web links in the various field including the bugs field http://code.google.com/p/reviewboard/issues/detail?id=3196 That worked great! Thanks for your help. -- 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/groups/opt_out.
Issue 3200 in reviewboard: Depends on field should use strikethrough for submitted dependencies.
Status: New Owner: Labels: Type-Defect Priority-Medium EasyFix Component-Reviews New issue 3200 by trowb...@gmail.com: Depends on field should use strikethrough for submitted dependencies. http://code.google.com/p/reviewboard/issues/detail?id=3200 The Depends on field is used to indicate when one change depends on another. It would be very useful if it could react when those dependencies are marked as submitted by setting a strikethrough on the text. That way, users don't have to click through to see whether or not the dependent change has been committed yet. -- 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/groups/opt_out.
Re: Issue 3073 in reviewboard: Updating review with rbt post obliterates Depends On field
Updates: Status: Fixed Comment #3 on issue 3073 by trowb...@gmail.com: Updating review with rbt post obliterates Depends On field http://code.google.com/p/reviewboard/issues/detail?id=3073 Fixed in master (b73b167). -- 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/groups/opt_out.
Re: Issue 3139 in reviewboard: Depends on field isn't shown in change descriptions
Updates: Status: Fixed Comment #2 on issue 3139 by trowb...@gmail.com: Depends on field isn't shown in change descriptions http://code.google.com/p/reviewboard/issues/detail?id=3139 Fixed in master (b73b167). -- 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/groups/opt_out.
Re: Issue 2723 in reviewboard: Show issue status in dashboard
Updates: Status: Fixed Comment #20 on issue 2723 by trowb...@gmail.com: Show issue status in dashboard http://code.google.com/p/reviewboard/issues/detail?id=2723 This is now done in master, and will ship in 2.0 beta 3 -- 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/groups/opt_out.
Re: Issue 2886 in reviewboard: Ship It ASCII art duplicates for successive Ship It's
Updates: Status: Fixed Comment #1 on issue 2886 by trowb...@gmail.com: Ship It ASCII art duplicates for successive Ship It's http://code.google.com/p/reviewboard/issues/detail?id=2886 I'm cleaning up the ship-it extension code to commit to rb-extension-pack. As part of that, I've fixed this bug. -- 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/groups/opt_out.
Re: Issue 2125 in reviewboard: Page elements overlap when review request summary is too long
Updates: Labels: EasyFix Comment #3 on issue 2125 by trowb...@gmail.com: Page elements overlap when review request summary is too long http://code.google.com/p/reviewboard/issues/detail?id=2125 (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/groups/opt_out.
Re: Issue 2157 in reviewboard: Inner diff in draft generate 404 error
Updates: Status: Fixed Comment #9 on issue 2157 by trowb...@gmail.com: Inner diff in draft generate 404 error http://code.google.com/p/reviewboard/issues/detail?id=2157 This is no longer an issue with the new interdiff selector. -- 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/groups/opt_out.
