Re: Review Board 1.0.3 released
Yes, I realized this after I posted. I had accidentally pulled in a nightly build at one point due to my .pydistutils.cfg, but I had since downgraded to 1.0.1. Is there any way to get rid of the issue, or am I stuck with the warning forever? :) Dan On Sep 17, 3:44 pm, Christian Hammond chip...@chipx86.com wrote: Hi Dan, Were you at any point running a 1.1 nightly or out of a Git tree? This is a field introduced in the 1.1 branch, so I don't know why you would see this in 1.0.x. It doesn't appear that the 1.0.x releases mention this at all in the codebase. If you went from a 1.1 to a 1.0.3, then you would definitely hit this error, as the field would be introduced and then removed without an evolution rule. Christian -- Christian Hammond - chip...@chipx86.com Review Board -http://www.review-board.org VMware, Inc. -http://www.vmware.com On Thu, Sep 17, 2009 at 8:52 AM, Dan Savilonis d...@n-cube.org wrote: I got the following error during the evolution: # rb-site upgrade /home/reviewboard_head Rebuilding directory structure Updating database. This may take a while. There are unapplied evolutions for diffviewer. Project signature has changed - an evolution is required /usr/lib/python2.5/site-packages/ReviewBoard-1.0.3-py2.5.egg/ reviewboard/scmtools/bzr.py:6: ImportWarning: Not importing directory '/usr/lib/python2.5/site-packages/bzrlib': missing __init__.py from bzrlib import bzrdir, revisionspec The stored evolutions do not completely resolve all model changes. Run `./manage.py evolve --hint` to see a suggestion for the changes required. The following are the changes that could not be resolved: In model scmtools.Repository: Field 'raw_file_url' has been deleted It appears to be working okay, though. Other thing I noticed is that the admin dashboard has CSS applied but appears very basic and has no images. Other pages look okay, and the same as they used to. Dan On Sep 16, 8:38 pm, Christian Hammond chip...@chipx86.com wrote: Last night's 1.0.2 release was pretty broken in two major ways. The web server configuration templates were no longer bundled in the package, due to a change in the structure of our code tree, and users using Django 1.0.2 would hit a bug, as we needed functionality only present in 1.0.3 and higher. The new 1.0.3 release should address these problems. If you've been bitten by 1.0.2 (our deepest apologies), please give this release a try and let us know how it works. Full release notes are available athttp:// www.review-board.org/docs/releasenotes/dev/reviewboard/1.0.3/ Christian -- Christian Hammond - chip...@chipx86.com Review Board -http://www.review-board.org VMware, Inc. -http://www.vmware.com --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups reviewboard group. To post to this group, send email to reviewboard@googlegroups.com 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 -~--~~~~--~~--~--~---
Issue 1320 in reviewboard: Auto-added names cause exceptions.
Updates: Status: Confirmed Labels: Milestone-Release1.0.x Component-Reviews Comment #1 on issue 1320 by chipx86: Auto-added names cause exceptions. http://code.google.com/p/reviewboard/issues/detail?id=1320 (No comment was entered for this change.) -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Issue 1321 in reviewboard: post-review fails when submitting a Perforce CLN that includes a symlink to a symlink.
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 1321 by josh.hamacher: post-review fails when submitting a Perforce CLN that includes a symlink to a symlink. http://code.google.com/p/reviewboard/issues/detail?id=1321 *NOTE: Do not post confidential information in this bug report.* What version are you running? 1.0 What's the URL of the page containing the problem? None - this is an issue with post-review. What steps will reproduce the problem? 1. Find an existing symlink (A) somewhere on your system. 2. Inside a Perforce client view, create a symlink (B) to A. 3. Create a changelist. 4. p4 add -c XXX B 5. Run post-review XXX. What is the expected output? What do you see instead? We see this: Traceback (most recent call last): File /apollo/env/SDETools/share/rbtools/scripts/post-review, line 2348, in module main(sys.argv[1:]) File /apollo/env/SDETools/share/rbtools/scripts/post-review, line 2294, in main diff, parent_diff = tool.diff(args) File /apollo/env/SDETools/share/rbtools/scripts/post-review, line 1473, in diff m = re.search(r'(\d\d\d\d-\d\d-\d\d \d\d:\d\d:\d\d)', dl[1]) IndexError: list index out of range Symlinks to files and directories seem to work, so I'd expect symlinks to symlinks to work the same. What operating system are you using? What browser? Red Hat Enterprise Linux 5.3 on the server. Post-review is running under Red Hat Enterprise Linux 3. Please provide any additional information below. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Issue 1322 in reviewboard: Post-review is ignorant of many files brought in via svn merge.
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 1322 by josh.hamacher: Post-review is ignorant of many files brought in via svn merge. http://code.google.com/p/reviewboard/issues/detail?id=1322 *NOTE: Do not post confidential information in this bug report.* What version are you running? 1.0 What's the URL of the page containing the problem? None; this is a post-review problem. What steps will reproduce the problem? 1. Use 'svn merge' to bring in changes from a different branch to the working copy. In this case, the other branch should have had many files added compared to the working copy. 2. Run 'svn status' and see how many files are opened. 3. Run 'svn diff' and see a significantly smaller number of files. 4. Since post-review only uses the output of 'svn diff', many files don't appear as part of the review. What is the expected output? What do you see instead? 'svn diff' (and therefore post-review) only picks up files that have changed due to the merge; it seems to skip over files that are created locally. Since the addition of files is a significant change to a code tree, I'd argue that all of the new files should be visible for review (even if they were reviewed earlier in their original location). What operating system are you using? What browser? Shouldn't matter, but I have Red Hat Enterprise Linux 3 on my workstation. Please provide any additional information below. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
