Re: Formatting errors in description field
Okay, can that be fixed? I don't want to change our templates. Or can markdown be disabled? Am Freitag, 25. Juli 2014 23:51:20 UTC+2 schrieb David Trowbridge: OK, I believe that the problem is the indentation. Markdown treats indented text as a code block, and won't handle any markdown syntax in it. -David On Thu, Jul 24, 2014 at 11:15 PM, Philip Schiffer philip@sprylab.com javascript: wrote: Sorry for the late answer - I did not get any notification :/ Am Donnerstag, 17. Juli 2014 22:30:38 UTC+2 schrieb David Trowbridge: Can you show what the source markdown looks like? (Click the pencil and then copy/paste/redact) -David On Thu, Jul 17, 2014 at 2:34 AM, Philip Schiffer philip@sprylab.com wrote: Hello everyone, I have upgraded our reviewboard installation from 1.7.x to 2.0.3. Unfortunately we have some issues with the formatting of the description field. We are using the post-review tool in our scripts to post our reviews. Inside the description field we put the git commit log entries. As you can see in the attachment, there are problems displaying the links. I've searched the bug tracker but unfortunately I'm getting http 500 errors from google code for this issue: https://code.google.com/p/ reviewboard/issues/detail?id=3377 -- 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. For more options, visit https://groups.google.com/d/optout. -- 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/d/optout. -- 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/d/optout.
Re: Migrating Reviewboard from 1.5 to 2.0.4
Hi Christian, That worked :). I've updated django-evolution to 0.7.3 and can confirm the upgrade went smoothly. Thanks a lot for your help. Bogdan On Friday, July 25, 2014 10:27:34 PM UTC+3, Christian Hammond wrote: Hi Bogdan, Re-running the upgrade is guaranteed to fail, because the database is in an inconsistent state. The problem isn’t so much an upgrade from 1.5.x to 2.0.x.. Rather, it’s anything 2.0 to 2.0.4. Fortunately, I found the cause, and have put out a django-evolution 0.7.3 release. You should be able to upgrade that: sudo easy_install -U django_evolution And then restore your database dump and re-upgrade. It should work. (Please let me know either way.) We’ll be putting out a 2.0.5 shortly that requires this version. Christian -- Christian Hammond - chri...@beanbaginc.com javascript: Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On July 25, 2014 at 2:06:23 AM, Bogdan Berezovyi (bod...@gmail.com javascript:) wrote: Hi Christian, Yes I have a backup, I'm playing with it on dev server, so can reimport at any time. I've also tried upgrading from 1.5.3 to 1.6.22 frist (as an intermidiary step) - this went smoothly Next upgrading from 1.6.22 to 2.0.4 gives me the same error first, but I'm able to rerun upgrade (no traceback) and then it gives the other error: 1. Error applying evolution: (1051, Unknown table 'auth_message') solution: Recreate table 2. CommandError: Error applying evolution: (1060, Duplicate column name 'permissions') solution: alter table accounts_localsiteprofile drop column permissions; 3. CommandError: Error applying evolution: (1060, Duplicate column name 'timezone') ... Should I follow the rabbit hole or just redump my database? Thanks, Bogdan On Thursday, July 24, 2014 10:43:49 PM UTC+3, Christian Hammond wrote: Hi, Do you have a backup of your 1.5.3 database? You’ll need one at this point, since the new database is in an inconsistent state. Christian -- Christian Hammond - chri...@beanbaginc.com Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On July 24, 2014 at 11:48:49 AM, Bogdan Berezovyi (bod...@gmail.com) wrote: Hi, I'm having trouble upgrading existing reviewboard 1.5.3 to the new release 2.0.4. After importing mysql dump and running rb-site upgrade I get the following error: CommandError: Error applying evolution: (1061, Duplicate key name 'scmtools_repository_97c59b73') I tried removing index as per one of earlier thread with similar error by running drop index scmtools_repository_97c59b73 on scmtools_repository; But this didn't help. If I rerun upgrade it crashes with traceback. Any help would be much appreciated. Bogdan -- 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. For more options, visit https://groups.google.com/d/optout. -- 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/d/optout. -- 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/d/optout.
Re: Can't upload diff for clearcase in 2.0.4
Thanks. I will post the questions there.
On Friday, July 25, 2014 5:40:10 PM UTC-4, Christian Hammond wrote:
Hi,
You’re going to need to go through Bitnami support for this. This looks
specific to their install.
Christian
--
Christian Hammond - chri...@beanbaginc.com javascript:
Review Board - http://www.reviewboard.org
Beanbag, Inc. - http://www.beanbaginc.com
On July 25, 2014 at 1:15:18 PM, liuzy163 (zhiyong...@gmail.com
javascript:) wrote:
I installed Reviewboard 2.0.4 on Windows by using the Bitnami installer
and configured it for Clearcase dynamic view. I set the repository path to
the top of the view then ran rbt post --server=http:/localhost/reviewboard
--user=xxx --password=xxx -o --summary=test --debug from my view
directory. I could see rbt was able to generate the diff but it failed to
post it. Here below I pasted the error stacks from both the console and the
log file.
Any help or hint will be highly appreciated.
*Console Error*
Making HTTP GET request to
http://localhost/reviewboard/api/review-requests/
Making HTTP POST request to
http://localhost/reviewboard/api/review-requests/
Making HTTP GET request to
http://localhost/reviewboard/api/review-requests/1/diffs/
Making HTTP POST request to
http://localhost/reviewboard/api/review-requests/1/diffs/
Got HTTP error: 500: !DOCTYPE html
html
head
title500 - Internal Server Error | Review Board/title
/head
body
h1Something broke! (Error 500)/h1
p
It appears something broke when you tried to go to here. This is either
a bug in Review Board or a server configuration error. Please report
this to your administrator.
/p
/body
/title
Traceback (most recent call last):
File d:\reviewboard-2.0.4-0\python\Scripts\rbt-script.py, line 8, in
module
load_entry_point('rbtools==0.6.2', 'console_scripts', 'rbt')()
File
D:\reviewboard-2.0.4-0\python\lib\site-packages\rbtools-0.6.2-py2.7.egg\rbtools\commands\main.py,
line 134, in main
command.run_from_argv([RB_MAIN, command_name] + args)
File
D:\reviewboard-2.0.4-0\python\lib\site-packages\rbtools-0.6.2-py2.7.egg\rbtools\commands\__init__.py,
line 416, in run_from_argv
exit_code = self.main(*args) or 0
File
D:\reviewboard-2.0.4-0\python\lib\site-packages\rbtools-0.6.2-py2.7.egg\rbtools\commands\post.py,
line 784, in main
submit_as=self.options.submit_as)
File
D:\reviewboard-2.0.4-0\python\lib\site-packages\rbtools-0.6.2-py2.7.egg\rbtools\commands\post.py,
line 551, in post_request
raise CommandError(u'\n'.join(error_msg))
rbtools.commands.CommandError: Error uploading diff
HTTP 500
Your review request still exists, but the diff is not attached.
*Error stack from reviewboard.log*
2014-07-25 15:25:16,834 - ERROR - - Exception thrown for user liuz6163
at http://localhost/reviewboard/api/review-requests/1/diffs/
[Error 267] The directory name is invalid
Traceback (most recent call last):
File D:\reviewboard-2.0.4-0\apps\django\django\core\handlers\base.py,
line 112, in get_response
response = wrapped_callback(request, *callback_args, **callback_kwargs)
File
D:\reviewboard-2.0.4-0\apps\django\django\views\decorators\cache.py, line
52, in _wrapped_view_func
response = view_func(request, *args, **kwargs)
File
D:\reviewboard-2.0.4-0\apps\django\django\views\decorators\vary.py, line
19, in inner_func
response = func(*args, **kwargs)
File
D:\reviewboard-2.0.4-0\python\lib\site-packages\djblets-0.8.7-py2.7.egg\djblets\webapi\resources.py,
line 494, in __call__
request, method, view, api_format=api_format, *args, **kwargs)
File
D:\reviewboard-2.0.4-0\python\lib\site-packages\djblets-0.8.7-py2.7.egg\djblets\webapi\resources.py,
line 565, in call_method_view
return view(request, *args, **kwargs)
File
D:\reviewboard-2.0.4-0\python\lib\site-packages\djblets-0.8.7-py2.7.egg\djblets\webapi\resources.py,
line 747, in post
return self.create(*args, **kwargs)
File
D:\reviewboard-2.0.4-0\python\lib\site-packages\djblets-0.8.7-py2.7.egg\djblets\webapi\decorators.py,
line 117, in _call
return view_func(*args, **kwargs)
File
D:\reviewboard-2.0.4-0\python\lib\site-packages\djblets-0.8.7-py2.7.egg\djblets\webapi\decorators.py,
line 138, in _checklogin
return view_func(*args, **kwargs)
File
D:\reviewboard-2.0.4-0\python\lib\site-packages\djblets-0.8.7-py2.7.egg\djblets\webapi\decorators.py,
line 117, in _call
return view_func(*args, **kwargs)
File
D:\reviewboard-2.0.4-0\apps\reviewboard\Lib\site-packages\ReviewBoard-2.0.4-py2.7.egg\reviewboard\webapi\decorators.py,
line 110, in _check
return view_func(*args, **kwargs)
File
D:\reviewboard-2.0.4-0\python\lib\site-packages\djblets-0.8.7-py2.7.egg\djblets\webapi\decorators.py,
line 117, in _call
return view_func(*args, **kwargs)
File
Re: Formatting errors in description field
How are you putting the git log into the description? By hand? With the JSON API? Using arguments to post-review? -David On Mon, Jul 28, 2014 at 1:54 AM, Philip Schiffer philip.schif...@sprylab.com wrote: Okay, can that be fixed? I don't want to change our templates. Or can markdown be disabled? Am Freitag, 25. Juli 2014 23:51:20 UTC+2 schrieb David Trowbridge: OK, I believe that the problem is the indentation. Markdown treats indented text as a code block, and won't handle any markdown syntax in it. -David On Thu, Jul 24, 2014 at 11:15 PM, Philip Schiffer philip@sprylab.com wrote: Sorry for the late answer - I did not get any notification :/ Am Donnerstag, 17. Juli 2014 22:30:38 UTC+2 schrieb David Trowbridge: Can you show what the source markdown looks like? (Click the pencil and then copy/paste/redact) -David On Thu, Jul 17, 2014 at 2:34 AM, Philip Schiffer philip@sprylab.com wrote: Hello everyone, I have upgraded our reviewboard installation from 1.7.x to 2.0.3. Unfortunately we have some issues with the formatting of the description field. We are using the post-review tool in our scripts to post our reviews. Inside the description field we put the git commit log entries. As you can see in the attachment, there are problems displaying the links. I've searched the bug tracker but unfortunately I'm getting http 500 errors from google code for this issue: https://code.google.com/p/revi ewboard/issues/detail?id=3377 -- Get the Review Board Power Pack at http://www.reviewboard.org/pow erpack/ --- 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. For more options, visit https://groups.google.com/d/optout. -- 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. For more options, visit https://groups.google.com/d/optout. -- 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/d/optout. -- 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/d/optout.
Re: Formatting errors in description field
We are all creating our review with this git alias: prd = !sh -c 'git fetch origin git push origin -u $(git name-rev --name-only HEAD) post-review -d --guess-summary --description=\$(git log origin/develop...HEAD)\ --branch=$(git name-rev --name-only HEAD) --tracking-branch=origin/develop --target-groups=$(git config reviewboard.group) --repository-url=$(git config reviewboard.repository) --server=$(git config reviewboard.url) --open' Am Montag, 28. Juli 2014 22:10:30 UTC+2 schrieb David Trowbridge: How are you putting the git log into the description? By hand? With the JSON API? Using arguments to post-review? -David On Mon, Jul 28, 2014 at 1:54 AM, Philip Schiffer philip@sprylab.com javascript: wrote: Okay, can that be fixed? I don't want to change our templates. Or can markdown be disabled? Am Freitag, 25. Juli 2014 23:51:20 UTC+2 schrieb David Trowbridge: OK, I believe that the problem is the indentation. Markdown treats indented text as a code block, and won't handle any markdown syntax in it. -David On Thu, Jul 24, 2014 at 11:15 PM, Philip Schiffer philip@sprylab.com wrote: Sorry for the late answer - I did not get any notification :/ Am Donnerstag, 17. Juli 2014 22:30:38 UTC+2 schrieb David Trowbridge: Can you show what the source markdown looks like? (Click the pencil and then copy/paste/redact) -David On Thu, Jul 17, 2014 at 2:34 AM, Philip Schiffer philip@sprylab.com wrote: Hello everyone, I have upgraded our reviewboard installation from 1.7.x to 2.0.3. Unfortunately we have some issues with the formatting of the description field. We are using the post-review tool in our scripts to post our reviews. Inside the description field we put the git commit log entries. As you can see in the attachment, there are problems displaying the links. I've searched the bug tracker but unfortunately I'm getting http 500 errors from google code for this issue: https://code.google.com/p/ reviewboard/issues/detail?id=3377 -- Get the Review Board Power Pack at http://www.reviewboard.org/pow erpack/ --- 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. For more options, visit https://groups.google.com/d/optout. -- 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. For more options, visit https://groups.google.com/d/optout. -- 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/d/optout. -- 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/d/optout.
Re: Formatting errors in description field
I believe that things should be fixed just by upgrading your version of rbtools and swapping out 'post-review' for 'rbt post'. -David On Mon, Jul 28, 2014 at 1:22 PM, Philip Schiffer philip.schif...@sprylab.com wrote: We are all creating our review with this git alias: prd = !sh -c 'git fetch origin git push origin -u $(git name-rev --name-only HEAD) post-review -d --guess-summary --description=\$(git log origin/develop...HEAD)\ --branch=$(git name-rev --name-only HEAD) --tracking-branch=origin/develop --target-groups=$(git config reviewboard.group) --repository-url=$(git config reviewboard.repository) --server=$(git config reviewboard.url) --open' Am Montag, 28. Juli 2014 22:10:30 UTC+2 schrieb David Trowbridge: How are you putting the git log into the description? By hand? With the JSON API? Using arguments to post-review? -David On Mon, Jul 28, 2014 at 1:54 AM, Philip Schiffer philip@sprylab.com wrote: Okay, can that be fixed? I don't want to change our templates. Or can markdown be disabled? Am Freitag, 25. Juli 2014 23:51:20 UTC+2 schrieb David Trowbridge: OK, I believe that the problem is the indentation. Markdown treats indented text as a code block, and won't handle any markdown syntax in it. -David On Thu, Jul 24, 2014 at 11:15 PM, Philip Schiffer philip@sprylab.com wrote: Sorry for the late answer - I did not get any notification :/ Am Donnerstag, 17. Juli 2014 22:30:38 UTC+2 schrieb David Trowbridge: Can you show what the source markdown looks like? (Click the pencil and then copy/paste/redact) -David On Thu, Jul 17, 2014 at 2:34 AM, Philip Schiffer philip@sprylab.com wrote: Hello everyone, I have upgraded our reviewboard installation from 1.7.x to 2.0.3. Unfortunately we have some issues with the formatting of the description field. We are using the post-review tool in our scripts to post our reviews. Inside the description field we put the git commit log entries. As you can see in the attachment, there are problems displaying the links. I've searched the bug tracker but unfortunately I'm getting http 500 errors from google code for this issue: https://code.google.com/p/ reviewboard/issues/detail?id=3377 -- Get the Review Board Power Pack at http://www.reviewboard.org/pow erpack/ --- 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. For more options, visit https://groups.google.com/d/optout. -- Get the Review Board Power Pack at http://www.reviewboard.org/pow erpack/ --- 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. For more options, visit https://groups.google.com/d/optout. -- 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. For more options, visit https://groups.google.com/d/optout. -- 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/d/optout. -- 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/d/optout.
request.user.is_authenticated() 'int' object is not subscriptable
Hey, I'm not sure if this is our set up or not but we seem to be getting a lot of Traceback (most recent call last): File /usr/local/lib/python2.7/site-packages/Django-1.6.5-py2.7.egg/django/core/handlers/base.py, line 88, in get_response response = middleware_method(request) File /usr/local/lib/python2.7/site-packages/ReviewBoard-2.0.3-py2.7.egg/reviewboard/accounts/middleware.py, line 12, in process_request if request.user.is_authenticated(): File /usr/local/lib/python2.7/site-packages/Django-1.6.5-py2.7.egg/django/utils/functional.py, line 213, in inner self._setup() File /usr/local/lib/python2.7/site-packages/Django-1.6.5-py2.7.egg/django/utils/functional.py, line 298, in _setup self._wrapped = self._setupfunc() File /usr/local/lib/python2.7/site-packages/Django-1.6.5-py2.7.egg/django/contrib/auth/middleware.py, line 18, in lambda request.user = SimpleLazyObject(lambda: get_user(request)) File /usr/local/lib/python2.7/site-packages/Django-1.6.5-py2.7.egg/django/contrib/auth/middleware.py, line 10, in get_user request._cached_user = auth.get_user(request) File */usr/local/lib/python2.7/site-packages/Django-1.6.5-py2.7.egg/django/contrib/auth/*__init__.py, line 140, in get_user user_id = request.session[SESSION_KEY] File /usr/local/lib/python2.7/site-packages/Django-1.6.5-py2.7.egg/django/contrib/sessions/backends/base.py, line 47, in __getitem__ return self._session[key] TypeError: 'int' object is not subscriptable This seems like it's a core django issue but i've never seen this before. This is on python2.7 (obviously from the above) on centos 5. Has anyone else run into this? I was about to file a bug but this seem so related to django that I feel weird without some confirmation... Thanks! -- 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/d/optout.
Issue 3502 in reviewboard: Separate Security Groups
Status: New Owner: Labels: Type-Enhancement Priority-Medium New issue 3502 by jon.bark...@gmail.com: Separate Security Groups http://code.google.com/p/reviewboard/issues/detail?id=3502 What version are you running? 2.0.3 What's the URL of the page this enhancement relates to, if any? admin/db/reviews/group/ Describe the enhancement and the motivation for it. Users can remove themselves from review groups that provide their access to view certain repositories. For some reason, they keep doing this, so really, I would like to have security groups that are not review groups. This way users can't opt out accidentally, and also so they don't send reviews to security groups when it is not appropriate. What operating system are you using? What browser? Not really relevant, but Mac, Firefox Please provide any additional information below. As part of this feature, it would also be great if the rest api could get updated so that repositories can be created as non public, with specific groups/people having access. As it is right now, I can't script creating new repos because they wouldn't have the correct permissions. -- 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: Issue 3340 in reviewboard: loaddp failing with FK error
Updates: Status: SetupIssue Comment #1 on issue 3340 by trowb...@gmail.com: loaddp failing with FK error http://code.google.com/p/reviewboard/issues/detail?id=3340 I believe this is caused when trying to run loaddb using a different version from the server where you dumped. You'll have to install the same version on the new server, load the db, and then upgrade there. -- 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: Issue 3486 in reviewboard: Upgrade 2.0 to 2.0.3 fails
Comment #5 on issue 3486 by abhishek.mukher.g: Upgrade 2.0 to 2.0.3 fails http://code.google.com/p/reviewboard/issues/detail?id=3486 This, from the sounds of it, might have been fixed by 2.0.5? The release notes suggest django-evolutions changes. not sure if that encompasses this or not. -- 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: Issue 3486 in reviewboard: Upgrade 2.0 to 2.0.3 fails
Updates: Status: Fixed Comment #6 on issue 3486 by trowb...@gmail.com: Upgrade 2.0 to 2.0.3 fails http://code.google.com/p/reviewboard/issues/detail?id=3486 Yes, this should be fixed by 2.0.5 -- 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.
