Re: Upgrading python versions?
Should I do a whole new install and migrate the DB? On Tue, Feb 28, 2012 at 2:43 PM, Tucker j...@gmail.com wrote: I decided to try and build pylucene again on CentOs 5.2. I kept running into problems with python2.4, so I built jcc against python2.6 (ActivePython). I eventually got it working (using openjdk-1.6 and a modern version of ant) but ReviewBoard doesn't seem to agree and I can't enable search. Since I built jcc with python2.6 and installed ReviewBoard using python2.4. this makes sense. Anyone have any suggestions on how to either cheat the enable search setting or upgrade the python version ReviewBoard is using? -- --tucker -- --tucker -- 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
Re: Upgrading python versions?
On Fri, Mar 2, 2012 at 10:58 AM, Tucker j...@gmail.com wrote: Should I do a whole new install and migrate the DB? On Tue, Feb 28, 2012 at 2:43 PM, Tucker j...@gmail.com wrote: I decided to try and build pylucene again on CentOs 5.2. I kept running into problems with python2.4, so I built jcc against python2.6 (ActivePython). I eventually got it working (using openjdk-1.6 and a modern version of ant) but ReviewBoard doesn't seem to agree and I can't enable search. Since I built jcc with python2.6 and installed ReviewBoard using python2.4. this makes sense. If you can migrate to CentOS 6 your life will be easier. If you have to stay with CentOS 5, you can't upgrade Python, as in you can't replace Python 2.4 (/usr/bin/python). You can install Python 2.6 in parallel. The EPEL http://fedoraproject.org/wiki/EPEL repository has a python26 package, and some dependencies you'll need like python26-distribute, python26-mysqldb, and python26-mod_wsgi. python26-distribute should provide a python26 specific version of pip/easy_install you can try to use to install Review Board. I've never tried it, but it's probably possible. Again, CentOS 6 is easier. -Anton -- 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
Any restriction in extension of file being uploaded to reviewboard
Hi, We are trying to check in the changes to perforce, but we see post-review got stuck, it happens for only one file with extention (.STEP) which is having headType as 'ctext', I would like to know if review board impose any restriction while posting the diff to review board for certain set of files. if yes then how could we solve this issue. if no what could be issue and where it got stuck. I can see reviewboard server has the file which has the *some random number.upload* (eg: tmpJq8GqG.upload ) file present in the /tmp/ which contain the files which is sent for review request. Please help on this its been urgent. Regards, Nilesh J -- 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
Re: Any restriction in extension of file being uploaded to reviewboard
Are you doing pre- or post-commit reviews? post-review will try to send diffs for all non-binary files. There's no way to exclude individual files except for temporarily removing them from the changelist. If your .STEP files are actually large binaries, I'd suggest changing the filetype in perforce. If they're large text files which have big diffs, and you're doing post-commit reviews, it's not a great situation. Reviewers probably won't be able to deal with looking at very large diffs (and it's a big load on the server). You could falsely mark the file as binary, but that might interfere with line ending conversion (if you use that). Otherwise, it's possible that an improvement to post-review could be made to try to drop very large diffs instead of posting them. - David On Mar 2, 2012, at 6:45 PM, Nilesh Jaiswal nileshj...@gmail.com wrote: Hi, We are trying to check in the changes to perforce, but we see post-review got stuck, it happens for only one file with extention (.STEP) which is having headType as 'ctext', I would like to know if review board impose any restriction while posting the diff to review board for certain set of files. if yes then how could we solve this issue. if no what could be issue and where it got stuck. I can see reviewboard server has the file which has the some random number.upload (eg: tmpJq8GqG.upload ) file present in the /tmp/ which contain the files which is sent for review request. Please help on this its been urgent. Regards, Nilesh J -- 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 -- 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
Re: Any restriction in extension of file being uploaded to reviewboard
Thanks David, While separately we are not doing any pre or post commit review its only the tool which post-review does that it. Yes the file is very large so what could be done here, are their any enhancement we need to do in our review board server or client to make this thing work. Please suggest. On Sat, Mar 3, 2012 at 10:03 AM, David Trowbridge trowb...@gmail.comwrote: Are you doing pre- or post-commit reviews? post-review will try to send diffs for all non-binary files. There's no way to exclude individual files except for temporarily removing them from the changelist. If your .STEP files are actually large binaries, I'd suggest changing the filetype in perforce. If they're large text files which have big diffs, and you're doing post-commit reviews, it's not a great situation. Reviewers probably won't be able to deal with looking at very large diffs (and it's a big load on the server). You could falsely mark the file as binary, but that might interfere with line ending conversion (if you use that). Otherwise, it's possible that an improvement to post-review could be made to try to drop very large diffs instead of posting them. - David On Mar 2, 2012, at 6:45 PM, Nilesh Jaiswal nileshj...@gmail.com wrote: Hi, We are trying to check in the changes to perforce, but we see post-review got stuck, it happens for only one file with extention (.STEP) which is having headType as 'ctext', I would like to know if review board impose any restriction while posting the diff to review board for certain set of files. if yes then how could we solve this issue. if no what could be issue and where it got stuck. I can see reviewboard server has the file which has the *some random number.upload* (eg: tmpJq8GqG.upload ) file present in the /tmp/ which contain the files which is sent for review request. Please help on this its been urgent. Regards, Nilesh J -- 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 -- 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 -- 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
Re: Any restriction in extension of file being uploaded to reviewboard
As I said, there are a few approaches. Ordered in terms of simplicity: - Mark the file as binary in perforce. - Tell users to remove the file from their changelist during review (it's not possible for people to review megabytes of text, and reviewing things which are automatically generated generally isn't useful anyway). - Make an improvement to post-review to avoid including any file diffs which are very large. - David On Mar 2, 2012, at 8:44 PM, Nilesh Jaiswal nileshj...@gmail.com wrote: Thanks David, While separately we are not doing any pre or post commit review its only the tool which post-review does that it. Yes the file is very large so what could be done here, are their any enhancement we need to do in our review board server or client to make this thing work. Please suggest. On Sat, Mar 3, 2012 at 10:03 AM, David Trowbridge trowb...@gmail.com wrote: Are you doing pre- or post-commit reviews? post-review will try to send diffs for all non-binary files. There's no way to exclude individual files except for temporarily removing them from the changelist. If your .STEP files are actually large binaries, I'd suggest changing the filetype in perforce. If they're large text files which have big diffs, and you're doing post-commit reviews, it's not a great situation. Reviewers probably won't be able to deal with looking at very large diffs (and it's a big load on the server). You could falsely mark the file as binary, but that might interfere with line ending conversion (if you use that). Otherwise, it's possible that an improvement to post-review could be made to try to drop very large diffs instead of posting them. - David On Mar 2, 2012, at 6:45 PM, Nilesh Jaiswal nileshj...@gmail.com wrote: Hi, We are trying to check in the changes to perforce, but we see post-review got stuck, it happens for only one file with extention (.STEP) which is having headType as 'ctext', I would like to know if review board impose any restriction while posting the diff to review board for certain set of files. if yes then how could we solve this issue. if no what could be issue and where it got stuck. I can see reviewboard server has the file which has the some random number.upload (eg: tmpJq8GqG.upload ) file present in the /tmp/ which contain the files which is sent for review request. Please help on this its been urgent. Regards, Nilesh J -- 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 -- 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 -- 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 -- 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
Re: Is it possible to install ReviewBoard without sudo?
Thanks, I got some response from TM, they said I need to buy some service for a dedicated server. On Wed, Feb 29, 2012 at 11:01 PM, Stephen Gallagher step...@gallagherhome.com wrote: On Tue, 2012-02-28 at 23:59 -0800, David Trowbridge wrote: I won't rule it out entirely because I haven't tried, but I think it's pretty unlikely that you'll be able to install and configure everything that you need. Strictly speaking, you could install your own private Python installation in your home directory, as well as your own private HTTPD (running on a non-privileged port), but you're talking about a MUCH more complicated setup than any sane person would want to do. (As an aside, this IS how openshift sets up ReviewBoard instances in the cloud, but it's carefully scripted) -- 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 -- 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
Re: Upgrading python versions?
On Fri, Mar 2, 2012 at 2:38 PM, Anton Cohen an...@antoncohen.com wrote: On Fri, Mar 2, 2012 at 10:58 AM, Tucker j...@gmail.com wrote: Should I do a whole new install and migrate the DB? On Tue, Feb 28, 2012 at 2:43 PM, Tucker j...@gmail.com wrote: I decided to try and build pylucene again on CentOs 5.2. I kept running into problems with python2.4, so I built jcc against python2.6 (ActivePython). I eventually got it working (using openjdk-1.6 and a modern version of ant) but ReviewBoard doesn't seem to agree and I can't enable search. Since I built jcc with python2.6 and installed ReviewBoard using python2.4. this makes sense. If you can migrate to CentOS 6 your life will be easier. If you have to stay with CentOS 5, you can't upgrade Python, as in you can't replace Python 2.4 (/usr/bin/python). You can install Python 2.6 in parallel. The EPEL http://fedoraproject.org/wiki/EPEL repository has a python26 package, and some dependencies you'll need like python26-distribute, python26-mysqldb, and python26-mod_wsgi. python26-distribute should provide a python26 specific version of pip/easy_install you can try to use to install Review Board. I've never tried it, but it's probably possible. Again, CentOS 6 is easier. -Anton This is an important point. We'll make a more formal announcement in time, but the next version of Review Board will not be compatible with Python 2.4. So it's best to get a 2.6 or 2.7 setup if at all possible. Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com -- 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
Re: Issue 2510 in reviewboard: full names instead of logins in People: field
Comment #1 on issue 2510 by yakov.sh...@gmail.com: full names instead of logins in People: field http://code.google.com/p/reviewboard/issues/detail?id=2510 small qualification: we use LDAP auth in our RB installation, if it matters. -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
Re: Issue 2512 in reviewboard: Modify review fields persmissions
Comment #7 on issue 2512 by trowb...@gmail.com: Modify review fields persmissions http://code.google.com/p/reviewboard/issues/detail?id=2512 I'm sorry, I meant the admin role. -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
