Re: The current directory does not contain a checkout... (problem posting from perforce)
Thanks! On Thursday, 20 February 2014 16:44:25 UTC-5, David Trowbridge wrote: Darryl, The --p4-* options have a bug where settings in a .p4config file still had higher priority than the command-line options. I'll make sure that the fix for that bug is in the next rbtools point release. Thanks, -David On Thu, Feb 20, 2014 at 6:16 AM, Darryl McCutcheon dar...@themccutcheons.ca javascript: wrote: I'm seeing a couple issues with the perforce integration as well. The one above with the case mismatch, as well as the --p4-client parameter is not respected in RBTools 0.5.7. An integration with eclipse and reviewboard ( https://code.google.com/p/p4reviewboard/) breaks because this parameter is not respected. On Saturday, 15 February 2014 20:03:45 UTC-5, David Trowbridge wrote: Greg, You're probably getting hit by case mismatches ( https://code.google.com/p/reviewboard/issues/detail?id=3221). We'll be fixing this for 0.5.8. -David On Wed, Feb 12, 2014 at 5:14 PM, Greg Dean gr...@familydean.net wrote: Hi there, I've updated to 0.5.7 and I'm running from cygwin and I get the same result. Can rbt be run from cygwin? Here is what I get: $ rbt post -d -o 299074 DEBUG:root:Checking for a Subversion repository... DEBUG:root:Checking for a Git repository... DEBUG:root:Checking for a Mercurial repository... DEBUG:root:Checking for a CVS repository... DEBUG:root:Checking for a Perforce repository... DEBUG:root:Running: p4 info DEBUG:root:Checking for a Plastic repository... DEBUG:root:Checking for a ClearCase repository... DEBUG:root:Checking for a Bazaar repository... ERROR:root:The current directory does not contain a checkout from a supported source code repository. On Tuesday, February 4, 2014 1:14:16 PM UTC-8, Karl Nordstrom wrote: Thanks for the quick fix! 0.5.7 did it. Karl On Monday, 3 February 2014 13:50:03 UTC-8, Karl Nordstrom wrote: Okay, looking forward to getting the fix. Thanks, Karl On Monday, 3 February 2014 13:28:17 UTC-8, David Trowbridge wrote: Karl, It looks like we introduced a regression in 0.5.6 where it only will post from the client root. We'll get this sorted out asap. -David On Mon, Feb 3, 2014 at 1:17 PM, Karl Nordstrom north...@gmail.comwrote: I am attempting to generate a diff using rbt diff from a perforce workspace. I get the same error when I do rbt post. (Thank you for helping with the previous problem I was having, it appears to be resolved with RBTools 0.5.6.) My p4config is as follows: P4PORT=stork:1666 P4USER=knordstrom P4CLIENT=knordstrom_passenger The p4config appears to be setup correctly. I can do p4 diff from the commandline and generate a diff without errors. Unfortunately, this diff is not in a format that ReviewBoard understands. My .reviewboard rc file is as follows (just one line): REVIEWBOARD_URL = http://reviewboard/; I have tried the following on the commandline: rbt diff -d rbt diff -d 25012 (the latest changelist number) rbt post -d rbt post -d 25012 In all cases I get the same result: DEBUG:root:Checking for a Subversion repository... DEBUG:root:Checking for a Git repository... DEBUG:root:Checking for a Mercurial repository... DEBUG:root:Checking for a CVS repository... DEBUG:root:Checking for a Perforce repository... DEBUG:root:Running: p4 info DEBUG:root:Checking for a Plastic repository... DEBUG:root:Checking for a ClearCase repository... DEBUG:root:Checking for a Bazaar repository... ERROR:root:The current directory does not contain a checkout from a supported source code repository. When I do p4 info it provides relevant information. I'm hesitant to post it here as it shows company specific information. Is there something that I need to do in the configuration? Is this something to do with the way that Perforce works? As far as I can tell, Perforce works on workspaces (a collection of files that are being edited) rather than directories. That said, I would have thought that RBTools could find it via p4 diff, which references p4config. Ideally, I want to post to reviewboard based on changed files rather than an already committed changelist, but right now any solution would be welcome. Does anyone have an example of how to configure RBTools to work with Perforce? I have searched all over and have not found any concrete examples. Thanks, Karl -- Get the Review Board Power Pack at http://www.reviewboard.org/pow erpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- Get the Review Board Power Pack
Re: The current directory does not contain a checkout... (problem posting from perforce)
I'm seeing a couple issues with the perforce integration as well. The one above with the case mismatch, as well as the --p4-client parameter is not respected in RBTools 0.5.7. An integration with eclipse and reviewboard (https://code.google.com/p/p4reviewboard/) breaks because this parameter is not respected. On Saturday, 15 February 2014 20:03:45 UTC-5, David Trowbridge wrote: Greg, You're probably getting hit by case mismatches ( https://code.google.com/p/reviewboard/issues/detail?id=3221). We'll be fixing this for 0.5.8. -David On Wed, Feb 12, 2014 at 5:14 PM, Greg Dean gr...@familydean.netjavascript: wrote: Hi there, I've updated to 0.5.7 and I'm running from cygwin and I get the same result. Can rbt be run from cygwin? Here is what I get: $ rbt post -d -o 299074 DEBUG:root:Checking for a Subversion repository... DEBUG:root:Checking for a Git repository... DEBUG:root:Checking for a Mercurial repository... DEBUG:root:Checking for a CVS repository... DEBUG:root:Checking for a Perforce repository... DEBUG:root:Running: p4 info DEBUG:root:Checking for a Plastic repository... DEBUG:root:Checking for a ClearCase repository... DEBUG:root:Checking for a Bazaar repository... ERROR:root:The current directory does not contain a checkout from a supported source code repository. On Tuesday, February 4, 2014 1:14:16 PM UTC-8, Karl Nordstrom wrote: Thanks for the quick fix! 0.5.7 did it. Karl On Monday, 3 February 2014 13:50:03 UTC-8, Karl Nordstrom wrote: Okay, looking forward to getting the fix. Thanks, Karl On Monday, 3 February 2014 13:28:17 UTC-8, David Trowbridge wrote: Karl, It looks like we introduced a regression in 0.5.6 where it only will post from the client root. We'll get this sorted out asap. -David On Mon, Feb 3, 2014 at 1:17 PM, Karl Nordstrom north...@gmail.comwrote: I am attempting to generate a diff using rbt diff from a perforce workspace. I get the same error when I do rbt post. (Thank you for helping with the previous problem I was having, it appears to be resolved with RBTools 0.5.6.) My p4config is as follows: P4PORT=stork:1666 P4USER=knordstrom P4CLIENT=knordstrom_passenger The p4config appears to be setup correctly. I can do p4 diff from the commandline and generate a diff without errors. Unfortunately, this diff is not in a format that ReviewBoard understands. My .reviewboard rc file is as follows (just one line): REVIEWBOARD_URL = http://reviewboard/; I have tried the following on the commandline: rbt diff -d rbt diff -d 25012 (the latest changelist number) rbt post -d rbt post -d 25012 In all cases I get the same result: DEBUG:root:Checking for a Subversion repository... DEBUG:root:Checking for a Git repository... DEBUG:root:Checking for a Mercurial repository... DEBUG:root:Checking for a CVS repository... DEBUG:root:Checking for a Perforce repository... DEBUG:root:Running: p4 info DEBUG:root:Checking for a Plastic repository... DEBUG:root:Checking for a ClearCase repository... DEBUG:root:Checking for a Bazaar repository... ERROR:root:The current directory does not contain a checkout from a supported source code repository. When I do p4 info it provides relevant information. I'm hesitant to post it here as it shows company specific information. Is there something that I need to do in the configuration? Is this something to do with the way that Perforce works? As far as I can tell, Perforce works on workspaces (a collection of files that are being edited) rather than directories. That said, I would have thought that RBTools could find it via p4 diff, which references p4config. Ideally, I want to post to reviewboard based on changed files rather than an already committed changelist, but right now any solution would be welcome. Does anyone have an example of how to configure RBTools to work with Perforce? I have searched all over and have not found any concrete examples. Thanks, Karl -- 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/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...@googlegroups.com javascript:.
Re: RBTools 0.5.7 is released
Hi Christian, I saw the announcment yesterday concerning the release of the new version of RB Tools, however every time I run easy_install -U RBTools I only get 0.5.6 as the latest version. I looked in the directory: http://downloads.reviewboard.org/releases/RBTools/0.5/ and the latest version posted in there is: 0.5.6. Any idea why it is not there? On Monday, 3 February 2014 22:10:37 UTC-5, Christian Hammond wrote: Hi everyone, RBTools 0.5.7 is released. It's a very small bug fix release for Perforce, allowing commands to once again be run from within a subdirectory of a Perforce checkout. http://www.reviewboard.org/news/2014/02/03/rbtools-0-5-7-released/ We're working toward a 0.6 release, which will offer some major (but very nice) changes for working with revisions. If you're interested in giving it a try and giving us feedback, please check it out from our Git repository - https://github.com/reviewboard/rbtools/ Christian -- Christian Hammond - chri...@beanbaginc.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.
Javascript errors with Reviewboard 1.7.15
I installed Reviewboard 1.7.15 this morning, and I am getting the following errors on the edit review page. Uncaught SyntaxError: Use of future reserved word in strict mode 3rdparty.min.f0d3e37f248a.js:36 Uncaught ReferenceError: Backbone is not defined base.min.9651809ef5d5.js:1 Uncaught SyntaxError: Invalid regular expression: missing / /static/rb/js/reviews.min.d91b5b5b17e3.js:69 Uncaught ReferenceError: RB is not defined (index):529 As a result, when posting a new review, the review cannot be edited, published or discarded. -- 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.
P4PythonInstaller issue on Ubuntu 11.10
During the install of P4PythonInstaller on Ubuntu 11.10 I am getting the error Unsupported Linux version: 3.0.0-12-servererror: Setup script exited with 1 I used the command line sudo easy_isntall P4PythonInstaller which resulted in the output below: Searching for P4PythonInstaller Reading http://pypi.python.org/simple/P4PythonInstaller/ Reading http://www.review-board.org/ Best match: P4PythonInstaller 0.2 Downloading http://reviewboard.googlecode.com/svn/trunk/P4PythonInstaller#egg=P4 PythonInstaller-0.2 Doing subversion checkout from http://reviewboard.googlecode.com/svn/trunk/P4Pyt honInstaller to /tmp/easy_install-Bxskf8/P4PythonInstaller Processing P4PythonInstaller Running setup.py -q bdist_egg --dist-dir /tmp/easy_install-Bxskf8/ P4PythonInstal ler/egg-dist-tmp-c8b27G Unsupported Linux version: 3.0.0-12-servererror: Setup script exited with 1 Any idea what is causing the issue, and is there a workaround or fix? -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
