Using Hashlibs.sha instead of hashlib.md5 on FIPS-enabled CentOS7. Am I totally off base? Is this possible?
Ideally we'd like to use the security profile for the NIST 800-171. Yes, this is for a security *need *and not some whimsical desire for security. For all new installs, that's what we're going with. That includes a certain required level of encryption. Reviewboard as is uses hashlibs.md5, and FIPS mode for CentOS7 rejects this. I'm unsure, but is there a simple pre-conf switch I can add to change the setting? I'm looking for it at the moment, but haven't found anything yet. Is this a Python/CentOS thing? I honestly don't know exactly where to look for support at the moment. -- Supercharge your Review Board with Power Pack: https://www.reviewboard.org/powerpack/ Want us to host Review Board for you? Check out RBCommons: https://rbcommons.com/ Happy user? Let us know! https://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups "Review Board Community" 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: Changing Python Version (2.6 -> 2.7) for Existing Reviewboard Installation on CentOS 6
That works for installing Python, and that's fine. And it looks easier than using make altinstall or another method. But it doesn't really address the primary issue which is getting reviewboard to *use* the alternative version of python. On Mon, Nov 2, 2015 at 5:43 PM, Alfred von Campe <alf...@von-campe.com> wrote: > This is what I do on the CentOS 6 systems I mange: > > # Install repo file and then Python itself > rpm -ivh > http://dl.iuscommunity.org/pub/ius/stable/Redhat/6/i386/ius-release-1.0-14.ius.el6.noarch.rpm > yum install -y python27 python27-virtualenv > > Alfred > > On Nov 2, 2015, at 17:31, Zachary Gallagher <zachary.gallag...@remcom.com> > wrote: > > Rather than update the entire OS, I'd like to install python 2.7 on > CentOS6. Now, so far as I am aware, there's no method for installing python > over the system version without breaking at *least* yum. If not more. > Maybe there's a way? But I don't know what it is. > > > So installing python 2.7 as, say, /usr/local/python27 is totally easy and > I have no problem doing that. But what I can't find in the documentation is > whether or not it's possible to change which python binaries/libraries > reviewboard uses without completely recompiling and installing. And since > we use easy_install, that seems like it would make it even more complicated. > > Is there a known, working method for installing python2.7 side-by-side on > a CentOS 6 machine, and getting an existing reviewboard installation to > recognize it? > > -- > Supercharge your Review Board with Power Pack: > https://www.reviewboard.org/powerpack/ > Want us to host Review Board for you? Check out RBCommons: > https://rbcommons.com/ > Happy user? Let us know! https://www.reviewboard.org/users/ > --- > You received this message because you are subscribed to the Google Groups > "reviewboard" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to reviewboard+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > > > -- > Supercharge your Review Board with Power Pack: > https://www.reviewboard.org/powerpack/ > Want us to host Review Board for you? Check out RBCommons: > https://rbcommons.com/ > Happy user? Let us know! https://www.reviewboard.org/users/ > --- > You received this message because you are subscribed to a topic in the > Google Groups "reviewboard" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/reviewboard/fyCiYhx41KU/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > reviewboard+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- Zachary Gallagher System Administrator Remcom, Inc. 315 S. Allen St., Ste 420 State College, PA 16801 Office: 814-861-1299 x298 Mobile: 814-218-3762 -- Supercharge your Review Board with Power Pack: https://www.reviewboard.org/powerpack/ Want us to host Review Board for you? Check out RBCommons: https://rbcommons.com/ Happy user? Let us know! https://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups "reviewboard" group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Changing Python Version (2.6 -> 2.7) for Existing Reviewboard Installation on CentOS 6
That works for installing Python, and that's fine. And it looks easier than using make altinstall or another method. But it doesn't really address the primary issue which is getting reviewboard to *use* the alternative version of python. On Monday, November 2, 2015 at 5:43:36 PM UTC-5, Alfred von Campe wrote: > > This is what I do on the CentOS 6 systems I mange: > > # Install repo file and then Python itself > rpm -ivh > http://dl.iuscommunity.org/pub/ius/stable/Redhat/6/i386/ius-release-1.0-14.ius.el6.noarch.rpm > yum install -y python27 python27-virtualenv > > Alfred > > On Nov 2, 2015, at 17:31, Zachary Gallagher <zachary@remcom.com > > wrote: > > Rather than update the entire OS, I'd like to install python 2.7 on > CentOS6. Now, so far as I am aware, there's no method for installing python > over the system version without breaking at *least* yum. If not more. > Maybe there's a way? But I don't know what it is. > > > So installing python 2.7 as, say, /usr/local/python27 is totally easy and > I have no problem doing that. But what I can't find in the documentation is > whether or not it's possible to change which python binaries/libraries > reviewboard uses without completely recompiling and installing. And since > we use easy_install, that seems like it would make it even more complicated. > > Is there a known, working method for installing python2.7 side-by-side on > a CentOS 6 machine, and getting an existing reviewboard installation to > recognize it? > > -- > Supercharge your Review Board with Power Pack: > https://www.reviewboard.org/powerpack/ > Want us to host Review Board for you? Check out RBCommons: > https://rbcommons.com/ > Happy user? Let us know! https://www.reviewboard.org/users/ > --- > You received this message because you are subscribed to the Google Groups > "reviewboard" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to reviewboard...@googlegroups.com . > For more options, visit https://groups.google.com/d/optout. > > > -- Supercharge your Review Board with Power Pack: https://www.reviewboard.org/powerpack/ Want us to host Review Board for you? Check out RBCommons: https://rbcommons.com/ Happy user? Let us know! https://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups "reviewboard" group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Unapplied Evolutions error possibly Django related after installing 2.0 RC2. Can upgrade a second time to remove the error and site functions, but admin console and account preferences return
/messages/storage/cookie.py, line 152, in _decode* *return json.loads(value, cls=MessageDecoder)* * File /usr/lib64/python2.6/json/__init__.py, line 318, in loads* *return cls(encoding=encoding, **kw).decode(s)* * File /usr/lib/python2.6/site-packages/Django-1.6.2-py2.6.egg/django/contrib/messages/storage/cookie.py, line 47, in decode* *return self.process_messages(decoded)* * File /usr/lib/python2.6/site-packages/Django-1.6.2-py2.6.egg/django/contrib/messages/storage/cookie.py, line 39, in process_messages* *return [self.process_messages(item) for item in obj]* * File /usr/lib/python2.6/site-packages/Django-1.6.2-py2.6.egg/django/contrib/messages/storage/cookie.py, line 37, in process_messages* *obj[3] = mark_safe(obj[3])* *IndexError: list index out of range* *(END)* On Friday, April 4, 2014 8:37:47 PM UTC-4, Christian Hammond wrote: Hi Zachary, As per the instructions, everything within the begin/end log output can be ignored if the install is successful. Those messages you saw about unapplied evolutions were just part of the normal upgrade path, and were then successfully applied. From this end, it looks like everything went fine. What errors are you seeing in the log files (reviewboard.log or apache's error_log) when you see the 500 error? Christian -- Christian Hammond - chi...@chipx86.com javascript: Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On Fri, Apr 4, 2014 at 2:36 PM, Zachary Gallagher zachary@remcom.comjavascript: wrote: *[root@mercury html]# rb-site upgrade /var/www/html/reviewboard* *Rebuilding directory structure* *Updating database. This may take a while.* *The log output below, including warnings and errors,* *can be ignored unless upgrade fails.* *-- begin log output --* *Creating tables ...* *Upgrading Review Board from 1.7.22 to 2.0 RC2* *There are unapplied evolutions for auth.* *There are unapplied evolutions for contenttypes.* *There are unapplied evolutions for attachments.* *There are unapplied evolutions for changedescs.* *There are unapplied evolutions for diffviewer.* *There are unapplied evolutions for hostingsvcs.* *There are unapplied evolutions for reviews.* *There are unapplied evolutions for scmtools.* */usr/lib/python2.6/site-packages/Djblets-0.8rc1-py2.6.egg/djblets/util/fields.py:11: DeprecationWarning: djblets.util.fields is deprecated. Use djblets.db.fields instead.* * 'djblets.db.fields instead.', DeprecationWarning)* *Adding baseline version for new models* *Project signature has changed - an evolution is required* *There are unapplied evolutions for accounts.* *Installing custom SQL ...* *Installing indexes ...* *Installed 0 object(s) from 0 fixture(s)* *Evolution successful.* *--- end log output ---* *Resetting in-database caches.* *Upgrade complete!* *[root@mercury html]# service httpd start* *Starting httpd: [ OK ]* *[root@mercury html]# service httpd stop* *Stopping httpd:[ OK ]* *[root@mercury html]# rb-site upgrade /var/www/html/reviewboard* *Rebuilding directory structure* *Updating database. This may take a while.* *The log output below, including warnings and errors,* *can be ignored unless upgrade fails.* *-- begin log output --* *Creating tables ...* *Installing custom SQL ...* *Installing indexes ...* *Installed 0 object(s) from 0 fixture(s)* *No evolution required.* *--- end log output ---* *Resetting in-database caches.* *Upgrade complete!* *[root@mercury html]# service httpd start* The above is my exact console output in upgrading the server. I upgrade the site the first time and I'm unable to load the site at all. I upgrade again and the site will load, I can navigate to review requests and certain things. But attempting to access account preferences or the admin console returns the 500 error. Erasing the database and recreating it from the backup allows me to reproduce this error repeatedly. -- 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
Re: Unapplied Evolutions error possibly Django related after installing 2.0 RC2. Can upgrade a second time to remove the error and site functions, but admin console and account preferences return
Also, just learned another normal user with some admin privileges does seem to be able to access the admin pages (at least the ones he has access to). So it seems to be account related, somehow. On Friday, April 4, 2014 8:37:47 PM UTC-4, Christian Hammond wrote: Hi Zachary, As per the instructions, everything within the begin/end log output can be ignored if the install is successful. Those messages you saw about unapplied evolutions were just part of the normal upgrade path, and were then successfully applied. From this end, it looks like everything went fine. What errors are you seeing in the log files (reviewboard.log or apache's error_log) when you see the 500 error? Christian -- Christian Hammond - chi...@chipx86.com javascript: Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On Fri, Apr 4, 2014 at 2:36 PM, Zachary Gallagher zachary@remcom.comjavascript: wrote: *[root@mercury html]# rb-site upgrade /var/www/html/reviewboard* *Rebuilding directory structure* *Updating database. This may take a while.* *The log output below, including warnings and errors,* *can be ignored unless upgrade fails.* *-- begin log output --* *Creating tables ...* *Upgrading Review Board from 1.7.22 to 2.0 RC2* *There are unapplied evolutions for auth.* *There are unapplied evolutions for contenttypes.* *There are unapplied evolutions for attachments.* *There are unapplied evolutions for changedescs.* *There are unapplied evolutions for diffviewer.* *There are unapplied evolutions for hostingsvcs.* *There are unapplied evolutions for reviews.* *There are unapplied evolutions for scmtools.* */usr/lib/python2.6/site-packages/Djblets-0.8rc1-py2.6.egg/djblets/util/fields.py:11: DeprecationWarning: djblets.util.fields is deprecated. Use djblets.db.fields instead.* * 'djblets.db.fields instead.', DeprecationWarning)* *Adding baseline version for new models* *Project signature has changed - an evolution is required* *There are unapplied evolutions for accounts.* *Installing custom SQL ...* *Installing indexes ...* *Installed 0 object(s) from 0 fixture(s)* *Evolution successful.* *--- end log output ---* *Resetting in-database caches.* *Upgrade complete!* *[root@mercury html]# service httpd start* *Starting httpd: [ OK ]* *[root@mercury html]# service httpd stop* *Stopping httpd:[ OK ]* *[root@mercury html]# rb-site upgrade /var/www/html/reviewboard* *Rebuilding directory structure* *Updating database. This may take a while.* *The log output below, including warnings and errors,* *can be ignored unless upgrade fails.* *-- begin log output --* *Creating tables ...* *Installing custom SQL ...* *Installing indexes ...* *Installed 0 object(s) from 0 fixture(s)* *No evolution required.* *--- end log output ---* *Resetting in-database caches.* *Upgrade complete!* *[root@mercury html]# service httpd start* The above is my exact console output in upgrading the server. I upgrade the site the first time and I'm unable to load the site at all. I upgrade again and the site will load, I can navigate to review requests and certain things. But attempting to access account preferences or the admin console returns the 500 error. Erasing the database and recreating it from the backup allows me to reproduce this error repeatedly. -- 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: Unapplied Evolutions error possibly Django related after installing 2.0 RC2. Can upgrade a second time to remove the error and site functions, but admin console and account preferences return
False positive. It's cookie related, or must be. I had been working in a different browser when I'd tested the site after the server restart. Working with the original browser returns the issue. Just thought you'd want to know. On Monday, April 7, 2014 3:32:02 PM UTC-4, Christian Hammond wrote: Looks like something was stuck. Bad session data in the database or in a cookie, I'm guessing, judging by the load error. Glad it's working now! Christian On Monday, April 7, 2014, Zachary Gallagher zachary@remcom.comjavascript: wrote: Huh... Nevermind. I mean, if you're still curious about this bug/behavior. I can answer questions but... I just restarted the server (for a reason unrelated to this matter) and the problem went away. Everything's working fine now. Pages are loading faster, too. (Page load times had decreased post-update, but I wasn't ready to attribute that directly to anything yet). So, looks like something reset. Mysql? On Friday, April 4, 2014 5:36:28 PM UTC-4, Zachary Gallagher wrote: *[root@mercury html]# rb-site upgrade /var/www/html/reviewboard* *Rebuilding directory structure* *Updating database. This may take a while.* *The log output below, including warnings and errors,* *can be ignored unless upgrade fails.* *-- begin log output --* *Creating tables ...* *Upgrading Review Board from 1.7.22 to 2.0 RC2* *There are unapplied evolutions for auth.* *There are unapplied evolutions for contenttypes.* *There are unapplied evolutions for attachments.* *There are unapplied evolutions for changedescs.* *There are unapplied evolutions for diffviewer.* *There are unapplied evolutions for hostingsvcs.* *There are unapplied evolutions for reviews.* *There are unapplied evolutions for scmtools.* */usr/lib/python2.6/site-packages/Djblets-0.8rc1-py2.6.egg/djblets/util/fields.py:11: DeprecationWarning: djblets.util.fields is deprecated. Use djblets.db.fields instead.* * 'djblets.db.fields instead.', DeprecationWarning)* *Adding baseline version for new models* *Project signature has changed - an evolution is required* *There are unapplied evolutions for accounts.* *Installing custom SQL ...* *Installing indexes ...* *Installed 0 object(s) from 0 fixture(s)* *Evolution successful.* *--- end log output ---* *Resetting in-database caches.* *Upgrade complete!* *[root@mercury html]# service httpd start* *Starting httpd: [ OK ]* *[root@mercury html]# service httpd stop* *Stopping httpd:[ OK ]* *[root@mercury html]# rb-site upgrade /var/www/html/reviewboard* *Rebuilding directory structure* *Updating database. This may take a while.* *The log output below, including warnings and errors,* *can be ignored unless upgrade fails.* *-- begin log output --* *Creating tables ...* *Installing custom SQL ...* *Installing indexes ...* *Installed 0 object(s) from 0 fixture(s)* *No evolution required.* *--- end log output ---* *Resetting in-database caches.* *Upgrade complete!* *[root@mercury html]# service httpd start* The above is my exact console output in upgrading the server. I upgrade the site the first time and I'm unable to load the site at all. I upgrade again and the site will load, I can navigate to review requests and certain things. But attempting to access account preferences or the admin console returns the 500 error. Erasing the database and recreating it from the backup allows me to reproduce this error repeatedly. -- 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. -- -- Christian Hammond - chi...@chipx86.com javascript: Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com -- 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.
Unapplied Evolutions error possibly Django related after installing 2.0 RC2. Can upgrade a second time to remove the error and site functions, but admin console and account preferences return ERR:
*[root@mercury html]# rb-site upgrade /var/www/html/reviewboard* *Rebuilding directory structure* *Updating database. This may take a while.* *The log output below, including warnings and errors,* *can be ignored unless upgrade fails.* *-- begin log output --* *Creating tables ...* *Upgrading Review Board from 1.7.22 to 2.0 RC2* *There are unapplied evolutions for auth.* *There are unapplied evolutions for contenttypes.* *There are unapplied evolutions for attachments.* *There are unapplied evolutions for changedescs.* *There are unapplied evolutions for diffviewer.* *There are unapplied evolutions for hostingsvcs.* *There are unapplied evolutions for reviews.* *There are unapplied evolutions for scmtools.* */usr/lib/python2.6/site-packages/Djblets-0.8rc1-py2.6.egg/djblets/util/fields.py:11: DeprecationWarning: djblets.util.fields is deprecated. Use djblets.db.fields instead.* * 'djblets.db.fields instead.', DeprecationWarning)* *Adding baseline version for new models* *Project signature has changed - an evolution is required* *There are unapplied evolutions for accounts.* *Installing custom SQL ...* *Installing indexes ...* *Installed 0 object(s) from 0 fixture(s)* *Evolution successful.* *--- end log output ---* *Resetting in-database caches.* *Upgrade complete!* *[root@mercury html]# service httpd start* *Starting httpd: [ OK ]* *[root@mercury html]# service httpd stop* *Stopping httpd:[ OK ]* *[root@mercury html]# rb-site upgrade /var/www/html/reviewboard* *Rebuilding directory structure* *Updating database. This may take a while.* *The log output below, including warnings and errors,* *can be ignored unless upgrade fails.* *-- begin log output --* *Creating tables ...* *Installing custom SQL ...* *Installing indexes ...* *Installed 0 object(s) from 0 fixture(s)* *No evolution required.* *--- end log output ---* *Resetting in-database caches.* *Upgrade complete!* *[root@mercury html]# service httpd start* The above is my exact console output in upgrading the server. I upgrade the site the first time and I'm unable to load the site at all. I upgrade again and the site will load, I can navigate to review requests and certain things. But attempting to access account preferences or the admin console returns the 500 error. Erasing the database and recreating it from the backup allows me to reproduce this error repeatedly. -- 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.
Login to the SCM server failed. when using rbt post -d. Also, /api/repositories is empty.
I've made it farther now than I have ever before. But I'm still running
into one last issue. (Maybe two.)
First, background information. Hopefully this makes more sense. I'm
learning Subversion as I do all this. C'est la vie.
The .reviewboardrc file reads as
REVIEWBOARD_URL = http://*ReviewBoardServer*;
REPOSITORY = *RepositoryName* (Not the name as it appears in the admin
dashboard, but it is the parent directory to branches/, trunk/, tags/. It
goes https://*ServerName/SvnDirectory/RepositoryName. *The checkout
directory is a checkout of a repository under
*RepositoryName/*branches/. The *is* a repository named *RepositoryName *in
the admin dashboard, that refers to the parent directory of branches/,
trunk/, tags/. But there have been no noted conflicts. Not sure if the
repository names in ReviewBoard matter.)
*SvnDirectory* is the actual directory under /svn/ on the machine itself.
I'm providing this information because I'm still learning Subversion, and
don't know exactly/technically what Subversion defines as repository and
working copy. I understand the concepts, but I'm still learning their
literal/technical/practical application.
Ok, so...
I'm in the checkout directory. The checkout directory is a checkout of
*RepositoryName/*branches/20131209-repo-P14. The exact directory on the
user's machine is /dfs/*User/RepositoryName*_repo_P14.
If I run just svn info I get
-bash-4.1$ svn info
Path: .
Working Copy Root Path: /dfs/*User*/*RepositoryName*_nrl_p14
URL: https://*ServerName*/*SvnDirectory*/*RepositoryName*
/branches/20131209-repo-P14
Repository Root: https://*ServerName*/*SvnDirectory*
Repository UUID: (buncha letters numbers)
Revision: 15168
Node Kind: directory
Schedule: normal
Depth: files
Last Changed Author: *User*
Last Changed Rev: 15168
Last Changed Date: 2014-01-11 13:19:21 -0500 (Sat, 11 Jan 2014)
I use rbt post -d.
It runs a bunch of svn info commands on the dev/ directory. Then gets to
this.
DEBUG:root:Making HTTP GET request to http://*ReviewBoardServer*
/api/review-requests/
DEBUG:root:Making HTTP POST request to http://*ReviewBoardServer*
/api/review-requests/
DEBUG:root:Making HTTP GET request to http://*ReviewBoardServer*
/api/review-requests/45/diffs/
DEBUG:root:Making HTTP POST request to http://*ReviewBoardServer*
/api/review-requests/45/diffs/
DEBUG:root:Got API Error 105 (HTTP code 400): One or more fields had errors
DEBUG:root:Error data: {u'fields': {u'path': [u'Login to the SCM server
failed.']}, u'stat': u'fail', u'err': {u'msg': u'One or more fields had
errors', u'code': 105}}
Traceback (most recent call last):
File /usr/bin/rbt, line 9, in module
load_entry_point('RBTools==0.5.5', 'console_scripts', 'rbt')()
File
/usr/lib/python2.6/site-packages/RBTools-0.5.5-py2.6.egg/rbtools/commands/main.py,
line 127, in main
command.run_from_argv([RB_MAIN] + args)
File
/usr/lib/python2.6/site-packages/RBTools-0.5.5-py2.6.egg/rbtools/commands/__init__.py,
line 158, in run_from_argv
exit_code = self.main(*args) or 0
File
/usr/lib/python2.6/site-packages/RBTools-0.5.5-py2.6.egg/rbtools/commands/post.py,
line 659, in main
submit_as=self.options.submit_as)
File
/usr/lib/python2.6/site-packages/RBTools-0.5.5-py2.6.egg/rbtools/commands/post.py,
line 534, in post_request
raise CommandError('\n'.join(error_msg))
rbtools.commands.CommandError: Error uploading diff
One or more fields had errors (HTTP 400, API Error 105
path: Login to the SCM server failed
Your review request still exists, but the diff is not attached.
Also, if I navigate to http://*ReviewBoardServer*/api/repositories, I get
this. Yet there are 5 repositories listed in the admin dashboard.
Not sure if that is expected or not. Not entirely up to snuff on http and
the web api.
?xml version=1.0 encoding=utf-8?
rsp
statfail/stat
err
msgObject does not exist/msg
code100/code
/err
/rsp
--
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: Login to the SCM server failed. when using rbt post -d. Also, /api/repositories is empty.
There is obviously some sort of credential mismatch. But there is no indication as to what credentials it's using on what. I don't know what is being mismatched. And I don't know how to find 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: Login to the SCM server failed. when using rbt post -d. Also, /api/repositories is empty.
I changed the password for my username to *password*. The actual, all lowercase word. Then I ran rbt post -d --username=gallagher --password=password --submit-as=gallagher And got the same error. On Wednesday, January 15, 2014 3:41:49 PM UTC-5, David Trowbridge wrote: This error is typically a problem with the credentials on the reviewboard side, not rbtools. Can you check that those are correct, and if they are, check the reviewboard log file for any more interesting errors? -David On Jan 15, 2014, at 12:35 PM, Zachary Gallagher zachary@remcom.comjavascript: wrote: I suppose it should also be said that, as far as the *actual* problem at hand. I'm sure that all the credentials I've entered were correct. I can connect to svn and ReviewBoard with them. I just don't know if there's some setting I'm missing, or I put the right ones in the wrong places. I just don't know how to see what it's trying to do before it gets the Login error. I ran a strace, but I didn't glean anything useful from it. -- 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: Login to the SCM server failed. when using rbt post -d. Also, /api/repositories is empty.
I can log in with gallagher password But I can't run *rbt post* with it. -- 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: Login to the SCM server failed. when using rbt post -d. Also, /api/repositories is empty.
Oh.
Ok, well, that's embarrassing.
But now I have a new error. And it's part of what my issue was before. When
Subversion speaks of base path. Does that refer to the parent directory
of branches/, trunk/, etc. Or the parent directory of *that* directory.
It's something that's apparently so basic that I can't even find
information on it. I was told that the repositories had to be base paths.
The error I'm getting now is
DEBUG:root:Error data: {u'stat': u'fail', u'file':
u'/*RepositoryName*/branches/20131209-repo-P14/dev/src/modelLibraries/Adapter/Makefile',
u'err': {u'msg': u'The file was not found in the repository', u'code':
207}, u'revision': u'15168'}
I think it's because the checkout is actually a directory of branches. But
it's somehow trying to act like this is the base path.
On Wednesday, January 15, 2014 3:55:20 PM UTC-5, David Trowbridge wrote:
I mean in the repository configuration in the reviewboard admin.
-David
On Jan 15, 2014, at 12:49 PM, Zachary Gallagher
zachary@remcom.comjavascript:
wrote:
I can log in with
gallagher
password
But I can't run *rbt post* with it.
--
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: Login to the SCM server failed. when using rbt post -d. Also, /api/repositories is empty.
-.- On Wednesday, January 15, 2014 3:57:25 PM UTC-5, Christian Hammond wrote: On Wed, Jan 15, 2014 at 12:02 PM, Zachary Gallagher zachary@remcom.com javascript: wrote: Also, if I navigate to http://*ReviewBoardServer*/api/repositories, I get this. Yet there are 5 repositories listed in the admin dashboard. Not sure if that is expected or not. Not entirely up to snuff on http and the web api. ?xml version=1.0 encoding=utf-8? rsp statfail/stat err msgObject does not exist/msg code100/code /err /rsp You're missing a trailing slash. It must be http://ReviewBoardServer/api/repositories/ Christian -- Christian Hammond - chi...@chipx86.com javascript: Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com -- 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: Login to the SCM server failed. when using rbt post -d. Also, /api/repositories is empty.
So this very last issue... (An optimistic claim)
DEBUG:root:Got API Error 207 (HTTP code 400): The file was not found in the
repository
DEBUG:root:Error data: {u'stat': u'fail', u'file':
u'/*RepositoryName*/branches/20131209-repo-P14/dev/src/modelLibraries/VTRPEAdapter/Makefile',
u'err': {u'msg': u'The file was not found in the repository', u'code':
207}, u'revision': u'15168'}
Traceback (most recent call last):
File /usr/bin/rbt, line 9, in module
load_entry_point('RBTools==0.5.5', 'console_scripts', 'rbt')()
File
/usr/lib/python2.6/site-packages/RBTools-0.5.5-py2.6.egg/rbtools/commands/main.py,
line 127, in main
command.run_from_argv([RB_MAIN] + args)
File
/usr/lib/python2.6/site-packages/RBTools-0.5.5-py2.6.egg/rbtools/commands/__init__.py,
line 158, in run_from_argv
exit_code = self.main(*args) or 0
File
/usr/lib/python2.6/site-packages/RBTools-0.5.5-py2.6.egg/rbtools/commands/post.py,
line 659, in main
submit_as=self.options.submit_as)
File
/usr/lib/python2.6/site-packages/RBTools-0.5.5-py2.6.egg/rbtools/commands/post.py,
line 534, in post_request
raise CommandError('\n'.join(error_msg))
rbtools.commands.CommandError: Error uploading diff
The file was not found in the repository (HTTP 400, API Error 207)
Your review request still exists, but the diff is not attached.
The file *is* there on the machine. The absolute path is
/dfs/*User*/*RepositoryName*
_nrl_p14/dev/src/modelLibraries/VTRPEAdapter/Makefile
And the path in svn is
https://*SvnServer*/*SvnDirectory*/*RepositoryName*
/branches/20131209-repo-P14/dev/src/modelLibraries/VTRPEAdapter/Makefile
Any idea what's going on? I'm running rbt post from
/dfs/*User*/*RepositoryName*_nrl_p14/
and Repository in .reviewboardrc is set to the single word
*RepositoryName.*
The slight confusion is that (and I didn't do this, so I'm not sure if it
was right or not at the time)
as noted above, these are the repositories in ReviewBoard
Repository
Path http://mercury/admin/db/scmtools/repository/?o=2
Hosting
Show this repository http://mercury/admin/db/scmtools/repository/?o=4
SvnDirectoryhttps://*SvnServer*/*SvnDirectory*/ [image: True]
RepositoryName_20131209-repo-P14https://*SvnServer*/*SvnDirectory*/
*RepositoryName*/branches/20131209-repo-P14 [image: True]RepositoryName
-Trunkhttps://*SvnServer*/*SvnDirectory*/*RepositoryName*/trunk [image:
True]Results Viewerhttps://*SvnServer*/*SvnDirectory*/results_viewer/trunk/
[image:
False]RepositoryName
https://*SvnServer*/*SvnDirectory*/*RepositoryName*/ [image: False]
5 Repositories
So I don't even know which one rbt post is trying to attach this to. The
second? Or fifth? Maybe the first?
On Wednesday, January 15, 2014 4:11:03 PM UTC-5, Christian Hammond wrote:
No worries. We used to redirect calls like /api/repositories to
/api/repositories/, but got rid of it.
The base path is everything between the root of the repository and where
the diff was taken.
So basically, if you are in /trunk/myproject, and you run 'svn diff' (or
'rbt post', which runs it for you), the base path is /trunk/myproject.
This requires that the repository entry is set up properly on Review
Board. It must always point to the very root of a Subversion repository,
and not a directory inside it.
Christian
--
Christian Hammond - chi...@chipx86.com javascript:
Review Board - http://www.reviewboard.org
Beanbag, Inc. - http://www.beanbaginc.com
On Wed, Jan 15, 2014 at 1:08 PM, Zachary Gallagher
zachary@remcom.comjavascript:
wrote:
Oh.
Ok, well, that's embarrassing.
But now I have a new error. And it's part of what my issue was before.
When Subversion speaks of base path. Does that refer to the parent
directory of branches/, trunk/, etc. Or the parent directory of *that*
directory.
It's something that's apparently so basic that I can't even find
information on it. I was told that the repositories had to be base paths.
The error I'm getting now is
DEBUG:root:Error data: {u'stat': u'fail', u'file':
u'/*RepositoryName*/branches/20131209-repo-P14/dev/src/modelLibraries/Adapter/Makefile',
u'err': {u'msg': u'The file was not found in the repository', u'code':
207}, u'revision': u'15168'}
I think it's because the checkout is actually a directory of branches.
But it's somehow trying to act like this is the base path.
On Wednesday, January 15, 2014 3:55:20 PM UTC-5, David Trowbridge wrote:
I mean in the repository configuration in the reviewboard admin.
-David
On Jan 15, 2014, at 12:49 PM, Zachary Gallagher zachary@remcom.com
wrote:
I can log in with
gallagher
password
But I can't run *rbt post* with it.
--
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
Re: Login to the SCM server failed. when using rbt post -d. Also, /api/repositories is empty.
And there is confusion at all because I haven't been the sysadmin for a
software company for long, the programmers use the term for both, and when
I once asked which was which I was met with a shrug and iunno.
On Wednesday, January 15, 2014 4:23:30 PM UTC-5, Zachary Gallagher wrote:
The reason there is a *SvnDirectory* at all is because there are multiple
'repositories' under it, all with their own branches and trunks. I put
repositories in air quotes because I'm not sure if those branches/trunks
parent directories are themselves the repositories, or if repository
exclusively refers to the entire package.
On Wednesday, January 15, 2014 4:21:11 PM UTC-5, Zachary Gallagher wrote:
So this very last issue... (An optimistic claim)
DEBUG:root:Got API Error 207 (HTTP code 400): The file was not found in
the repository
DEBUG:root:Error data: {u'stat': u'fail', u'file':
u'/*RepositoryName*/branches/20131209-repo-P14/dev/src/modelLibraries/VTRPEAdapter/Makefile',
u'err': {u'msg': u'The file was not found in the repository', u'code':
207}, u'revision': u'15168'}
Traceback (most recent call last):
File /usr/bin/rbt, line 9, in module
load_entry_point('RBTools==0.5.5', 'console_scripts', 'rbt')()
File
/usr/lib/python2.6/site-packages/RBTools-0.5.5-py2.6.egg/rbtools/commands/main.py,
line 127, in main
command.run_from_argv([RB_MAIN] + args)
File
/usr/lib/python2.6/site-packages/RBTools-0.5.5-py2.6.egg/rbtools/commands/__init__.py,
line 158, in run_from_argv
exit_code = self.main(*args) or 0
File
/usr/lib/python2.6/site-packages/RBTools-0.5.5-py2.6.egg/rbtools/commands/post.py,
line 659, in main
submit_as=self.options.submit_as)
File
/usr/lib/python2.6/site-packages/RBTools-0.5.5-py2.6.egg/rbtools/commands/post.py,
line 534, in post_request
raise CommandError('\n'.join(error_msg))
rbtools.commands.CommandError: Error uploading diff
The file was not found in the repository (HTTP 400, API Error 207)
Your review request still exists, but the diff is not attached.
The file *is* there on the machine. The absolute path is
/dfs/*User*/*RepositoryName*
_nrl_p14/dev/src/modelLibraries/VTRPEAdapter/Makefile
And the path in svn is
https://*SvnServer*/*SvnDirectory*/*RepositoryName*
/branches/20131209-repo-P14/dev/src/modelLibraries/VTRPEAdapter/Makefile
Any idea what's going on? I'm running rbt post from
/dfs/*User*/*RepositoryName*_nrl_p14/
and Repository in .reviewboardrc is set to the single word
*RepositoryName.*
The slight confusion is that (and I didn't do this, so I'm not sure if it
was right or not at the time)
as noted above, these are the repositories in ReviewBoard
Repository
Path http://mercury/admin/db/scmtools/repository/?o=2
Hosting
Show this repository http://mercury/admin/db/scmtools/repository/?o=4
SvnDirectoryhttps://*SvnServer*/*SvnDirectory*/ [image: True]
RepositoryName_20131209-repo-P14https://*SvnServer*/*SvnDirectory*/
*RepositoryName*/branches/20131209-repo-P14 [image: True]RepositoryName
-Trunkhttps://*SvnServer*/*SvnDirectory*/*RepositoryName*/trunk [image:
True]Results Viewerhttps://*SvnServer*/*SvnDirectory*
/results_viewer/trunk/ [image: False]RepositoryName
https://*SvnServer*/*SvnDirectory*/*RepositoryName*/ [image: False]
5 Repositories
So I don't even know which one rbt post is trying to attach this to.
The second? Or fifth? Maybe the first?
On Wednesday, January 15, 2014 4:11:03 PM UTC-5, Christian Hammond wrote:
No worries. We used to redirect calls like /api/repositories to
/api/repositories/, but got rid of it.
The base path is everything between the root of the repository and where
the diff was taken.
So basically, if you are in /trunk/myproject, and you run 'svn diff' (or
'rbt post', which runs it for you), the base path is /trunk/myproject.
This requires that the repository entry is set up properly on Review
Board. It must always point to the very root of a Subversion repository,
and not a directory inside it.
Christian
--
Christian Hammond - chi...@chipx86.com
Review Board - http://www.reviewboard.org
Beanbag, Inc. - http://www.beanbaginc.com
On Wed, Jan 15, 2014 at 1:08 PM, Zachary Gallagher
zachary@remcom.com wrote:
Oh.
Ok, well, that's embarrassing.
But now I have a new error. And it's part of what my issue was before.
When Subversion speaks of base path. Does that refer to the parent
directory of branches/, trunk/, etc. Or the parent directory of *that*
directory.
It's something that's apparently so basic that I can't even find
information on it. I was told that the repositories had to be base paths.
The error I'm getting now is
DEBUG:root:Error data: {u'stat': u'fail', u'file':
u'/*RepositoryName*/branches/20131209-repo-P14/dev/src/modelLibraries/Adapter/Makefile',
u'err': {u'msg': u'The file was not found in the repository', u'code':
207}, u'revision': u'15168'}
I
Re: Login to the SCM server failed. when using rbt post -d. Also, /api/repositories is empty.
And the confusion in the first place exists because I haven't been the sysadmin for a software company for long, the programmers use the term for both, and when I once asked which it was I was met with a shrug and iunno. -- 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: Login to the SCM server failed. when using rbt post -d. Also, /api/repositories is empty.
Oh my goodness. It worked.
On Wednesday, January 15, 2014 4:36:12 PM UTC-5, Christian Hammond wrote:
Run 'svn info' in your local checkout and see what Repository Root is. If
it's https://SvnServer/SvnDirectory/, then there should be only one
repository entry for that. All the others are just there to cause problems.
That would be why your rbt post is broken.
I suspect that that's the case.
If that is the case, what you want to do is set up the SvnDirectory one
and mark all the other ones as invisible so they won't be used anymore.
They won't break existing review requests, since they'll still be in the
database, but RBTools won't look at them anymore.
Christian
--
Christian Hammond - chi...@chipx86.com javascript:
Review Board - http://www.reviewboard.org
Beanbag, Inc. - http://www.beanbaginc.com
On Wed, Jan 15, 2014 at 1:23 PM, Zachary Gallagher
zachary@remcom.comjavascript:
wrote:
The reason there is a *SvnDirectory* at all is because there are
multiple 'repositories' under it, all with their own branches and trunks. I
put repositories in air quotes because I'm not sure if those
branches/trunks parent directories are themselves the repositories, or if
repository exclusively refers to the entire package.
On Wednesday, January 15, 2014 4:21:11 PM UTC-5, Zachary Gallagher wrote:
So this very last issue... (An optimistic claim)
DEBUG:root:Got API Error 207 (HTTP code 400): The file was not found in
the repository
DEBUG:root:Error data: {u'stat': u'fail', u'file': u'/*RepositoryName*
/branches/20131209-repo-P14/dev/src/modelLibraries/VTRPEAdapter/Makefile',
u'err': {u'msg': u'The file was not found in the repository', u'code':
207}, u'revision': u'15168'}
Traceback (most recent call last):
File /usr/bin/rbt, line 9, in module
load_entry_point('RBTools==0.5.5', 'console_scripts', 'rbt')()
File
/usr/lib/python2.6/site-packages/RBTools-0.5.5-py2.6.egg/rbtools/commands/main.py,
line 127, in main
command.run_from_argv([RB_MAIN] + args)
File /usr/lib/python2.6/site-packages/RBTools-0.5.5-py2.6.
egg/rbtools/commands/__init__.py, line 158, in run_from_argv
exit_code = self.main(*args) or 0
File
/usr/lib/python2.6/site-packages/RBTools-0.5.5-py2.6.egg/rbtools/commands/post.py,
line 659, in main
submit_as=self.options.submit_as)
File
/usr/lib/python2.6/site-packages/RBTools-0.5.5-py2.6.egg/rbtools/commands/post.py,
line 534, in post_request
raise CommandError('\n'.join(error_msg))
rbtools.commands.CommandError: Error uploading diff
The file was not found in the repository (HTTP 400, API Error 207)
Your review request still exists, but the diff is not attached.
The file *is* there on the machine. The absolute path is
/dfs/*User*/*RepositoryName*_nrl_p14/dev/src/modelLibraries/
VTRPEAdapter/Makefile
And the path in svn is
https://*SvnServer*/*SvnDirectory*/*RepositoryName*/branches/
20131209-repo-P14/dev/src/modelLibraries/VTRPEAdapter/Makefile
Any idea what's going on? I'm running rbt post from
/dfs/*User*/*RepositoryName*_nrl_p14/
and Repository in .reviewboardrc is set to the single word
*RepositoryName.*
The slight confusion is that (and I didn't do this, so I'm not sure if
it was right or not at the time)
as noted above, these are the repositories in ReviewBoard
Repository
Path http://mercury/admin/db/scmtools/repository/?o=2
Hosting
Show this repository http://mercury/admin/db/scmtools/repository/?o=4
SvnDirectoryhttps://*SvnServer*/*SvnDirectory*/ [image: True]
RepositoryName_20131209-repo-P14https://*SvnServer*/*SvnDirectory*/
*RepositoryName*/branches/20131209-repo-P14 [image: True]
RepositoryName-Trunkhttps://*SvnServer*/*SvnDirectory*/*RepositoryName*
/trunk [image: True] Results Viewerhttps://*SvnServer*/*SvnDirectory*
/results_viewer/trunk/ [image: False] RepositoryName
https://*SvnServer*/*SvnDirectory*/*RepositoryName*/ [image: False]
5 Repositories
So I don't even know which one rbt post is trying to attach this to.
The second? Or fifth? Maybe the first?
On Wednesday, January 15, 2014 4:11:03 PM UTC-5, Christian Hammond wrote:
No worries. We used to redirect calls like /api/repositories to
/api/repositories/, but got rid of it.
The base path is everything between the root of the repository and
where the diff was taken.
So basically, if you are in /trunk/myproject, and you run 'svn diff'
(or 'rbt post', which runs it for you), the base path is /trunk/myproject.
This requires that the repository entry is set up properly on Review
Board. It must always point to the very root of a Subversion repository,
and not a directory inside it.
Christian
--
Christian Hammond - chi...@chipx86.com
Review Board - http://www.reviewboard.org
Beanbag, Inc. - http://www.beanbaginc.com
On Wed, Jan 15, 2014 at 1:08 PM, Zachary Gallagher
zachary@remcom.com wrote:
Oh.
Ok, well, that's embarrassing
Re: RB Tools issue with repositories. RB Tools not GETing the repositories linked on our reviewboard server.
Oh, well that's better. I'm a novice sysadmin, so I'm never sure how much of any given problem is a real problem, and how much is because I left off the trailing / or something. Thanks for the response! On Tuesday, January 14, 2014 2:40:43 PM UTC-5, Christian Hammond wrote: Hi Zachary, It's trying to find a match based on the result of 'svn info'. If it can't find a repository entry on Review Board that has a Path or Mirror Path matching your local checkout, then it'll fail. This is a new tool, and we probably should improve it in this case. What I'd recommend is creating the file by hand. Just create a .reviewboardrc file containing: REVIEWBOARD_URL = http://ReviewBoardServer; REPOSITORY = repository name Now that said, that's going to fail for you right now. There's currently a bug in RBTools with name-based lookups for Subversion. I'm putting out a 0.5.4 release today though, so that'll soon be taken care of. Let me know if you would like me to rush a build to you (and let me know the Python version) and I'll do so. Christian -- Christian Hammond - chi...@chipx86.com javascript: Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On Tue, Jan 14, 2014 at 11:06 AM, Zachary Gallagher zachary@remcom.com javascript: wrote: I navigate to a subversion checkout. I run rbt setup-repo --debug. This is what I get. There are four repositories linked on our reviewboard server, but they're not hosted on the same machine. How do I get this to work? I'm sure it's something blatant that I've missed. [root@*workstation **checkout*]# rbt setup-repo --debug Enter the Review Board server URL: http://*ReviewBoardServer* DEBUG:root:Checking for a Subversion repository... DEBUG:root:Running: svn info --non-interactive DEBUG:root:Running: diff --version DEBUG:root:repository info: Path: https://*SvnServer*/svnrepo, Base path: /*Base*/*path*/*repository*, Supports changesets: False DEBUG:root:Making HTTP GET request to http://*ReviewBoardServer.Domain.com http://ReviewBoardServer.Domain.com*/api/ DEBUG:root:Making HTTP GET request to http://*ReviewBoardServer.Domain.com http://ReviewBoardServer.Domain.com*/api/info/ DEBUG:root:Making HTTP GET request to http://*ReviewBoardServer.Domain.com http://ReviewBoardServer.Domain.com*/api/repositories/ No Subversion repository found or selected for http://*ReviewBoardServer.Domain.com http://ReviewBoardServer.Domain.com*/. .reviewboardrc not created. -- 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: RB Tools issue with repositories. RB Tools not GETing the repositories linked on our reviewboard server.
That being said, http://ReviewBoardServer/api/repositories *is* empty. And I am given the impression that it shouldn't be. Was this something that was dropped. I'm using RB 1.7.16. -- 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: RB Tools issue with repositories. RB Tools not GETing the repositories linked on our reviewboard server.
Also, and I feel I may be abusing this opportunity to ask a third question: Is there still a problem I should expect if a single server is hosting multiple svn repositories? Or was that just an older version. Im looking for documentation for it, but it's not coming to me easily. On Tuesday, January 14, 2014 2:40:43 PM UTC-5, Christian Hammond wrote: Hi Zachary, It's trying to find a match based on the result of 'svn info'. If it can't find a repository entry on Review Board that has a Path or Mirror Path matching your local checkout, then it'll fail. This is a new tool, and we probably should improve it in this case. What I'd recommend is creating the file by hand. Just create a .reviewboardrc file containing: REVIEWBOARD_URL = http://ReviewBoardServer; REPOSITORY = repository name Now that said, that's going to fail for you right now. There's currently a bug in RBTools with name-based lookups for Subversion. I'm putting out a 0.5.4 release today though, so that'll soon be taken care of. Let me know if you would like me to rush a build to you (and let me know the Python version) and I'll do so. Christian -- Christian Hammond - chi...@chipx86.com javascript: Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On Tue, Jan 14, 2014 at 11:06 AM, Zachary Gallagher zachary@remcom.com javascript: wrote: I navigate to a subversion checkout. I run rbt setup-repo --debug. This is what I get. There are four repositories linked on our reviewboard server, but they're not hosted on the same machine. How do I get this to work? I'm sure it's something blatant that I've missed. [root@*workstation **checkout*]# rbt setup-repo --debug Enter the Review Board server URL: http://*ReviewBoardServer* DEBUG:root:Checking for a Subversion repository... DEBUG:root:Running: svn info --non-interactive DEBUG:root:Running: diff --version DEBUG:root:repository info: Path: https://*SvnServer*/svnrepo, Base path: /*Base*/*path*/*repository*, Supports changesets: False DEBUG:root:Making HTTP GET request to http://*ReviewBoardServer.Domain.com http://ReviewBoardServer.Domain.com*/api/ DEBUG:root:Making HTTP GET request to http://*ReviewBoardServer.Domain.com http://ReviewBoardServer.Domain.com*/api/info/ DEBUG:root:Making HTTP GET request to http://*ReviewBoardServer.Domain.com http://ReviewBoardServer.Domain.com*/api/repositories/ No Subversion repository found or selected for http://*ReviewBoardServer.Domain.com http://ReviewBoardServer.Domain.com*/. .reviewboardrc not created. -- 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: RB Tools issue with repositories. RB Tools not GETing the repositories linked on our reviewboard server.
Ah... The bases weren't added. It was sub-directories. That was the
problem. I added the base path, and re-tried 'rbt setup-repo --debug' and
got farther. Now, you mentioned name-based lookup with Subversion. Is this
the currently expected outcome?
- Create '/dfs/*UserDirectory/CheckoutFolder*/.reviewboardrc' with the
following?
-
- REVIEWBOARD_URL = http://*ReviewBoardServer*;
- REPOSITORY = *Repository*
-
- [Yes/No]: Yes
-
- Traceback (most recent call last):
- File /usr/bin/rbt, line 9, in module
- load_entry_point('RBTools==0.5.3', 'console_scripts', 'rbt')()
- File
/usr/lib/python2.6/site-packages/RBTools-0.5.3-py2.6.egg/rbtools/command
s/main.py, line 127, in main
- command.run_from_argv([RB_MAIN] + args)
- File
/usr/lib/python2.6/site-packages/RBTools-0.5.3-py2.6.egg/rbtools/commands/__init__.py,
line 158, in run_from_argv
- exit_code = self.main(*args) or 0
- File
/usr/lib/python2.6/site-packages/RBTools-0.5.3-py2.6.egg/rbtools/commands/setup_repo.py,
line 148, in main
- self.generate_config_file(outfile_path, config)
- File
/usr/lib/python2.6/site-packages/RBTools-0.5.3-py2.6.egg/rbtools/commands/setup_repo.py,
line 102, in generate_config_file
- % e.errno, e.strerror)
- TypeError: not enough arguments for format string
On Tuesday, January 14, 2014 3:24:31 PM UTC-5, Christian Hammond wrote:
Hi Zachary,
/api/repositories/ should not be empty so long as you've added more or
more repository configurations in Review Board and your user has access to
them.
It's totally fine if a single server is hosting multiple SVN repositories.
Make sure to add the base of each repository (not a subdirectory within it)
to Review Board, though. That is, http://example.com/svn/, not
http://example.com/svn/trunk/myproject.
Feel free to ask questions on here. That's what this list is for :)
Christian
--
Christian Hammond - chi...@chipx86.com javascript:
Review Board - http://www.reviewboard.org
Beanbag, Inc. - http://www.beanbaginc.com
On Tue, Jan 14, 2014 at 12:08 PM, Zachary Gallagher
zachary@remcom.com javascript: wrote:
Also, and I feel I may be abusing this opportunity to ask a third
question:
Is there still a problem I should expect if a single server is hosting
multiple svn repositories? Or was that just an older version. Im looking
for documentation for it, but it's not coming to me easily.
On Tuesday, January 14, 2014 2:40:43 PM UTC-5, Christian Hammond wrote:
Hi Zachary,
It's trying to find a match based on the result of 'svn info'. If it
can't find a repository entry on Review Board that has a Path or Mirror
Path matching your local checkout, then it'll fail. This is a new tool, and
we probably should improve it in this case.
What I'd recommend is creating the file by hand. Just create a
.reviewboardrc file containing:
REVIEWBOARD_URL = http://ReviewBoardServer;
REPOSITORY = repository name
Now that said, that's going to fail for you right now. There's currently
a bug in RBTools with name-based lookups for Subversion. I'm putting out a
0.5.4 release today though, so that'll soon be taken care of. Let me know
if you would like me to rush a build to you (and let me know the Python
version) and I'll do so.
Christian
--
Christian Hammond - chi...@chipx86.com
Review Board - http://www.reviewboard.org
Beanbag, Inc. - http://www.beanbaginc.com
On Tue, Jan 14, 2014 at 11:06 AM, Zachary Gallagher
zachary@remcom.com wrote:
I navigate to a subversion checkout. I run rbt setup-repo --debug. This
is what I get.
There are four repositories linked on our reviewboard server, but
they're not hosted on the same machine. How do I get this to work? I'm
sure
it's something blatant that I've missed.
[root@*workstation **checkout*]# rbt setup-repo --debug
Enter the Review Board server URL: http://*ReviewBoardServer*
DEBUG:root:Checking for a Subversion repository...
DEBUG:root:Running: svn info --non-interactive
DEBUG:root:Running: diff --version
DEBUG:root:repository info: Path: https://*SvnServer*/svnrepo, Base
path: /*Base*/*path*/*repository*, Supports changesets: False
DEBUG:root:Making HTTP GET request to http://*ReviewBoardServer.Domain.com
http://ReviewBoardServer.Domain.com*/api/
DEBUG:root:Making HTTP GET request to http://*ReviewBoardServer.Domain.com
http://ReviewBoardServer.Domain.com*/api/info/
DEBUG:root:Making HTTP GET request to http://*ReviewBoardServer.Domain.com
http://ReviewBoardServer.Domain.com*/api/repositories/
No Subversion repository found or selected for
http://*ReviewBoardServer.Domain.com
http://ReviewBoardServer.Domain.com*/. .reviewboardrc not created.
--
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
