Re: Failed to upgrade from 1.7.12 to 1.7.28 and 2.x

2015-12-11 Thread Kevin Yin 
Turned out I have django_evolution version updated somehow. Rolling back to 
the previous version worked.

On Tuesday, December 8, 2015 at 4:42:50 PM UTC-8, Kevin Yin wrote:
>
> So I got this reviewboard 1.7.12 server assigned to me. We have the need 
> for some new features from newer versions of reviewboard. So I simply did 
> easy_install -U ReviewBoard and rb-site upgrade. It failed. I did not have 
> a recent backup, but luckily rolling back the ReviewBoard python package 
> version worked. So I read a bunch of discussions here. I decided to upgrade 
> to 1.7.28 first. But it fails too, with following error same as 
> https://groups.google.com/forum/#!searchin/reviewboard/Downgrading$20Reviewboard$202.0RC2%7Csort:relevance/reviewboard/pxQ3eyYPhzE/PxEj_0_Oi9YJ
> :
>
> --  --
> Creating tables ...
>
> [!] Unable to execute the manager command syncdb: No module named
> db.fields
>
> [!] Unable to execute the manager command evolve: No module named
> db.fields
> ---  ---
>
> So I compared some schema and content, figured out it is from 
> reviewboard.django_project_version. Then I took dumpdb this time, and 
> deleted the last record of reviewboard.django_project_version, retried 
> upgrading, it now fails with
>
>
> -  --
> Creating tables ...
> Upgrading Review Board from 1.7.12 to 1.7.28
> There are unapplied evolutions for accounts.
> There are unapplied evolutions for attachments.
> There are unapplied evolutions for diffviewer.
> There are unapplied evolutions for site.
> Project signature has changed - an evolution is required
> Installing custom SQL ...
> Installing indexes ...
> Installed 0 object(s) from 0 fixture(s)
> 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 attachments.FileAttachment:
> Field 'orig_filename' has been added
> In model hostingsvcs.HostingServiceAccount:
> Field 'hosting_url' has been added
> The model auth.Message has been deleted
> In model reviews.FileAttachmentComment:
> Field 'extra_data' has been added
> In model reviews.ReviewRequest:
> Field 'last_review_activity_timestamp' has been added
> Field 'depends_on' has been added
> Field 'last_review_timestamp' has been deleted
> In model reviews.ReviewRequestDraft:
> Field 'depends_on' has been added
> In model accounts.Profile:
> Field 'timezone' has been added
> Field 'open_an_issue' has been added
> Field 'extra_data' has been added
> In model diffviewer.DiffSetHistory:
> Field 'last_diff_updated' has been added
> In model diffviewer.FileDiff:
> Field 'diff_hash' has been added
> Field 'parent_diff_hash' has been added
> Field 'diff64' has been added
> Field 'parent_diff64' has been added
> Field 'parent_diff' has been deleted
> Field 'diff' has been deleted
> Error: Your models contain changes that Django Evolution cannot resolve 
> automatically.
>
> How can I proceed? I have a backup before this happens (quite old so not 
> possible to load back).
>

-- 
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: member of the review group wont get emails unless they are in mailing list

2015-12-11 Thread David Trowbridge 
Sam,

It looks like we had an issue that was preventing the field from showing up
in the admin UI. We'll get this fixed up for 2.5.3.

-David

On Thu, Dec 10, 2015 at 8:59 AM Sam  wrote:

> Thank you David for your response.
>
> We have groups that people are members and these groups are being used for
> review.
>
> I have Reviewboard 2.5.1.1. Can you please guide me how to set for the
> option to send email to member of the groups since I have hard time to find
> the option.
>
> --
> 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 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: Upgrade from 1.6.22 to 2.5.2 fails, using PostgreSQL / Ubuntu 12.04.4

2015-12-11 Thread Jukka Akkanen 
I am hitting the same problem when upgrading 1.6.14 to 2.5.2 using MySQL. 

Something I tried was, create a new, empty database with syncdb on 1.6.14 
and try upgrading to 2.5.2, and that fails as well. Is this a valid test or 
am I missing something?

-Jukka

