Re: Upgrade rb 2.x - Unable to import settings_local.py: No module named settings_local
Hi Christian, I saw that thread that's why I uninstalled RB from yum (even if the errors are different. I uninstalled today Django and Djiblets but it still compains about settings: [root@centos6 ~]# rpm -qa|grep setuptools python-setuptools-0.6.10-3.el6.noarch [root@centos6 ~]# rpm -qa|grep setuptools python-setuptools-0.6.10-3.el6.noarch [root@centos6 ~]# rpm -qa|grep python python-iniparse-0.3.1-2.1.el6.noarch newt-python-0.52.11-3.el6.x86_64 python-recaptcha-client-1.0.6-4.el6.noarch python-pip-1.3.1-4.el6.noarch python-crypto-2.0.1-22.el6.x86_64 python-mimeparse-0.1.4-1.el6.noarch python-nose-0.10.4-3.1.el6.noarch python-slimit-0.7.4-3.el6.noarch python-ldap-2.3.10-1.el6.x86_64 python-pycurl-7.19.0-8.el6.x86_64 setools-libs-python-3.3.7-4.el6.x86_64 policycoreutils-python-2.0.83-19.39.el6.x86_64 python-imaging-1.1.6-19.el6.x86_64 python-memcached-1.43-6.el6.noarch python-markdown-2.0.1-3.1.el6.noarch python-psycopg2-2.0.14-2.el6.x86_64 MySQL-python-1.2.3-0.3.c1.1.el6.x86_64 python-django-pipeline-1.2.24-2.el6.noarch python-feedparser-5.1.2-2.el6.noarch python-libs-2.6.6-52.el6.x86_64 python-devel-2.6.6-52.el6.x86_64 rpm-python-4.8.0-37.el6.x86_64 libsemanage-python-2.0.43-4.2.el6.x86_64 python-paramiko-1.7.5-2.1.el6.noarch audit-libs-python-2.2-4.el6_5.x86_64 python-flup-1.0.2-2.el6.noarch python-pygments-1.1.1-1.el6.noarch python-django-evolution-0.6.9-4.el6.noarch python-djblets-0.7.30-2.el6.noarch python-2.6.6-52.el6.x86_64 python-urlgrabber-3.9.1-9.el6.noarch libselinux-python-2.0.94-5.3.el6_4.1.x86_64 python-setuptools-0.6.10-3.el6.noarch libproxy-python-0.3.0-4.el6_3.x86_64 python-docutils-0.6-1.el6.noarch python-dateutil-1.4.1-6.el6.noarch python-odict-1.5.0-4.el6.noarch python-simplejson-2.0.9-3.1.el6.x86_64 python-ply-3.4-4.el6.noarch [root@centos6 ~]# rpm -qa|grep -i django python-django-pipeline-1.2.24-2.el6.noarch Django14-1.4.13-1.el6.noarch python-django-evolution-0.6.9-4.el6.noarch [root@centos6 ~]# yum remove python-sjango-pipeline Django python-django-evolution Loaded plugins: fastestmirror Setting up Remove Process No Match for argument: python-sjango-pipeline Loading mirror speeds from cached hostfile * base: centos.mirrors.linux.ro * epel: ftp.ines.lug.ro * extras: centos.mirrors.linux.ro * updates: centos.mirrors.linux.ro Resolving Dependencies -- Running transaction check --- Package Django14.noarch 0:1.4.13-1.el6 will be erased -- Processing Dependency: Django for package: python-django-pipeline-1.2.24-2.el6.noarch -- Processing Dependency: Django14 for package: python-djblets-0.7.30-2.el6.noarch --- Package python-django-evolution.noarch 1:0.6.9-4.el6 will be erased -- Running transaction check --- Package python-django-pipeline.noarch 0:1.2.24-2.el6 will be erased --- Package python-djblets.noarch 0:0.7.30-2.el6 will be erased -- Finished Dependency Resolution Dependencies Resolved Package ArchVersion Repository Size Removing: Django14 noarch 1.4.13-1.el6 @epel 16 M python-django-evolution noarch 1:0.6.9-4.el6@epel 703 k Removing for dependencies: python-django-pipeline noarch 1.2.24-2.el6 @epel 120 k python-djblets noarch 0.7.30-2.el6 @epel 2.2 M Transaction Summary Remove4 Package(s) Installed size: 19 M Is this ok [y/N]: y Downloading Packages: Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction Erasing: python-djblets-0.7.30-2.el6.noarch 1/4 Erasing: python-django-pipeline-1.2.24-2.el6.noarch 2/4 Erasing: 1:python-django-evolution-0.6.9-4.el6.noarch 3/4 Erasing: Django14-1.4.13-1.el6.noarch 4/4 Verifying : Django14-1.4.13-1.el6.noarch 1/4 Verifying : python-django-pipeline-1.2.24-2.el6.noarch 2/4 Verifying : python-djblets-0.7.30-2.el6.noarch 3/4 Verifying : 1:python-django-evolution-0.6.9-4.el6.noarch 4/4 Removed: Django14.noarch 0:1.4.13-1.el6 python-django-evolution.noarch 1:0.6.9-4.el6 Dependency Removed: python-django-pipeline.noarch 0:1.2.24-2.el6 python-djblets.noarch 0:0.7.30-2.el6 Complete! [root@centos6 ~]# easy_install -U django_evolution Searching for django-evolution Reading http://pypi.python.org/simple/django_evolution/ Reading http://code.google.com/p/django-evolution/ Reading http://downloads.reviewboard.org/releases/django-evolution/0.7/ Best match: django-evolution 0.7.3 Processing django_evolution-0.7.3-py2.6.egg django-evolution 0.7.3 is
error when svn root is not project root
ok, so I have a setup where my company's root svn is different from the projects that people checkout. In otherwords, each project is setup as only a folder in svn. so svn info shows: URL: https://url.org/svn/root/projectname Relative URL: ^/projectname Repository Root: https://url.org/svn/root The repo is setup in ReviewBoard as https://url.org/svn/root/projectname Anytime I run rbt post, I get: The file was not found in the repository. (HTTP 400, API Error 207) I AM able to get diffs to post automatically using the post-review version that comes bundled with debian testing by running something like: post-review --repository-url=https://url.org/svn/root/projectname --diff-filename=/tmp/manualdiff But obviously, this is hackish and post-review is deprecated, from my understanding. If I insert a logging line into get_file in pysvn.py per another post here, I see something like the following in the logs: - repopath = https://url.org/svn/root/projectname;, path = /projectname/file.py, revision = 18376 Which I assume why this is not working is because of the screwy path root problem and the duplicate projectname above. So, my question... what is the best way to make this work for automatic diff uploads using rbt? Even if I have to hardcode something hackish, I would rather have your advice on where is the best place to do so. Any help appreciated. -- 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: error when svn root is not project root
Hi, Even if your users are checking out from a subdirectory, you need to configure Review Board to have one entry for the root of the repository. RBTools will compare against the Repository Root field, figure out the relative URL they’re using from there, and look up the correct URL on Review Board. What happens if you try that? Christian -- Christian Hammond - christ...@beanbaginc.com Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On August 5, 2014 at 2:15:49 PM, emptyt...@gmail.com (emptyt...@gmail.com) wrote: ok, so I have a setup where my company's root svn is different from the projects that people checkout. In otherwords, each project is setup as only a folder in svn. so svn info shows: URL: https://url.org/svn/root/projectname Relative URL: ^/projectname Repository Root: https://url.org/svn/root The repo is setup in ReviewBoard as https://url.org/svn/root/projectname Anytime I run rbt post, I get: The file was not found in the repository. (HTTP 400, API Error 207) I AM able to get diffs to post automatically using the post-review version that comes bundled with debian testing by running something like: post-review --repository-url=https://url.org/svn/root/projectname --diff-filename=/tmp/manualdiff But obviously, this is hackish and post-review is deprecated, from my understanding. If I insert a logging line into get_file in pysvn.py per another post here, I see something like the following in the logs: - repopath = https://url.org/svn/root/projectname;, path = /projectname/file.py, revision = 18376 Which I assume why this is not working is because of the screwy path root problem and the duplicate projectname above. So, my question... what is the best way to make this work for automatic diff uploads using rbt? Even if I have to hardcode something hackish, I would rather have your advice on where is the best place to do so. Any help appreciated. -- 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: error when svn root is not project root
Interesting... so apparently I was making this too complicated... I was worried that because my users don't have read access to the root that this wouldn't work, but it seems to. Thanks! On Tuesday, August 5, 2014 4:18:22 PM UTC-5, Christian Hammond wrote: Hi, Even if your users are checking out from a subdirectory, you need to configure Review Board to have one entry for the root of the repository. RBTools will compare against the Repository Root field, figure out the relative URL they’re using from there, and look up the correct URL on Review Board. What happens if you try that? Christian -- Christian Hammond - chri...@beanbaginc.com javascript: Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On August 5, 2014 at 2:15:49 PM, empt...@gmail.com javascript: ( empt...@gmail.com javascript:) wrote: ok, so I have a setup where my company's root svn is different from the projects that people checkout. In otherwords, each project is setup as only a folder in svn. so svn info shows: URL: https://url.org/svn/root/projectname Relative URL: ^/projectname Repository Root: https://url.org/svn/root The repo is setup in ReviewBoard as https://url.org/svn/root/projectname Anytime I run rbt post, I get: The file was not found in the repository. (HTTP 400, API Error 207) I AM able to get diffs to post automatically using the post-review version that comes bundled with debian testing by running something like: post-review --repository-url=https://url.org/svn/root/projectname --diff-filename=/tmp/manualdiff https://url.org/svn/root/projectname--diff-filename=/tmp/manualdiff But obviously, this is hackish and post-review is deprecated, from my understanding. If I insert a logging line into get_file in pysvn.py per another post here, I see something like the following in the logs: - repopath = https://url.org/svn/root/projectname;, path = /projectname/file.py, revision = 18376 Which I assume why this is not working is because of the screwy path root problem and the duplicate projectname above. So, my question... what is the best way to make this work for automatic diff uploads using rbt? Even if I have to hardcode something hackish, I would rather have your advice on where is the best place to do so. Any help appreciated. -- 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.
Clarification of Pre-Commit Workflow
I've been reading the workflow page here: https://www.reviewboard.org/docs/manual/2.0/users/getting-started/workflow/ We're planning to follow the pre-commit workflow. Would be grateful if someone could clarify some of the steps for us. Here's my current understanding of the first few steps: *1) Make a change to your local source tree.* Here we: a) Edit a file b) Commit the change *2) Create a review request for your new change.* Here we: a) Run rbt post (which seems to post the latest commit?) *3) Publish the review request and wait for your reviewers to see it.* Here we: a) Log into Review Board b) Choose reviewers c) Publish the review request At the moment we are all committing to master, then push to our origin regularly. 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.
Re: Issue 3518 in reviewboard: Can't upload review due to UnicodeDecodeError
Updates: Status: Fixed Comment #3 on issue 3518 by trowb...@gmail.com: Can't upload review due to UnicodeDecodeError http://code.google.com/p/reviewboard/issues/detail?id=3518 Fixed in release-2.0.x (6c7881f). 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 3503 in reviewboard: Formattings errors in description field
Updates: Status: PendingReview Owner: trowb...@gmail.com Comment #1 on issue 3503 by trowb...@gmail.com: Formattings errors in description field http://code.google.com/p/reviewboard/issues/detail?id=3503 (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.
