Re: CVS 1.12 on ReviewBoard
Understood. Here is the output of 'cvs -f -d cvsroot version' with an invalid repository path: $ cvs -f -d username@cvshost:/invalid/path version; echo $? Client: Concurrent Versions System (CVS) 1.12.13 (client/server) Server: Cannot access /invalid/path/CVSROOT No such file or directory 1 And the output using a valid repository path: $ cvs -f -d username@cvshost:/opt/cvs/root version; echo $? Client: Concurrent Versions System (CVS) 1.12.13 (client/server) Server: Concurrent Versions System (CVS) 1.11.22 (client/server) 0 As you might have guessed I substituted the username and host, but the output is the actual output from that command. Here's the output using a valid CVSROOT with the rls command: $ cvs -f -d username@cvshost:/opt/cvs/root rls; echo $? cvs [rls aborted]: server does not support rls 1 On Wednesday, May 14, 2014 3:24:12 PM UTC-6, David Trowbridge wrote: Actually, one question, too. Does 'cvs -f -d cvsroot version' actually check that the cvsroot is valid, or does it just check that the local cvs binary runs? The goal of this method is to verify the remote repository. -David On Wed, May 14, 2014 at 2:05 PM, Jason Woodrich jwoo...@gmail.comjavascript: wrote: Greetings, I'm had a problem with adding a CVS repository running on CVS 1.11. I'm accessing it using ssh with a key and my CVSROOT is valid. When I click Save on the Add Repository page it returns the message A repository was not found at the specified path. This is on CentOS 6 with both ReviewBoard 1.7.25 and 2.0rc3. I found that ReviewBoard is attempting to execute the rls cvs command, which isn't valid until CVS 1.12, which is the 'feature' build. The current stable build is 1.11.23 (according to http://ftp.gnu.org/non-gnu/cvs/source/stable/). Anyone attempting to add a CVS server running anything lower than 1.12 is going to fail. I suspect that even if the server was 1.12 the operation would still fail if the client is anything less than 1.12. I found the problem in /usr/lib/python2.6/site-packages/ReviewBoard-2.0rc3-py2.6.egg/reviewboard/scmtools/cvs.py: 331 def check_repository(self): 332 p = SCMTool.popen(['cvs', '-f', '-d', self.cvsroot, ' *rls*'], 333 self.local_site_name) 334 errmsg = six.text_type(p.stderr.read()) 335 if p.wait() != 0: 336 raise SCMError(errmsg) I was able to resolve the issue by substituting 'rls' for 'version' on line 332. Since ReviewBoard is just checking for the return code from CVS it should function the same. 331 def check_repository(self): 332 p = SCMTool.popen(['cvs', '-f', '-d', self.cvsroot, ' *version*'], 333 self.local_site_name) 334 errmsg = six.text_type(p.stderr.read()) 335 if p.wait() != 0: 336 raise SCMError(errmsg) I then did a recompile (python -m compileall .) from the reviewboard/scmtools directory and restarted Apache. Problem solved. Thought you might want to know. Your documentation indicates that on RHEL/CentOS you can install CVS using yum install cvs. The version included with CentOS 6 is 1.11.23 and will not work without these modifications. Thanks, Jason -- 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.
please advise if reviewboard it recommended for production use with ClearCase.
Hi it seems that ClearCase module little bit outdated and not maintained, can you please advise if you can recommend use it in production environment thanks in advance Ilya -- 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: CVS 1.12 on ReviewBoard
Thanks for the info. We'll get this fixed for the next releases. -David On Thu, May 15, 2014 at 9:03 AM, Jason Woodrich jwoodr...@gmail.com wrote: Understood. Here is the output of 'cvs -f -d cvsroot version' with an invalid repository path: $ cvs -f -d username@cvshost:/invalid/path version; echo $? Client: Concurrent Versions System (CVS) 1.12.13 (client/server) Server: Cannot access /invalid/path/CVSROOT No such file or directory 1 And the output using a valid repository path: $ cvs -f -d username@cvshost:/opt/cvs/root version; echo $? Client: Concurrent Versions System (CVS) 1.12.13 (client/server) Server: Concurrent Versions System (CVS) 1.11.22 (client/server) 0 As you might have guessed I substituted the username and host, but the output is the actual output from that command. Here's the output using a valid CVSROOT with the rls command: $ cvs -f -d username@cvshost:/opt/cvs/root rls; echo $? cvs [rls aborted]: server does not support rls 1 On Wednesday, May 14, 2014 3:24:12 PM UTC-6, David Trowbridge wrote: Actually, one question, too. Does 'cvs -f -d cvsroot version' actually check that the cvsroot is valid, or does it just check that the local cvs binary runs? The goal of this method is to verify the remote repository. -David On Wed, May 14, 2014 at 2:05 PM, Jason Woodrich jwoo...@gmail.comwrote: Greetings, I'm had a problem with adding a CVS repository running on CVS 1.11. I'm accessing it using ssh with a key and my CVSROOT is valid. When I click Save on the Add Repository page it returns the message A repository was not found at the specified path. This is on CentOS 6 with both ReviewBoard 1.7.25 and 2.0rc3. I found that ReviewBoard is attempting to execute the rls cvs command, which isn't valid until CVS 1.12, which is the 'feature' build. The current stable build is 1.11.23 (according to http://ftp.gnu.org/non-gnu/cvs/source/stable/). Anyone attempting to add a CVS server running anything lower than 1.12 is going to fail. I suspect that even if the server was 1.12 the operation would still fail if the client is anything less than 1.12. I found the problem in /usr/lib/python2.6/site- packages/ReviewBoard-2.0rc3-py2.6.egg/reviewboard/scmtools/cvs.py: 331 def check_repository(self): 332 p = SCMTool.popen(['cvs', '-f', '-d', self.cvsroot, ' *rls*'], 333 self.local_site_name) 334 errmsg = six.text_type(p.stderr.read()) 335 if p.wait() != 0: 336 raise SCMError(errmsg) I was able to resolve the issue by substituting 'rls' for 'version' on line 332. Since ReviewBoard is just checking for the return code from CVS it should function the same. 331 def check_repository(self): 332 p = SCMTool.popen(['cvs', '-f', '-d', self.cvsroot, ' *version*'], 333 self.local_site_name) 334 errmsg = six.text_type(p.stderr.read()) 335 if p.wait() != 0: 336 raise SCMError(errmsg) I then did a recompile (python -m compileall .) from the reviewboard/scmtools directory and restarted Apache. Problem solved. Thought you might want to know. Your documentation indicates that on RHEL/CentOS you can install CVS using yum install cvs. The version included with CentOS 6 is 1.11.23 and will not work without these modifications. Thanks, Jason -- 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.
Issue 3343 in reviewboard: Unable to add CVS repository with version below 1.12
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 3343 by jwoodr...@gmail.com: Unable to add CVS repository with version below 1.12 http://code.google.com/p/reviewboard/issues/detail?id=3343 *** READ THIS BEFORE POSTING! *** *** You must complete this form in its entirety, or your bug report will be rejected. *** *** For customer support, please post to reviewbo...@googlegroups.com *** *** If you have a patch, please submit it to http://reviews.reviewboard.org/ *** *** Do not post confidential information in this bug report! What version are you running? 1.7.25, also tried 2.0rc3 What's the URL of the page containing the problem? /admin/db/scmtools/repository/add/ What steps will reproduce the problem? 1. Environmental configuration: CVS 1.11.23 server, CVS 1.11.23 or 1.12 client on RB server, RB components for CVS access present on server, RB SSH pub key in ~/.ssh/authorized_hosts on CVS server for a user with access to CVS 2. Access admin - manage repositories - add repository 3. Enter any name for the repository, select CVS for the repository type, enter a valid CVSROOT for the repository path and the username of the user with access to CVS in the username field, click Save. What is the expected output? What do you see instead? Expecting to see that the repository is added successfully. Instead, it reports A repository was not found at the specified path. What operating system are you using? What browser? RB Server is CentOS 6 Client OS is Windows 7 with Chrome 34.0.1847.131 m Please provide any additional information below. I found that ReviewBoard is attempting to execute the rls cvs command, which isn't valid until CVS 1.12, which is the 'feature' build. The current stable build is 1.11.23 (according to http://ftp.gnu.org/non-gnu/cvs/source/stable/). Anyone attempting to add a CVS server running anything lower than 1.12 is going to fail. I suspect that even if the server was 1.12 the operation would still fail if the client is anything less than 1.12. I found the problem in /usr/lib/python2.6/site-packages/ReviewBoard-2.0rc3-py2.6.egg/reviewboard/scmtools/cvs.py: 331 def check_repository(self): 332 p = SCMTool.popen(['cvs', '-f', '-d', self.cvsroot, 'rls'], 333 self.local_site_name) 334 errmsg = six.text_type(p.stderr.read()) 335 if p.wait() != 0: 336 raise SCMError(errmsg) I was able to resolve the issue by substituting 'rls' for 'version' on line 332. Since ReviewBoard is just checking for the return code from CVS it should function the same. 331 def check_repository(self): 332 p = SCMTool.popen(['cvs', '-f', '-d', self.cvsroot, 'version'], 333 self.local_site_name) 334 errmsg = six.text_type(p.stderr.read()) 335 if p.wait() != 0: 336 raise SCMError(errmsg) I then did a recompile (python -m compileall .) from the reviewboard/scmtools directory and restarted Apache. It now works. Your documentation indicates that on RHEL/CentOS you can install CVS using yum install cvs. The version included with CentOS 6 is 1.11.23 and will not work without these modifications. -- 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.
Issue 3344 in reviewboard: Modification details not shown for copied files in post-commit SVN reviews
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 3344 by dancec...@gmail.com: Modification details not shown for copied files in post-commit SVN reviews http://code.google.com/p/reviewboard/issues/detail?id=3344 What version are you running? * Review Board 1.7.24 * RBTools 0.6 What's the URL of the page containing the problem? .../diff/ What steps will reproduce the problem? 1. Check out an SVN sandbox 2. Rename a file and change one line in it 3. Check in the changes 4. Run rbt post --svn-show-copies-as-adds n revision-number to create a post-commit review 5. Check the diff in Review Board What is the expected output? What do you see instead? Expected to see the one line change highlighted clearly. Instead, the Review Board diff shows up as if the whole file was added as new. What operating system are you using? What browser? Windows 7, Chrome Please provide any additional information below. Pre-commit diffs for copied SVN files seem to work fine (see issue 1065), but for post-commit, the --svn-show-copies-as-adds seems to have no effect. -- 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.
Issue 3345 in reviewboard: Password reset 500 fail
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 3345 by ipe...@gmail.com: Password reset 500 fail
http://code.google.com/p/reviewboard/issues/detail?id=3345
*** READ THIS BEFORE POSTING!
***
*** You must complete this form in its entirety, or your bug report will be
rejected.
***
*** For customer support, please post to reviewbo...@googlegroups.com
***
*** If you have a patch, please submit it to
http://reviews.reviewboard.org/
***
*** Do not post confidential information in this bug report!
What version are you running?
Reviewboard 2.0 RC3, ugpraded from RC2.
What's the URL of the page containing the problem?
account/reset/MQ-3rm-b5e15bbd57f784bc0a0a/
What steps will reproduce the problem?
1. Request a password reset with a valid email.
2. Click on the link from the received email.
What is the expected output? What do you see instead?
Instead of the password reset form, a 500 is presented. I turned on
debugging on RB and received the traceback below.
What operating system are you using? What browser?
RB RC3 is running on Ubuntu Server 12.04. Issue is the same regardless of
browser version tested.
Please provide any additional information below.
Environment:
Server traceback:
Request Method: GET
Request URL:
http://reviews.example.com/account/reset/MQ-3rm-b5e15bbd57f784bc0a0a/
Django Version: 1.6.4
Python Version: 2.7.6
Installed Applications:
[u'django.contrib.admin',
u'django.contrib.auth',
u'django.contrib.contenttypes',
u'django.contrib.sites',
u'django.contrib.sessions',
u'django.contrib.staticfiles',
u'djblets',
u'djblets.configforms',
u'djblets.datagrid',
u'djblets.extensions',
u'djblets.feedview',
u'djblets.gravatars',
u'djblets.log',
u'djblets.pipeline',
u'djblets.siteconfig',
u'djblets.util',
u'djblets.webapi',
u'haystack',
u'pipeline',
u'reviewboard',
u'reviewboard.accounts',
u'reviewboard.admin',
u'reviewboard.attachments',
u'reviewboard.changedescs',
u'reviewboard.datagrids',
u'reviewboard.diffviewer',
u'reviewboard.extensions',
u'reviewboard.hostingsvcs',
u'reviewboard.notifications',
u'reviewboard.reviews',
u'reviewboard.reviews.ui',
u'reviewboard.scmtools',
u'reviewboard.site',
u'reviewboard.ssh',
u'reviewboard.webapi',
u'django_evolution']
Installed Middleware:
[u'django.middleware.gzip.GZipMiddleware',
u'reviewboard.admin.middleware.InitReviewBoardMiddleware',
u'django.middleware.clickjacking.XFrameOptionsMiddleware',
u'django.middleware.common.CommonMiddleware',
u'django.middleware.doc.XViewMiddleware',
u'django.middleware.http.ConditionalGetMiddleware',
u'django.middleware.locale.LocaleMiddleware',
u'django.contrib.sessions.middleware.SessionMiddleware',
u'django.contrib.auth.middleware.AuthenticationMiddleware',
u'django.contrib.messages.middleware.MessageMiddleware',
u'djblets.siteconfig.middleware.SettingsMiddleware',
u'reviewboard.admin.middleware.LoadSettingsMiddleware',
u'djblets.extensions.middleware.ExtensionsMiddleware',
u'djblets.log.middleware.LoggingMiddleware',
u'reviewboard.accounts.middleware.TimezoneMiddleware',
u'reviewboard.admin.middleware.CheckUpdatesRequiredMiddleware',
u'reviewboard.admin.middleware.X509AuthMiddleware',
u'reviewboard.site.middleware.LocalSiteMiddleware',
u'djblets.extensions.middleware.ExtensionsMiddlewareRunner']
Traceback:
File /srv/http/reviewboard/venv/local/lib/python2.7/site-packages/Django-1.6.4-py2.7.egg/django/core/handlers/base.py
in
get_response
114. response = wrapped_callback(request,
*callback_args, **callback_kwargs)
File /srv/http/reviewboard/venv/local/lib/python2.7/site-packages/Django-1.6.4-py2.7.egg/django/views/decorators/debug.py
in
sensitive_post_parameters_wrapper
75. return view(request, *args, **kwargs)
File /srv/http/reviewboard/venv/local/lib/python2.7/site-packages/Django-1.6.4-py2.7.egg/django/views/decorators/cache.py
in
_wrapped_view_func
52. response = view_func(request, *args, **kwargs)
File /srv/http/reviewboard/venv/local/lib/python2.7/site-packages/Django-1.6.4-py2.7.egg/django/contrib/auth/views.py
in
password_reset_confirm
197. post_reset_redirect = reverse('password_reset_complete')
File /srv/http/reviewboard/venv/local/lib/python2.7/site-packages/Django-1.6.4-py2.7.egg/django/core/urlresolvers.py
in
reverse
532. return iri_to_uri(resolver._reverse_with_prefix(view, prefix,
*args, **kwargs))
File /srv/http/reviewboard/venv/local/lib/python2.7/site-packages/Django-1.6.4-py2.7.egg/django/core/urlresolvers.py
in
_reverse_with_prefix
452. (lookup_view_s, args, kwargs,
len(patterns), patterns))
Exception Type: NoReverseMatch at
/account/reset/MQ-3rm-b5e15bbd57f784bc0a0a/
Exception Value: Reverse for 'password_reset_complete' with arguments '()'
and keyword arguments '{}' not found. 0 pattern(s) tried: []
--
You received this message because this project is configured to send all
Re: Issue 3343 in reviewboard: Unable to add CVS repository with version below 1.12
Updates: Status: PendingReview Owner: trowb...@gmail.com Comment #1 on issue 3343 by trowb...@gmail.com: Unable to add CVS repository with version below 1.12 http://code.google.com/p/reviewboard/issues/detail?id=3343 (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: Issue 3345 in reviewboard: Password reset 500 fail
Updates: Status: Fixed Comment #1 on issue 3345 by trowb...@gmail.com: Password reset 500 fail http://code.google.com/p/reviewboard/issues/detail?id=3345 Fixed in release-2.0.x (4fa21d9). Thanks! -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard-issues+unsubscr...@googlegroups.com. To post to this group, send email to reviewboard-issues@googlegroups.com. Visit this group at http://groups.google.com/group/reviewboard-issues. For more options, visit https://groups.google.com/d/optout.
Re: Issue 3342 in reviewboard: ADS authentication not available after upgrade
Comment #2 on issue 3342 by tjbut...@gmail.com: ADS authentication not available after upgrade http://code.google.com/p/reviewboard/issues/detail?id=3342 Commands as follows. There was also an update to Django to track the latest requirements. Unpack djblets tarball cd djblets python setup.py build python setup.py install cd .. Unpack reviewboard tarball cd reviewboard python setup.py build python setup.py install rb-site upgrade /srv/reviewboard/reviews.cea.com.au /etc/init.d/memcached stop;/etc/init.d/apache2 restart;/etc/init.d/memcached start -- 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 3342 in reviewboard: ADS authentication not available after upgrade
Comment #3 on issue 3342 by trowb...@gmail.com: ADS authentication not available after upgrade http://code.google.com/p/reviewboard/issues/detail?id=3342 Is there a reason why you aren't using the .egg packages? -- 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 3342 in reviewboard: ADS authentication not available after upgrade
Comment #4 on issue 3342 by tjbut...@gmail.com: ADS authentication not available after upgrade http://code.google.com/p/reviewboard/issues/detail?id=3342 The machine in question is not connected to the internet, so I cannot download eggs directly with setuptools, or similar. I have generally found it easier to install from source, particularly when tracking release candidates. This is mostly a habit I have built up while supporting Trac, and also do with Reviewboard now. -- 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 3342 in reviewboard: ADS authentication not available after upgrade
Comment #5 on issue 3342 by tjbut...@gmail.com: ADS authentication not available after upgrade http://code.google.com/p/reviewboard/issues/detail?id=3342 I fetched the latest djblets and reviewboard using git today, and installed as normal. All is OK now - ADS configuration is present and working. One difference today is that I cleared my web browser cache history of everything today, as I have found that helps with reviewboard upgrades sometimes. I thought I had done that previously, but was only clearing one day, not everything. -- 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 3342 in reviewboard: ADS authentication not available after upgrade
Updates: Status: SetupIssue Comment #6 on issue 3342 by trowb...@gmail.com: ADS authentication not available after upgrade http://code.google.com/p/reviewboard/issues/detail?id=3342 OK. My guess is that there was a VersionConflict somewhere between installed versions of different packages and their different requirements. When that happens, python won't load any entrypoints, which would manifest as missing authentication backends/SCM backends/hosting services. Glad it's working now. -- 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.