On Tuesday, 8 December 2015 17:09:05 UTC-5, Christian Hammond wrote:
>
> Hi Oliver,
>
> This is definitely a different problem than the ones you found, but it is 
> strange.. The stored schema should have had some state in there for the new 
> FileDiffData table, but it's not there I guess.
>
> Can you send me a dump of the schema of your database (no content), and a 
> second dump containing the content of your django_project_version and 
> django_evolution tables?
>
> Christian
>
> -- 
> Christian Hammond - chri...@beanbaginc.com 
> Review Board - https://www.reviewboard.org
> Beanbag, Inc. - https://www.beanbaginc.com
>
> On Tue, Dec 8, 2015 at 10:15 AM, Oliver Fasterling  > wrote:
>
> I attempted to upgrade our Reviewboard 1.6.22 to 2.5.2 (latest version). I 
> followed the steps documented in the upgrade guide, but failed with some 
> errors.
>
> I searched the mailing lists and found two articles which seem to match 
> the errors that I am getting. 
>
> https://goo.gl/VSbjds
>
> https://goo.gl/EpoghP
>
> The first article seems to isolate the culprit as a discrepancy of the 
> engine type found on MySQL tables, where there is a mix of MyISAM and 
> InnoDB types. Normalizing these to a single type fixed the issue. Found a 
> few other articles with that suggest the same fix. However, we use 
> PostgresSQL. From my understanding, there is a single engine type in 
> postgresql, and so the fix above does not apply.
>
> The second article talks about a bug in the Django Evolution package. I 
> ran the update command, but it was a moot action since it had already 
> downloaded the most recent version during the full upgrade.
>
> I considered running an upgrade to an earlier version, like 2.0.x but then 
> I found more articles where the upgrade also fails for them.
>
> Any assistance would be much appreciated.
>
> The output of my upgrade is shown below.
>
>
> root@reviewboard:~# easy_install -U ReviewBoard
> Searching for ReviewBoard
> Reading http://pypi.python.org/simple/ReviewBoard/
> Best match: ReviewBoard 2.5.2
> Downloading https://
> pypi.python.org/packages/2.7/R/ReviewBoard/ReviewBoard-2.5.2-py2.7.egg#md5=58b2dbe01761a1f3d398381130e75d26
> Processing ReviewBoard-2.5.2-py2.7.egg
> creating /usr/local/lib/python2.7/dist-packages/ReviewBoard-2.5.2-py2.
> 7.egg
> Extracting ReviewBoard-2.5.2-py2.7.egg to /usr/local/lib/python2.7/dist-
> packages
> Removing ReviewBoard 1.6.22.dev from easy-install.pth file
> Adding ReviewBoard 2.5.2 to easy-install.pth file
> Installing rbssh script to /usr/local/bin
> Installing rb-site script to /usr/local/bin
>
>
> Installed /usr/local/lib/python2.7/dist-packages/ReviewBoard-2.5.2-py2.
> 7.egg
> Reading http://downloads.reviewboard.org/mirror/
> Reading http://downloads.reviewboard.org/releases/Djblets/0.9/
> Reading http://downloads.reviewboard.org/releases/django-evolution/0.7/
> Processing dependencies for ReviewBoard
> Searching for Whoosh>=2.6
> Reading http://pypi.python.org/simple/Whoosh/
> Best match: Whoosh 2.7.0
> Downloading https://
> pypi.python.org/packages/source/W/Whoosh/Whoosh-2.7.0.zip#md5=7abfd970f16fadc7311960f3fa0bc7a9
> Processing Whoosh-2.7.0.zip
> Running Whoosh-2.7.0/setup.py -q bdist_egg --dist-dir /tmp/easy_install-
> 0wY0qe/Whoosh-2.7.0/egg-dist-tmp-yeD4wW
> warning: no files found matching '*.txt' under directory 'tests'
> warning: no files found matching '*.txt' under directory 'benchmark'
> warning: no files found matching '*.txt' under directory 'docs'
> warning: no files found matching '*.txt' under directory 'files'
> warning: no files found matching '*.py' under directory 'files'
> warning: no files found matching '*.jpg' under directory 'files'
> Adding Whoosh 2.7.0 to easy-install.pth file
>
>
> Installed /usr/local/lib/python2.7/dist-packages/Whoosh-2.7.0-py2.7.egg
> Searching for Pygments>=1.6
> Reading http://pypi.python.org/simple/Pygments/
> Best match: Pygments 2.0.2
> Downloading https://
> pypi.python.org/packages/source/P/Pygments/Pygments-2.0.2.tar.gz#md5=238587a1370d62405edabd0794b3ec4a
> Processing Pygments-2.0.2.tar.gz
> Running Pygments-2.0.2/setup.py -q bdist_egg --dist-dir /tmp/easy_install-
> MT7Fm3/Pygments-2.0.2/egg-dist-tmp-WGJV2n
> Removing Pygments 1.5 from easy-install.pth file
> Adding Pygments 2.0.2 to easy-install.pth file
> Installing pygmentize script to /usr/local/bin
>
>
> Installed /usr/local/lib/python2.7/dist-packages/Pygments-2.0.2-py2.7.egg
> Searching for pycrypto>=2.6
> Reading http://pypi.python.org/simple/pycrypto/
> Best match: pycrypto 2.6.1
> Downloading https://
> pypi.python.org/packages/source/p/pycrypto/pycrypto-2.6.1.tar.gz#md5=55a61a054aa66812daf5161a0d5d7eda
> Processing pycrypto-2.6.1.tar.gz
>