Re: Upgrade issues upgrading from 3.0.20 to 3.0.22
I'm glad to hear it! Thanks for letting me know :) Sorry for the trouble before. Christian On Thu, May 6, 2021 at 10:42 AM tw bert wrote: > Hi Christian, thank you, that worked flawlessly. > We considered pip installing bleach, but like to keep stuff vanilla where > possible. > Fixed. > For completeness, I've attached the output logs of pip install -U > ReviewBoard==3.0.23 and the rb-site upgrade. > > > On Thursday, 6 May 2021 at 03:16:10 UTC+2 Christian Hammond wrote: > >> Just put out the 3.0.23 release, so you should be able to upgrade and be >> good. Sorry about that. There was a lingering but unnecessary usage of a >> dependency that we had removed in 3.0.22. >> >> Christian >> >> On Wed, May 5, 2021 at 5:58 PM Christian Hammond >> wrote: >> >>> Hi, >>> >>> Looks like something went wrong with the release. You can get around >>> this temporarily by doing: >>> >>> pip install bleach_allowlist >>> >>> We'll put out a fixed build tonight. >>> >>> Christian >>> >>> >>> On Wed, May 5, 2021 at 8:42 AM tw bert wrote: >>> RB breaks when upgrading, we reverted to backup. Any clue? Previous upgrades always went fine. pip install -U ReviewBoard==3.0.22 (ok) root@srv-flux-dev-01:/# rb-site upgrade /var/www/reviews.XXX.XXX.com WARNING:py.warnings:/usr/local/lib/python2.7/dist-packages/paramiko/transport.py:33: CryptographyDeprecationWarning: Python 2 is no longer supported by the Python core team. Support for it is now deprecated in cryptography, and will be removed in the next release. from cryptography.hazmat.backends import default_backend Rebuilding directory structure Updating database. This may take a while. The log output below, including warnings and errors, can be ignored unless upgrade fails. -- -- [!] Unable to execute the manager command syncdb: cannot import name signals [!] Unable to execute the manager command registerscmtools: cannot import name signals [!] Unable to execute the manager command evolve: cannot import name signals --- --- Resetting in-database caches. [!] Unable to execute the manager command fixreviewcounts: No module named bleach_allowlist Upgrade complete! There are duplicate copies of diffs in your database that can be condensed. These are the result of posting several iterations of a change for review on older versions of Review Board. Removing duplicate diff data will save space in your database and speed up future upgrades. To condense duplicate diffs, type the following: $ rb-site manage /var/www/reviews.XXX.XXX.com condensediffs root@srv-flux-dev-01:/# tail -n30 /var/log/apache2/error.log [Wed May 05 08:20:37.853326 2021] [wsgi:error] [pid 5063:tid 139949663827712] [client 192.168.4.87:53160] self.load_middleware(), referer: http://srv-reviewboard:8089/dashboard/ [Wed May 05 08:20:37.853350 2021] [wsgi:error] [pid 5063:tid 139949663827712] [client 192.168.4.87:53160] File "/usr/local/lib/python2.7/dist-packages/django/core/handlers/base.py", line 45, in load_middleware, referer: http://srv-reviewboard:8089/dashboard/ [Wed May 05 08:20:37.853385 2021] [wsgi:error] [pid 5063:tid 139949663827712] [client 192.168.4.87:53160] mw_class = import_by_path(middleware_path), referer: http://srv-reviewboard:8089/dashboard/ [Wed May 05 08:20:37.853406 2021] [wsgi:error] [pid 5063:tid 139949663827712] [client 192.168.4.87:53160] File "/usr/local/lib/python2.7/dist-packages/django/utils/module_loading.py", line 26, in import_by_path, referer: http://srv-reviewboard:8089/dashboard/ [Wed May 05 08:20:37.853438 2021] [wsgi:error] [pid 5063:tid 139949663827712] [client 192.168.4.87:53160] sys.exc_info()[2]), referer: http://srv-reviewboard:8089/dashboard/ [Wed May 05 08:20:37.853458 2021] [wsgi:error] [pid 5063:tid 139949663827712] [client 192.168.4.87:53160] File "/usr/local/lib/python2.7/dist-packages/django/utils/module_loading.py", line 21, in import_by_path, referer: http://srv-reviewboard:8089/dashboard/ [Wed May 05 08:20:37.853504 2021] [wsgi:error] [pid 5063:tid 139949663827712] [client 192.168.4.87:53160] module = import_module(module_path), referer: http://srv-reviewboard:8089/dashboard/ [Wed May 05 08:20:37.853525 2021] [wsgi:error] [pid 5063:tid 139949663827712] [client 192.168.4.87:53160] File "/usr/local/lib/python2.7/dist-packages/django/utils/importlib.py", line 40, in import_module, referer: http://srv-reviewboard:8089/dashboard/ [Wed May 05 08:20:37.853556 2021] [wsgi:error] [pid 5063:tid 139949663827712]
Re: Upgrade issues upgrading from 3.0.20 to 3.0.22
Hi Christian, thank you, that worked flawlessly. We considered pip installing bleach, but like to keep stuff vanilla where possible. Fixed. For completeness, I've attached the output logs of pip install -U ReviewBoard==3.0.23 and the rb-site upgrade. On Thursday, 6 May 2021 at 03:16:10 UTC+2 Christian Hammond wrote: > Just put out the 3.0.23 release, so you should be able to upgrade and be > good. Sorry about that. There was a lingering but unnecessary usage of a > dependency that we had removed in 3.0.22. > > Christian > > On Wed, May 5, 2021 at 5:58 PM Christian Hammond > wrote: > >> Hi, >> >> Looks like something went wrong with the release. You can get around this >> temporarily by doing: >> >> pip install bleach_allowlist >> >> We'll put out a fixed build tonight. >> >> Christian >> >> >> On Wed, May 5, 2021 at 8:42 AM tw bert wrote: >> >>> RB breaks when upgrading, we reverted to backup. >>> >>> Any clue? Previous upgrades always went fine. >>> >>> pip install -U ReviewBoard==3.0.22 >>> >>> (ok) >>> >>> root@srv-flux-dev-01:/# rb-site upgrade /var/www/reviews.XXX.XXX.com >>> WARNING:py.warnings:/usr/local/lib/python2.7/dist-packages/paramiko/transport.py:33: >>> >>> CryptographyDeprecationWarning: Python 2 is no longer supported by the >>> Python core team. Support for it is now deprecated in cryptography, and >>> will be removed in the next release. >>> from cryptography.hazmat.backends import default_backend >>> >>> Rebuilding directory structure >>> Updating database. This may take a while. >>> >>> The log output below, including warnings and errors, >>> can be ignored unless upgrade fails. >>> >>> -- -- >>> >>> [!] Unable to execute the manager command syncdb: cannot import name >>> signals >>> >>> [!] Unable to execute the manager command registerscmtools: cannot >>> import name signals >>> >>> [!] Unable to execute the manager command evolve: cannot import name >>> signals >>> --- --- >>> >>> Resetting in-database caches. >>> >>> [!] Unable to execute the manager command fixreviewcounts: No module >>> named bleach_allowlist >>> >>> Upgrade complete! >>> >>> There are duplicate copies of diffs in your database that can be >>> condensed. >>> These are the result of posting several iterations of a change for >>> review on >>> older versions of Review Board. >>> >>> Removing duplicate diff data will save space in your database and speed >>> up >>> future upgrades. >>> >>> To condense duplicate diffs, type the following: >>> >>> $ rb-site manage /var/www/reviews.XXX.XXX.com condensediffs >>> >>> >>> root@srv-flux-dev-01:/# tail -n30 /var/log/apache2/error.log >>> [Wed May 05 08:20:37.853326 2021] [wsgi:error] [pid 5063:tid >>> 139949663827712] [client 192.168.4.87:53160] >>> self.load_middleware(), referer: http://srv-reviewboard:8089/dashboard/ >>> [Wed May 05 08:20:37.853350 2021] [wsgi:error] [pid 5063:tid >>> 139949663827712] [client 192.168.4.87:53160] File >>> "/usr/local/lib/python2.7/dist-packages/django/core/handlers/base.py", line >>> 45, in load_middleware, referer: http://srv-reviewboard:8089/dashboard/ >>> [Wed May 05 08:20:37.853385 2021] [wsgi:error] [pid 5063:tid >>> 139949663827712] [client 192.168.4.87:53160] mw_class = >>> import_by_path(middleware_path), referer: >>> http://srv-reviewboard:8089/dashboard/ >>> [Wed May 05 08:20:37.853406 2021] [wsgi:error] [pid 5063:tid >>> 139949663827712] [client 192.168.4.87:53160] File >>> "/usr/local/lib/python2.7/dist-packages/django/utils/module_loading.py", >>> line 26, in import_by_path, referer: >>> http://srv-reviewboard:8089/dashboard/ >>> [Wed May 05 08:20:37.853438 2021] [wsgi:error] [pid 5063:tid >>> 139949663827712] [client 192.168.4.87:53160] sys.exc_info()[2]), >>> referer: http://srv-reviewboard:8089/dashboard/ >>> [Wed May 05 08:20:37.853458 2021] [wsgi:error] [pid 5063:tid >>> 139949663827712] [client 192.168.4.87:53160] File >>> "/usr/local/lib/python2.7/dist-packages/django/utils/module_loading.py", >>> line 21, in import_by_path, referer: >>> http://srv-reviewboard:8089/dashboard/ >>> [Wed May 05 08:20:37.853504 2021] [wsgi:error] [pid 5063:tid >>> 139949663827712] [client 192.168.4.87:53160] module = >>> import_module(module_path), referer: >>> http://srv-reviewboard:8089/dashboard/ >>> [Wed May 05 08:20:37.853525 2021] [wsgi:error] [pid 5063:tid >>> 139949663827712] [client 192.168.4.87:53160] File >>> "/usr/local/lib/python2.7/dist-packages/django/utils/importlib.py", line >>> 40, in import_module, referer: http://srv-reviewboard:8089/dashboard/ >>> [Wed May 05 08:20:37.853556 2021] [wsgi:error] [pid 5063:tid >>> 139949663827712] [client 192.168.4.87:53160] __import__(name), >>> referer: http://srv-reviewboard:8089/dashboard/ >>> [Wed May 05 08:20:37.853575 2021] [wsgi:error] [pid 5063:tid >>> 139949663827712] [client 192.168.4.87:53160] File >>>
Re: Upgrade issues upgrading from 3.0.20 to 3.0.22
Just put out the 3.0.23 release, so you should be able to upgrade and be good. Sorry about that. There was a lingering but unnecessary usage of a dependency that we had removed in 3.0.22. Christian On Wed, May 5, 2021 at 5:58 PM Christian Hammond wrote: > Hi, > > Looks like something went wrong with the release. You can get around this > temporarily by doing: > > pip install bleach_allowlist > > We'll put out a fixed build tonight. > > Christian > > > On Wed, May 5, 2021 at 8:42 AM tw bert wrote: > >> RB breaks when upgrading, we reverted to backup. >> >> Any clue? Previous upgrades always went fine. >> >> pip install -U ReviewBoard==3.0.22 >> >> (ok) >> >> root@srv-flux-dev-01:/# rb-site upgrade /var/www/reviews.XXX.XXX.com >> WARNING:py.warnings:/usr/local/lib/python2.7/dist-packages/paramiko/transport.py:33: >> CryptographyDeprecationWarning: Python 2 is no longer supported by the >> Python core team. Support for it is now deprecated in cryptography, and >> will be removed in the next release. >> from cryptography.hazmat.backends import default_backend >> >> Rebuilding directory structure >> Updating database. This may take a while. >> >> The log output below, including warnings and errors, >> can be ignored unless upgrade fails. >> >> -- -- >> >> [!] Unable to execute the manager command syncdb: cannot import name >> signals >> >> [!] Unable to execute the manager command registerscmtools: cannot >> import name signals >> >> [!] Unable to execute the manager command evolve: cannot import name >> signals >> --- --- >> >> Resetting in-database caches. >> >> [!] Unable to execute the manager command fixreviewcounts: No module >> named bleach_allowlist >> >> Upgrade complete! >> >> There are duplicate copies of diffs in your database that can be >> condensed. >> These are the result of posting several iterations of a change for review >> on >> older versions of Review Board. >> >> Removing duplicate diff data will save space in your database and speed up >> future upgrades. >> >> To condense duplicate diffs, type the following: >> >> $ rb-site manage /var/www/reviews.XXX.XXX.com condensediffs >> >> >> root@srv-flux-dev-01:/# tail -n30 /var/log/apache2/error.log >> [Wed May 05 08:20:37.853326 2021] [wsgi:error] [pid 5063:tid >> 139949663827712] [client 192.168.4.87:53160] self.load_middleware(), >> referer: http://srv-reviewboard:8089/dashboard/ >> [Wed May 05 08:20:37.853350 2021] [wsgi:error] [pid 5063:tid >> 139949663827712] [client 192.168.4.87:53160] File >> "/usr/local/lib/python2.7/dist-packages/django/core/handlers/base.py", line >> 45, in load_middleware, referer: http://srv-reviewboard:8089/dashboard/ >> [Wed May 05 08:20:37.853385 2021] [wsgi:error] [pid 5063:tid >> 139949663827712] [client 192.168.4.87:53160] mw_class = >> import_by_path(middleware_path), referer: >> http://srv-reviewboard:8089/dashboard/ >> [Wed May 05 08:20:37.853406 2021] [wsgi:error] [pid 5063:tid >> 139949663827712] [client 192.168.4.87:53160] File >> "/usr/local/lib/python2.7/dist-packages/django/utils/module_loading.py", >> line 26, in import_by_path, referer: >> http://srv-reviewboard:8089/dashboard/ >> [Wed May 05 08:20:37.853438 2021] [wsgi:error] [pid 5063:tid >> 139949663827712] [client 192.168.4.87:53160] sys.exc_info()[2]), >> referer: http://srv-reviewboard:8089/dashboard/ >> [Wed May 05 08:20:37.853458 2021] [wsgi:error] [pid 5063:tid >> 139949663827712] [client 192.168.4.87:53160] File >> "/usr/local/lib/python2.7/dist-packages/django/utils/module_loading.py", >> line 21, in import_by_path, referer: >> http://srv-reviewboard:8089/dashboard/ >> [Wed May 05 08:20:37.853504 2021] [wsgi:error] [pid 5063:tid >> 139949663827712] [client 192.168.4.87:53160] module = >> import_module(module_path), referer: >> http://srv-reviewboard:8089/dashboard/ >> [Wed May 05 08:20:37.853525 2021] [wsgi:error] [pid 5063:tid >> 139949663827712] [client 192.168.4.87:53160] File >> "/usr/local/lib/python2.7/dist-packages/django/utils/importlib.py", line >> 40, in import_module, referer: http://srv-reviewboard:8089/dashboard/ >> [Wed May 05 08:20:37.853556 2021] [wsgi:error] [pid 5063:tid >> 139949663827712] [client 192.168.4.87:53160] __import__(name), >> referer: http://srv-reviewboard:8089/dashboard/ >> [Wed May 05 08:20:37.853575 2021] [wsgi:error] [pid 5063:tid >> 139949663827712] [client 192.168.4.87:53160] File >> "/usr/local/lib/python2.7/dist-packages/reviewboard/admin/middleware.py", >> line 9, in , referer: http://srv-reviewboard:8089/dashboard/ >> [Wed May 05 08:20:37.853621 2021] [wsgi:error] [pid 5063:tid >> 139949663827712] [client 192.168.4.87:53160] from >> reviewboard.accounts.backends.registry import get_enabled_auth_backends, >> referer: http://srv-reviewboard:8089/dashboard/ >> [Wed May 05 08:20:37.853653 2021] [wsgi:error] [pid 5063:tid >> 139949663827712] [client 192.168.4.87:53160]
Re: Upgrade issues upgrading from 3.0.20 to 3.0.22
Hi, Looks like something went wrong with the release. You can get around this temporarily by doing: pip install bleach_allowlist We'll put out a fixed build tonight. Christian On Wed, May 5, 2021 at 8:42 AM tw bert wrote: > RB breaks when upgrading, we reverted to backup. > > Any clue? Previous upgrades always went fine. > > pip install -U ReviewBoard==3.0.22 > > (ok) > > root@srv-flux-dev-01:/# rb-site upgrade /var/www/reviews.XXX.XXX.com > WARNING:py.warnings:/usr/local/lib/python2.7/dist-packages/paramiko/transport.py:33: > CryptographyDeprecationWarning: Python 2 is no longer supported by the > Python core team. Support for it is now deprecated in cryptography, and > will be removed in the next release. > from cryptography.hazmat.backends import default_backend > > Rebuilding directory structure > Updating database. This may take a while. > > The log output below, including warnings and errors, > can be ignored unless upgrade fails. > > -- -- > > [!] Unable to execute the manager command syncdb: cannot import name > signals > > [!] Unable to execute the manager command registerscmtools: cannot > import name signals > > [!] Unable to execute the manager command evolve: cannot import name > signals > --- --- > > Resetting in-database caches. > > [!] Unable to execute the manager command fixreviewcounts: No module > named bleach_allowlist > > Upgrade complete! > > There are duplicate copies of diffs in your database that can be condensed. > These are the result of posting several iterations of a change for review > on > older versions of Review Board. > > Removing duplicate diff data will save space in your database and speed up > future upgrades. > > To condense duplicate diffs, type the following: > > $ rb-site manage /var/www/reviews.XXX.XXX.com condensediffs > > > root@srv-flux-dev-01:/# tail -n30 /var/log/apache2/error.log > [Wed May 05 08:20:37.853326 2021] [wsgi:error] [pid 5063:tid > 139949663827712] [client 192.168.4.87:53160] self.load_middleware(), > referer: http://srv-reviewboard:8089/dashboard/ > [Wed May 05 08:20:37.853350 2021] [wsgi:error] [pid 5063:tid > 139949663827712] [client 192.168.4.87:53160] File > "/usr/local/lib/python2.7/dist-packages/django/core/handlers/base.py", line > 45, in load_middleware, referer: http://srv-reviewboard:8089/dashboard/ > [Wed May 05 08:20:37.853385 2021] [wsgi:error] [pid 5063:tid > 139949663827712] [client 192.168.4.87:53160] mw_class = > import_by_path(middleware_path), referer: > http://srv-reviewboard:8089/dashboard/ > [Wed May 05 08:20:37.853406 2021] [wsgi:error] [pid 5063:tid > 139949663827712] [client 192.168.4.87:53160] File > "/usr/local/lib/python2.7/dist-packages/django/utils/module_loading.py", > line 26, in import_by_path, referer: > http://srv-reviewboard:8089/dashboard/ > [Wed May 05 08:20:37.853438 2021] [wsgi:error] [pid 5063:tid > 139949663827712] [client 192.168.4.87:53160] sys.exc_info()[2]), > referer: http://srv-reviewboard:8089/dashboard/ > [Wed May 05 08:20:37.853458 2021] [wsgi:error] [pid 5063:tid > 139949663827712] [client 192.168.4.87:53160] File > "/usr/local/lib/python2.7/dist-packages/django/utils/module_loading.py", > line 21, in import_by_path, referer: > http://srv-reviewboard:8089/dashboard/ > [Wed May 05 08:20:37.853504 2021] [wsgi:error] [pid 5063:tid > 139949663827712] [client 192.168.4.87:53160] module = > import_module(module_path), referer: > http://srv-reviewboard:8089/dashboard/ > [Wed May 05 08:20:37.853525 2021] [wsgi:error] [pid 5063:tid > 139949663827712] [client 192.168.4.87:53160] File > "/usr/local/lib/python2.7/dist-packages/django/utils/importlib.py", line > 40, in import_module, referer: http://srv-reviewboard:8089/dashboard/ > [Wed May 05 08:20:37.853556 2021] [wsgi:error] [pid 5063:tid > 139949663827712] [client 192.168.4.87:53160] __import__(name), > referer: http://srv-reviewboard:8089/dashboard/ > [Wed May 05 08:20:37.853575 2021] [wsgi:error] [pid 5063:tid > 139949663827712] [client 192.168.4.87:53160] File > "/usr/local/lib/python2.7/dist-packages/reviewboard/admin/middleware.py", > line 9, in , referer: http://srv-reviewboard:8089/dashboard/ > [Wed May 05 08:20:37.853621 2021] [wsgi:error] [pid 5063:tid > 139949663827712] [client 192.168.4.87:53160] from > reviewboard.accounts.backends.registry import get_enabled_auth_backends, > referer: http://srv-reviewboard:8089/dashboard/ > [Wed May 05 08:20:37.853653 2021] [wsgi:error] [pid 5063:tid > 139949663827712] [client 192.168.4.87:53160] File > "/usr/local/lib/python2.7/dist-packages/reviewboard/accounts/backends/__init__.py", > line 34, in , referer: http://srv-reviewboard:8089/dashboard/ > [Wed May 05 08:20:37.853686 2021] [wsgi:error] [pid 5063:tid > 139949663827712] [client 192.168.4.87:53160] from > reviewboard.accounts.backends.registry import (AuthBackendRegistry,, > referer:
Upgrade issues upgrading from 3.0.20 to 3.0.22
RB breaks when upgrading, we reverted to backup. Any clue? Previous upgrades always went fine. pip install -U ReviewBoard==3.0.22 (ok) root@srv-flux-dev-01:/# rb-site upgrade /var/www/reviews.XXX.XXX.com WARNING:py.warnings:/usr/local/lib/python2.7/dist-packages/paramiko/transport.py:33: CryptographyDeprecationWarning: Python 2 is no longer supported by the Python core team. Support for it is now deprecated in cryptography, and will be removed in the next release. from cryptography.hazmat.backends import default_backend Rebuilding directory structure Updating database. This may take a while. The log output below, including warnings and errors, can be ignored unless upgrade fails. -- -- [!] Unable to execute the manager command syncdb: cannot import name signals [!] Unable to execute the manager command registerscmtools: cannot import name signals [!] Unable to execute the manager command evolve: cannot import name signals --- --- Resetting in-database caches. [!] Unable to execute the manager command fixreviewcounts: No module named bleach_allowlist Upgrade complete! There are duplicate copies of diffs in your database that can be condensed. These are the result of posting several iterations of a change for review on older versions of Review Board. Removing duplicate diff data will save space in your database and speed up future upgrades. To condense duplicate diffs, type the following: $ rb-site manage /var/www/reviews.XXX.XXX.com condensediffs root@srv-flux-dev-01:/# tail -n30 /var/log/apache2/error.log [Wed May 05 08:20:37.853326 2021] [wsgi:error] [pid 5063:tid 139949663827712] [client 192.168.4.87:53160] self.load_middleware(), referer: http://srv-reviewboard:8089/dashboard/ [Wed May 05 08:20:37.853350 2021] [wsgi:error] [pid 5063:tid 139949663827712] [client 192.168.4.87:53160] File "/usr/local/lib/python2.7/dist-packages/django/core/handlers/base.py", line 45, in load_middleware, referer: http://srv-reviewboard:8089/dashboard/ [Wed May 05 08:20:37.853385 2021] [wsgi:error] [pid 5063:tid 139949663827712] [client 192.168.4.87:53160] mw_class = import_by_path(middleware_path), referer: http://srv-reviewboard:8089/dashboard/ [Wed May 05 08:20:37.853406 2021] [wsgi:error] [pid 5063:tid 139949663827712] [client 192.168.4.87:53160] File "/usr/local/lib/python2.7/dist-packages/django/utils/module_loading.py", line 26, in import_by_path, referer: http://srv-reviewboard:8089/dashboard/ [Wed May 05 08:20:37.853438 2021] [wsgi:error] [pid 5063:tid 139949663827712] [client 192.168.4.87:53160] sys.exc_info()[2]), referer: http://srv-reviewboard:8089/dashboard/ [Wed May 05 08:20:37.853458 2021] [wsgi:error] [pid 5063:tid 139949663827712] [client 192.168.4.87:53160] File "/usr/local/lib/python2.7/dist-packages/django/utils/module_loading.py", line 21, in import_by_path, referer: http://srv-reviewboard:8089/dashboard/ [Wed May 05 08:20:37.853504 2021] [wsgi:error] [pid 5063:tid 139949663827712] [client 192.168.4.87:53160] module = import_module(module_path), referer: http://srv-reviewboard:8089/dashboard/ [Wed May 05 08:20:37.853525 2021] [wsgi:error] [pid 5063:tid 139949663827712] [client 192.168.4.87:53160] File "/usr/local/lib/python2.7/dist-packages/django/utils/importlib.py", line 40, in import_module, referer: http://srv-reviewboard:8089/dashboard/ [Wed May 05 08:20:37.853556 2021] [wsgi:error] [pid 5063:tid 139949663827712] [client 192.168.4.87:53160] __import__(name), referer: http://srv-reviewboard:8089/dashboard/ [Wed May 05 08:20:37.853575 2021] [wsgi:error] [pid 5063:tid 139949663827712] [client 192.168.4.87:53160] File "/usr/local/lib/python2.7/dist-packages/reviewboard/admin/middleware.py", line 9, in , referer: http://srv-reviewboard:8089/dashboard/ [Wed May 05 08:20:37.853621 2021] [wsgi:error] [pid 5063:tid 139949663827712] [client 192.168.4.87:53160] from reviewboard.accounts.backends.registry import get_enabled_auth_backends, referer: http://srv-reviewboard:8089/dashboard/ [Wed May 05 08:20:37.853653 2021] [wsgi:error] [pid 5063:tid 139949663827712] [client 192.168.4.87:53160] File "/usr/local/lib/python2.7/dist-packages/reviewboard/accounts/backends/__init__.py", line 34, in , referer: http://srv-reviewboard:8089/dashboard/ [Wed May 05 08:20:37.853686 2021] [wsgi:error] [pid 5063:tid 139949663827712] [client 192.168.4.87:53160] from reviewboard.accounts.backends.registry import (AuthBackendRegistry,, referer: http://srv-reviewboard:8089/dashboard/ [Wed May 05 08:20:37.853705 2021] [wsgi:error] [pid 5063:tid 139949663827712] [client 192.168.4.87:53160] File "/usr/local/lib/python2.7/dist-packages/reviewboard/accounts/backends/registry.py", line 15, in , referer: http://srv-reviewboard:8089/dashboard/ [Wed May 05 08:20:37.853736 2021] [wsgi:error] [pid 5063:tid 139949663827712] [client 192.168.4.87:53160]
Re: Database upgrade issues - Possible fix
... Installed 0 object(s) from 0 fixture(s) Now when I log in to my site, I get this: (1054, Unknown column 'accounts_profile.is_private' in 'field list') Request Method:GETRequest URL:https://crush/Django Version:1.4.5Exception Type:DatabaseErrorException Value: (1054, Unknown column 'accounts_profile.is_private' in 'field list') Exception Location:/usr/lib/python2.6/site-packages/MySQL_python-1.2.3-py2.6-linux-x86_64.egg/MySQLdb/connections.py in defaulterrorhandler, line 36Python Executable:/usr/bin/pythonPython Version:2.6.6Python Path: ['/var/www/reviewboard/conf', '/usr/lib64/python2.6/site-packages/JCC-2.14-py2.6-linux-x86_64.egg', '/usr/lib64/python2.6/site-packages/lucene-3.6.1-py2.6-linux-x86_64.egg', '/usr/lib/python2.6/site-packages/distribute-0.6.27-py2.6.egg', '/usr/lib/python2.6/site-packages/MySQL_python-1.2.3-py2.6-linux-x86_64.egg', '/usr/lib/python2.6/site-packages/recaptcha_client-1.0.6-py2.6.egg', '/usr/lib/python2.6/site-packages/python_dateutil-1.5-py2.6.egg', '/usr/lib/python2.6/site-packages/flup-1.0.3.dev_20110405-py2.6.egg', '/usr/lib/python2.6/site-packages/Pygments-1.5-py2.6.egg', '/usr/lib/python2.6/site-packages/PIL-1.1.7-py2.6-linux-x86_64.egg', '/usr/lib/python2.6/site-packages/pycrypto-2.6-py2.6-linux-x86_64.egg', '/usr/lib/python2.6/site-packages/feedparser-5.1.3-py2.6.egg', '/usr/lib/python2.6/site-packages/ReviewBoard-1.7.6-py2.6.egg', '/usr/lib/python2.6/site-packages/pytz-2012j-py2.6.egg', '/usr/lib/python2.6/site-packages/paramiko-1.9.0-py2.6.egg', '/usr/lib/python2.6/site-packages/mimeparse-0.1.3-py2.6.egg', '/usr/lib/python2.6/site-packages/Markdown-2.2.1-py2.6.egg', '/usr/lib/python2.6/site-packages/docutils-0.10-py2.6.egg', '/usr/lib/python2.6/site-packages/django_pipeline-1.2.24-py2.6.egg', '/usr/lib/python2.6/site-packages/Djblets-0.7.11-py2.6.egg', '/usr/lib/python2.6/site-packages/Django-1.4.5-py2.6.egg', '/usr/lib/python2.6/site-packages/django_evolution-0.6.8-py2.6.egg', '/usr/lib64/python26.zip', '/usr/lib64/python2.6', '/usr/lib64/python2.6/plat-linux2', '/usr/lib64/python2.6/lib-tk', '/usr/lib64/python2.6/lib-old', '/usr/lib64/python2.6/lib-dynload', '/usr/lib64/python2.6/site-packages', '/usr/lib64/python2.6/site-packages/gst-0.10', '/usr/lib64/python2.6/site-packages/gtk-2.0', '/usr/lib64/python2.6/site-packages/webkit-1.0', '/usr/lib/python2.6/site-packages'] Server time:Fri, 1 Mar 2013 19:08:48 + I may try it again on a pristine 1.5.5 database. --Steve On Wednesday, February 27, 2013 12:16:03 AM UTC-8, Christian Hammond wrote: Hi everyone, So some of you have hit database upgrade issues before when upgrading to 1.7 (or, in some cases, 1.6). We've managed to figure out solutions for some of you, but not all. I've spent a lot of time trying to figure out solutions, find the common cases, and figure out a fix. Today, I have one that should fix it for at least some of you. What I really need are volunteers to help test it. If you're having issues now, or have had issues in the past and still have a broken database dump handy, I'd appreciate your help. Heck, even if you have had no issues, and have an old database dump to test. I have a test version of Django Evolution up at http://downloads.reviewboard.org/temp/django-evolution/ This version has some new logic that tries to avoid applying database upgrades for things that are already in the database, which was the core problem most of you hit. If you can give this a try, here's what I'd like you to do: 1) Get an installation going with your broken or pre-upgrade database. 2) Install django_evolution from the above URL, using: $ sudo easy_install -U django_evolution -f http://downloads.reviewboard.org/temp/django-evolution/ 3) Attempt a Review Board upgrade (rb-site manage /path/to/site upgrade) 4) Assuming it works, try to access the site and make sure things generally work on it. Please then reply to this post with the following information: 1) The complete log output. 2) Whether you were testing with a dump from before a past broken upgrade attempt, or a dump made after that past upgrade attempt failed. For extra credit, if you have did have a working database dump, sanity-checking that you don't have any upgrade problems and that the site runs would also really help me out. Thanks! Sooner I get some feedback, the sooner I can put this problem to rest. - Christian -- Christian Hammond - chi...@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...@googlegroups.com For more options, visit this group
Re: Database upgrade issues - Possible fix
Sorry for the long, messy output, here's what happened when I tested the fix. This is an attempt to upgrade a 1.5.5 database to 1.7.6. [root@crush]~/ReviewBoard# easy_install -U django_evolution -f http://downloads.reviewboard.org/temp/django-evolution/ Searching for django-evolution Reading http://pypi.python.org/simple/django_evolution/ Reading http://code.google.com/p/django-evolution/ Best match: django-evolution 0.6.8 Downloading http://pypi.python.org/packages/2.6/d/django_evolution/django_evolution-0.6.8-py2.6.egg#md5=7527e0ca398639c87b68969ceb1cd2d7 Processing django_evolution-0.6.8-py2.6.egg removing '/usr/lib/python2.6/site-packages/django_evolution-0.6.8-py2.6.egg' (and everything under it) creating /usr/lib/python2.6/site-packages/django_evolution-0.6.8-py2.6.egg Extracting django_evolution-0.6.8-py2.6.egg to /usr/lib/python2.6/site-packages django-evolution 0.6.8 is already the active version in easy-install.pth Installed /usr/lib/python2.6/site-packages/django_evolution-0.6.8-py2.6.egg Processing dependencies for django-evolution Finished processing dependencies for django-evolution Searching for -f Reading http://pypi.python.org/simple/-f/ Couldn't find index page for '-f' (maybe misspelled?) Scanning index of all packages (this may take a while) Reading http://pypi.python.org/simple/ C-c C-c^Cinterrupted I don't know why easy_install got confused by '-f', but I did get a new django_evolution, so I tried updating my broken site: [root@crush]~/ReviewBoard# cat rb-upgrade.log Error: Model 'reviews.FileAttachmentComment' already has a field named 'extra_data' Rebuilding directory structure Updating database. This may take a while. The log output below, including warnings and errors, can be ignored unless upgrade fails. -- begin log output -- Creating tables ... There are unapplied evolutions for auth. There are unapplied evolutions for accounts. There are unapplied evolutions for changedescs. There are unapplied evolutions for diffviewer. There are unapplied evolutions for reviews. There are unapplied evolutions for scmtools. Project signature has changed - an evolution is required Installing custom SQL ... Installing indexes ... Installed 0 object(s) from 0 fixture(s) Now when I log in to my site, I get this: (1054, Unknown column 'accounts_profile.is_private' in 'field list') Request Method:GETRequest URL:https://crush/Django Version:1.4.5Exception Type:DatabaseErrorException Value: (1054, Unknown column 'accounts_profile.is_private' in 'field list') Exception Location:/usr/lib/python2.6/site-packages/MySQL_python-1.2.3-py2.6-linux-x86_64.egg/MySQLdb/connections.py in defaulterrorhandler, line 36Python Executable:/usr/bin/pythonPython Version:2.6.6Python Path: ['/var/www/reviewboard/conf', '/usr/lib64/python2.6/site-packages/JCC-2.14-py2.6-linux-x86_64.egg', '/usr/lib64/python2.6/site-packages/lucene-3.6.1-py2.6-linux-x86_64.egg', '/usr/lib/python2.6/site-packages/distribute-0.6.27-py2.6.egg', '/usr/lib/python2.6/site-packages/MySQL_python-1.2.3-py2.6-linux-x86_64.egg', '/usr/lib/python2.6/site-packages/recaptcha_client-1.0.6-py2.6.egg', '/usr/lib/python2.6/site-packages/python_dateutil-1.5-py2.6.egg', '/usr/lib/python2.6/site-packages/flup-1.0.3.dev_20110405-py2.6.egg', '/usr/lib/python2.6/site-packages/Pygments-1.5-py2.6.egg', '/usr/lib/python2.6/site-packages/PIL-1.1.7-py2.6-linux-x86_64.egg', '/usr/lib/python2.6/site-packages/pycrypto-2.6-py2.6-linux-x86_64.egg', '/usr/lib/python2.6/site-packages/feedparser-5.1.3-py2.6.egg', '/usr/lib/python2.6/site-packages/ReviewBoard-1.7.6-py2.6.egg', '/usr/lib/python2.6/site-packages/pytz-2012j-py2.6.egg', '/usr/lib/python2.6/site-packages/paramiko-1.9.0-py2.6.egg', '/usr/lib/python2.6/site-packages/mimeparse-0.1.3-py2.6.egg', '/usr/lib/python2.6/site-packages/Markdown-2.2.1-py2.6.egg', '/usr/lib/python2.6/site-packages/docutils-0.10-py2.6.egg', '/usr/lib/python2.6/site-packages/django_pipeline-1.2.24-py2.6.egg', '/usr/lib/python2.6/site-packages/Djblets-0.7.11-py2.6.egg', '/usr/lib/python2.6/site-packages/Django-1.4.5-py2.6.egg', '/usr/lib/python2.6/site-packages/django_evolution-0.6.8-py2.6.egg', '/usr/lib64/python26.zip', '/usr/lib64/python2.6', '/usr/lib64/python2.6/plat-linux2', '/usr/lib64/python2.6/lib-tk', '/usr/lib64/python2.6/lib-old', '/usr/lib64/python2.6/lib-dynload', '/usr/lib64/python2.6/site-packages', '/usr/lib64/python2.6/site-packages/gst-0.10', '/usr/lib64/python2.6/site-packages/gtk-2.0', '/usr/lib64/python2.6/site-packages/webkit-1.0', '/usr/lib/python2.6/site-packages'] Server time:Fri, 1 Mar 2013 19:08:48 + I may try it again on a pristine 1.5.5 database. --Steve On Wednesday, February 27, 2013 12:16:03 AM UTC-8, Christian Hammond wrote: Hi everyone, So some of you have hit database upgrade issues before when upgrading to 1.7 (or, in some cases, 1.6). We've managed to figure out solutions for some of you, but not all
Re: Database upgrade issues - Possible fix
evolutions for scmtools. Project signature has changed - an evolution is required Installing custom SQL ... Installing indexes ... Installed 0 object(s) from 0 fixture(s) Now when I log in to my site, I get this: (1054, Unknown column 'accounts_profile.is_private' in 'field list') Request Method:GETRequest URL:https://crush/Django Version:1.4.5Exception Type:DatabaseErrorException Value: (1054, Unknown column 'accounts_profile.is_private' in 'field list') Exception Location:/usr/lib/python2.6/site-packages/MySQL_python-1.2.3-py2.6-linux-x86_64.egg/MySQLdb/connections.py in defaulterrorhandler, line 36Python Executable:/usr/bin/pythonPython Version:2.6.6Python Path: ['/var/www/reviewboard/conf', '/usr/lib64/python2.6/site-packages/JCC-2.14-py2.6-linux-x86_64.egg', '/usr/lib64/python2.6/site-packages/lucene-3.6.1-py2.6-linux-x86_64.egg', '/usr/lib/python2.6/site-packages/distribute-0.6.27-py2.6.egg', '/usr/lib/python2.6/site-packages/MySQL_python-1.2.3-py2.6-linux-x86_64.egg', '/usr/lib/python2.6/site-packages/recaptcha_client-1.0.6-py2.6.egg', '/usr/lib/python2.6/site-packages/python_dateutil-1.5-py2.6.egg', '/usr/lib/python2.6/site-packages/flup-1.0.3.dev_20110405-py2.6.egg', '/usr/lib/python2.6/site-packages/Pygments-1.5-py2.6.egg', '/usr/lib/python2.6/site-packages/PIL-1.1.7-py2.6-linux-x86_64.egg', '/usr/lib/python2.6/site-packages/pycrypto-2.6-py2.6-linux-x86_64.egg', '/usr/lib/python2.6/site-packages/feedparser-5.1.3-py2.6.egg', '/usr/lib/python2.6/site-packages/ReviewBoard-1.7.6-py2.6.egg', '/usr/lib/python2.6/site-packages/pytz-2012j-py2.6.egg', '/usr/lib/python2.6/site-packages/paramiko-1.9.0-py2.6.egg', '/usr/lib/python2.6/site-packages/mimeparse-0.1.3-py2.6.egg', '/usr/lib/python2.6/site-packages/Markdown-2.2.1-py2.6.egg', '/usr/lib/python2.6/site-packages/docutils-0.10-py2.6.egg', '/usr/lib/python2.6/site-packages/django_pipeline-1.2.24-py2.6.egg', '/usr/lib/python2.6/site-packages/Djblets-0.7.11-py2.6.egg', '/usr/lib/python2.6/site-packages/Django-1.4.5-py2.6.egg', '/usr/lib/python2.6/site-packages/django_evolution-0.6.8-py2.6.egg', '/usr/lib64/python26.zip', '/usr/lib64/python2.6', '/usr/lib64/python2.6/plat-linux2', '/usr/lib64/python2.6/lib-tk', '/usr/lib64/python2.6/lib-old', '/usr/lib64/python2.6/lib-dynload', '/usr/lib64/python2.6/site-packages', '/usr/lib64/python2.6/site-packages/gst-0.10', '/usr/lib64/python2.6/site-packages/gtk-2.0', '/usr/lib64/python2.6/site-packages/webkit-1.0', '/usr/lib/python2.6/site-packages'] Server time:Fri, 1 Mar 2013 19:08:48 + I may try it again on a pristine 1.5.5 database. --Steve On Wednesday, February 27, 2013 12:16:03 AM UTC-8, Christian Hammond wrote: Hi everyone, So some of you have hit database upgrade issues before when upgrading to 1.7 (or, in some cases, 1.6). We've managed to figure out solutions for some of you, but not all. I've spent a lot of time trying to figure out solutions, find the common cases, and figure out a fix. Today, I have one that should fix it for at least some of you. What I really need are volunteers to help test it. If you're having issues now, or have had issues in the past and still have a broken database dump handy, I'd appreciate your help. Heck, even if you have had no issues, and have an old database dump to test. I have a test version of Django Evolution up at http://downloads.reviewboard.org/temp/django-evolution/ This version has some new logic that tries to avoid applying database upgrades for things that are already in the database, which was the core problem most of you hit. If you can give this a try, here's what I'd like you to do: 1) Get an installation going with your broken or pre-upgrade database. 2) Install django_evolution from the above URL, using: $ sudo easy_install -U django_evolution -f http://downloads.reviewboard.org/temp/django-evolution/ 3) Attempt a Review Board upgrade (rb-site manage /path/to/site upgrade) 4) Assuming it works, try to access the site and make sure things generally work on it. Please then reply to this post with the following information: 1) The complete log output. 2) Whether you were testing with a dump from before a past broken upgrade attempt, or a dump made after that past upgrade attempt failed. For extra credit, if you have did have a working database dump, sanity-checking that you don't have any upgrade problems and that the site runs would also really help me out. Thanks! Sooner I get some feedback, the sooner I can put this problem to rest. - Christian -- Christian Hammond - chi...@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
Re: Database upgrade issues - Possible fix
, so I tried updating my broken site: [root@crush]~/ReviewBoard# cat rb-upgrade.log Error: Model 'reviews.**FileAttachmentComment' already has a field named 'extra_data' Rebuilding directory structure Updating database. This may take a while. The log output below, including warnings and errors, can be ignored unless upgrade fails. -- begin log output -- Creating tables ... There are unapplied evolutions for auth. There are unapplied evolutions for accounts. There are unapplied evolutions for changedescs. There are unapplied evolutions for diffviewer. There are unapplied evolutions for reviews. There are unapplied evolutions for scmtools. Project signature has changed - an evolution is required Installing custom SQL ... Installing indexes ... Installed 0 object(s) from 0 fixture(s) Now when I log in to my site, I get this: (1054, Unknown column 'accounts_profile.is_private' in 'field list') Request Method:GETRequest URL:https://crush/Django Version:1.4.5Exception Type:DatabaseErrorException Value: (1054, Unknown column 'accounts_profile.is_private' in 'field list') Exception Location:/usr/lib/python2.6/site-**packages/MySQL_python-1.2.3- **py2.6-linux-x86_64.egg/**MySQLdb/connections.py in defaulterrorhandler, line 36Python Executable:/usr/bin/pythonPython Version:2.6.6Python Path: ['/var/www/reviewboard/conf', '/usr/lib64/python2.6/site-**packages/JCC-2.14-py2.6-linux-**x86_64.egg', '/usr/lib64/python2.6/site-**packages/lucene-3.6.1-py2.6-**linux-x86_64.egg', '/usr/lib/python2.6/site-**packages/distribute-0.6.27-**py2.6.egg', '/usr/lib/python2.6/site-**packages/MySQL_python-1.2.3-**py2.6-linux-x86_64.egg', '/usr/lib/python2.6/site-**packages/recaptcha_client-1.0.**6-py2.6.egg', '/usr/lib/python2.6/site-**packages/python_dateutil-1.5-**py2.6.egg', '/usr/lib/python2.6/site-**packages/flup-1.0.3.dev_**20110405-py2.6.egg', '/usr/lib/python2.6/site-**packages/Pygments-1.5-py2.6.**egg', '/usr/lib/python2.6/site-**packages/PIL-1.1.7-py2.6-**linux-x86_64.egg', '/usr/lib/python2.6/site-**packages/pycrypto-2.6-py2.6-**linux-x86_64.egg', '/usr/lib/python2.6/site-**packages/feedparser-5.1.3-py2.**6.egg', '/usr/lib/python2.6/site-**packages/ReviewBoard-1.7.6-**py2.6.egg', '/usr/lib/python2.6/site-**packages/pytz-2012j-py2.6.egg'**, '/usr/lib/python2.6/site-**packages/paramiko-1.9.0-py2.6.**egg', '/usr/lib/python2.6/site-**packages/mimeparse-0.1.3-py2.**6.egg', '/usr/lib/python2.6/site-**packages/Markdown-2.2.1-py2.6.**egg', '/usr/lib/python2.6/site-**packages/docutils-0.10-py2.6.**egg', '/usr/lib/python2.6/site-**packages/django_pipeline-1.2.**24-py2.6.egg', '/usr/lib/python2.6/site-**packages/Djblets-0.7.11-py2.6.**egg', '/usr/lib/python2.6/site-**packages/Django-1.4.5-py2.6.**egg', '/usr/lib/python2.6/site-**packages/django_evolution-0.6.**8-py2.6.egg', '/usr/lib64/python26.zip', '/usr/lib64/python2.6', '/usr/lib64/python2.6/plat-**linux2', '/usr/lib64/python2.6/lib-tk', '/usr/lib64/python2.6/lib-old'**, '/usr/lib64/python2.6/lib-**dynload', '/usr/lib64/python2.6/site-**packages', '/usr/lib64/python2.6/site-**packages/gst-0.10', '/usr/lib64/python2.6/site-**packages/gtk-2.0', '/usr/lib64/python2.6/site-**packages/webkit-1.0', '/usr/lib/python2.6/site-**packages'] Server time:Fri, 1 Mar 2013 19:08:48 + I may try it again on a pristine 1.5.5 database. --Steve On Wednesday, February 27, 2013 12:16:03 AM UTC-8, Christian Hammond wrote: Hi everyone, So some of you have hit database upgrade issues before when upgrading to 1.7 (or, in some cases, 1.6). We've managed to figure out solutions for some of you, but not all. I've spent a lot of time trying to figure out solutions, find the common cases, and figure out a fix. Today, I have one that should fix it for at least some of you. What I really need are volunteers to help test it. If you're having issues now, or have had issues in the past and still have a broken database dump handy, I'd appreciate your help. Heck, even if you have had no issues, and have an old database dump to test. I have a test version of Django Evolution up at http://downloads.** reviewboard.org/temp/django-**evolution/http://downloads.reviewboard.org/temp/django-evolution/ This version has some new logic that tries to avoid applying database upgrades for things that are already in the database, which was the core problem most of you hit. If you can give this a try, here's what I'd like you to do: 1) Get an installation going with your broken or pre-upgrade database. 2) Install django_evolution from the above URL, using: $ sudo easy_install -U django_evolution -f http://downloads.** reviewboard.org/temp/django-**evolution/http://downloads.reviewboard.org/temp/django-evolution/ 3) Attempt a Review Board upgrade (rb-site manage /path/to/site upgrade) 4) Assuming it works, try to access the site and make sure things
Re: Database upgrade issues - Possible fix
Updating database. This may take a while. The log output below, including warnings and errors, can be ignored unless upgrade fails. -- begin log output -- Creating tables ... There are unapplied evolutions for auth. There are unapplied evolutions for accounts. There are unapplied evolutions for changedescs. There are unapplied evolutions for diffviewer. There are unapplied evolutions for reviews. There are unapplied evolutions for scmtools. Project signature has changed - an evolution is required Installing custom SQL ... Installing indexes ... Installed 0 object(s) from 0 fixture(s) Now when I log in to my site, I get this: (1054, Unknown column 'accounts_profile.is_private' in 'field list') Request Method: GET Request URL: https://crush/ Django Version: 1.4.5 Exception Type: DatabaseError Exception Value: (1054, Unknown column 'accounts_profile.is_private' in 'field list') Exception Location: /usr/lib/python2.6/site-packages/MySQL_python-1.2.3-py2.6-linux-x86_64.egg/MySQLdb/connections.py in defaulterrorhandler, line 36 Python Executable: /usr/bin/python Python Version: 2.6.6 Python Path: ['/var/www/reviewboard/conf', '/usr/lib64/python2.6/site-packages/JCC-2.14-py2.6-linux-x86_64.egg', '/usr/lib64/python2.6/site-packages/lucene-3.6.1-py2.6-linux-x86_64.egg', '/usr/lib/python2.6/site-packages/distribute-0.6.27-py2.6.egg', '/usr/lib/python2.6/site-packages/MySQL_python-1.2.3-py2.6-linux-x86_64.egg', '/usr/lib/python2.6/site-packages/recaptcha_client-1.0.6-py2.6.egg', '/usr/lib/python2.6/site-packages/python_dateutil-1.5-py2.6.egg', '/usr/lib/python2.6/site-packages/flup-1.0.3.dev_20110405-py2.6.egg', '/usr/lib/python2.6/site-packages/Pygments-1.5-py2.6.egg', '/usr/lib/python2.6/site-packages/PIL-1.1.7-py2.6-linux-x86_64.egg', '/usr/lib/python2.6/site-packages/pycrypto-2.6-py2.6-linux-x86_64.egg', '/usr/lib/python2.6/site-packages/feedparser-5.1.3-py2.6.egg', '/usr/lib/python2.6/site-packages/ReviewBoard-1.7.6-py2.6.egg', '/usr/lib/python2.6/site-packages/pytz-2012j-py2.6.egg', '/usr/lib/python2.6/site-packages/paramiko-1.9.0-py2.6.egg', '/usr/lib/python2.6/site-packages/mimeparse-0.1.3-py2.6.egg', '/usr/lib/python2.6/site-packages/Markdown-2.2.1-py2.6.egg', '/usr/lib/python2.6/site-packages/docutils-0.10-py2.6.egg', '/usr/lib/python2.6/site-packages/django_pipeline-1.2.24-py2.6.egg', '/usr/lib/python2.6/site-packages/Djblets-0.7.11-py2.6.egg', '/usr/lib/python2.6/site-packages/Django-1.4.5-py2.6.egg', '/usr/lib/python2.6/site-packages/django_evolution-0.6.8-py2.6.egg', '/usr/lib64/python26.zip', '/usr/lib64/python2.6', '/usr/lib64/python2.6/plat-linux2', '/usr/lib64/python2.6/lib-tk', '/usr/lib64/python2.6/lib-old', '/usr/lib64/python2.6/lib-dynload', '/usr/lib64/python2.6/site-packages', '/usr/lib64/python2.6/site-packages/gst-0.10', '/usr/lib64/python2.6/site-packages/gtk-2.0', '/usr/lib64/python2.6/site-packages/webkit-1.0', '/usr/lib/python2.6/site-packages'] Server time: Fri, 1 Mar 2013 19:08:48 + I may try it again on a pristine 1.5.5 database. --Steve On Wednesday, February 27, 2013 12:16:03 AM UTC-8, Christian Hammond wrote: Hi everyone, So some of you have hit database upgrade issues before when upgrading to 1.7 (or, in some cases, 1.6). We've managed to figure out solutions for some of you, but not all. I've spent a lot of time trying to figure out solutions, find the common cases, and figure out a fix. Today, I have one that should fix it for at least some of you. What I really need are volunteers to help test it. If you're having issues now, or have had issues in the past and still have a broken database dump handy, I'd appreciate your help. Heck, even if you have had no issues, and have an old database dump to test. I have a test version of Django Evolution up at http://downloads.reviewboard.org/temp/django-evolution/ This version has some new logic that tries to avoid applying database upgrades for things that are already in the database, which was the core problem most of you hit. If you can give this a try, here's what I'd like you to do: 1) Get an installation going with your broken or pre-upgrade database. 2) Install django_evolution from the above URL, using: $ sudo easy_install -U django_evolution -f http://downloads.reviewboard.org/temp/django-evolution/ 3) Attempt a Review Board upgrade (rb-site manage /path/to/site upgrade) 4) Assuming it works, try to access the site and make sure things generally work on it. Please then reply to this post with the following information: 1) The complete log output. 2) Whether you were testing with a dump from before a past broken upgrade attempt, or a dump made after that past upgrade attempt failed. For extra credit, if you have did have a working database dump, sanity-checking that you don't have
Re: Database upgrade issues - Possible fix
tested the fix. This is an attempt to upgrade a 1.5.5 database to 1.7.6. [root@crush]~/ReviewBoard# easy_install -U django_evolution -f http://downloads.reviewboard.org/temp/django-evolution/ Searching for django-evolution Reading http://pypi.python.org/simple/django_evolution/ Reading http://code.google.com/p/django-evolution/ Best match: django-evolution 0.6.8 Downloading http://pypi.python.org/packages/2.6/d/django_evolution/django_evolution-0.6.8-py2.6.egg#md5=7527e0ca398639c87b68969ceb1cd2d7 Processing django_evolution-0.6.8-py2.6.egg removing '/usr/lib/python2.6/site-packages/django_evolution-0.6.8-py2.6.egg' (and everything under it) creating /usr/lib/python2.6/site-packages/django_evolution-0.6.8-py2.6.egg Extracting django_evolution-0.6.8-py2.6.egg to /usr/lib/python2.6/site-packages django-evolution 0.6.8 is already the active version in easy-install.pth Installed /usr/lib/python2.6/site-packages/django_evolution-0.6.8-py2.6.egg Processing dependencies for django-evolution Finished processing dependencies for django-evolution Searching for -f Reading http://pypi.python.org/simple/-f/ Couldn't find index page for '-f' (maybe misspelled?) Scanning index of all packages (this may take a while) Reading http://pypi.python.org/simple/ C-c C-c^Cinterrupted I don't know why easy_install got confused by '-f', but I did get a new django_evolution, so I tried updating my broken site: [root@crush]~/ReviewBoard# cat rb-upgrade.log Error: Model 'reviews.FileAttachmentComment' already has a field named 'extra_data' Rebuilding directory structure Updating database. This may take a while. The log output below, including warnings and errors, can be ignored unless upgrade fails. -- begin log output -- Creating tables ... There are unapplied evolutions for auth. There are unapplied evolutions for accounts. There are unapplied evolutions for changedescs. There are unapplied evolutions for diffviewer. There are unapplied evolutions for reviews. There are unapplied evolutions for scmtools. Project signature has changed - an evolution is required Installing custom SQL ... Installing indexes ... Installed 0 object(s) from 0 fixture(s) Now when I log in to my site, I get this: (1054, Unknown column 'accounts_profile.is_private' in 'field list') Request Method:GETRequest URL:https://crush/Django Version:1.4.5Exception Type:DatabaseErrorException Value: (1054, Unknown column 'accounts_profile.is_private' in 'field list') Exception Location:/usr/lib/python2.6/site-packages/MySQL_python-1.2.3-py2.6-linux-x86_64.egg/MySQLdb/connections.py in defaulterrorhandler, line 36Python Executable:/usr/bin/pythonPython Version:2.6.6Python Path: ['/var/www/reviewboard/conf', '/usr/lib64/python2.6/site-packages/JCC-2.14-py2.6-linux-x86_64.egg', '/usr/lib64/python2.6/site-packages/lucene-3.6.1-py2.6-linux-x86_64.egg', '/usr/lib/python2.6/site-packages/distribute-0.6.27-py2.6.egg', '/usr/lib/python2.6/site-packages/MySQL_python-1.2.3-py2.6-linux-x86_64.egg', '/usr/lib/python2.6/site-packages/recaptcha_client-1.0.6-py2.6.egg', '/usr/lib/python2.6/site-packages/python_dateutil-1.5-py2.6.egg', '/usr/lib/python2.6/site-packages/flup-1.0.3.dev_20110405-py2.6.egg', '/usr/lib/python2.6/site-packages/Pygments-1.5-py2.6.egg', '/usr/lib/python2.6/site-packages/PIL-1.1.7-py2.6-linux-x86_64.egg', '/usr/lib/python2.6/site-packages/pycrypto-2.6-py2.6-linux-x86_64.egg', '/usr/lib/python2.6/site-packages/feedparser-5.1.3-py2.6.egg', '/usr/lib/python2.6/site-packages/ReviewBoard-1.7.6-py2.6.egg', '/usr/lib/python2.6/site-packages/pytz-2012j-py2.6.egg', '/usr/lib/python2.6/site-packages/paramiko-1.9.0-py2.6.egg', '/usr/lib/python2.6/site-packages/mimeparse-0.1.3-py2.6.egg', '/usr/lib/python2.6/site-packages/Markdown-2.2.1-py2.6.egg', '/usr/lib/python2.6/site-packages/docutils-0.10-py2.6.egg', '/usr/lib/python2.6/site-packages/django_pipeline-1.2.24-py2.6.egg', '/usr/lib/python2.6/site-packages/Djblets-0.7.11-py2.6.egg', '/usr/lib/python2.6/site-packages/Django-1.4.5-py2.6.egg', '/usr/lib/python2.6/site-packages/django_evolution-0.6.8-py2.6.egg', '/usr/lib64/python26.zip', '/usr/lib64/python2.6', '/usr/lib64/python2.6/plat-linux2', '/usr/lib64/python2.6/lib-tk', '/usr/lib64/python2.6/lib-old', '/usr/lib64/python2.6/lib-dynload', '/usr/lib64/python2.6/site-packages', '/usr/lib64/python2.6/site-packages/gst-0.10', '/usr/lib64/python2.6/site-packages/gtk-2.0', '/usr/lib64/python2.6/site-packages/webkit-1.0', '/usr/lib/python2.6/site-packages'] Server time:Fri, 1 Mar 2013 19:08:48 + I may try it again on a pristine 1.5.5 database. --Steve On Wednesday, February 27, 2013 12:16:03 AM UTC-8, Christian Hammond wrote: Hi everyone, So some of you have hit database upgrade issues before when upgrading to 1.7 (or, in some cases, 1.6). We've managed to figure out solutions
Re: Database upgrade issues - Possible fix
/lib64/python2.6/site-packages/gst-0.10', '/usr/lib64/python2.6/site-packages/gtk-2.0', '/usr/lib64/python2.6/site-packages/webkit-1.0', '/usr/lib/python2.6/site-packages'] Server time: Fri, 1 Mar 2013 19:08:48 + I may try it again on a pristine 1.5.5 database. --Steve On Wednesday, February 27, 2013 12:16:03 AM UTC-8, Christian Hammond wrote: Hi everyone, So some of you have hit database upgrade issues before when upgrading to 1.7 (or, in some cases, 1.6). We've managed to figure out solutions for some of you, but not all. I've spent a lot of time trying to figure out solutions, find the common cases, and figure out a fix. Today, I have one that should fix it for at least some of you. What I really need are volunteers to help test it. If you're having issues now, or have had issues in the past and still have a broken database dump handy, I'd appreciate your help. Heck, even if you have had no issues, and have an old database dump to test. I have a test version of Django Evolution up at http://downloads.reviewboard.org/temp/django-evolution/ This version has some new logic that tries to avoid applying database upgrades for things that are already in the database, which was the core problem most of you hit. If you can give this a try, here's what I'd like you to do: 1) Get an installation going with your broken or pre-upgrade database. 2) Install django_evolution from the above URL, using: $ sudo easy_install -U django_evolution -f http://downloads.reviewboard.org/temp/django-evolution/ 3) Attempt a Review Board upgrade (rb-site manage /path/to/site upgrade) 4) Assuming it works, try to access the site and make sure things generally work on it. Please then reply to this post with the following information: 1) The complete log output. 2) Whether you were testing with a dump from before a past broken upgrade attempt, or a dump made after that past upgrade attempt failed. For extra credit, if you have did have a working database dump, sanity-checking that you don't have any upgrade problems and that the site runs would also really help me out. Thanks! Sooner I get some feedback, the sooner I can put this problem to rest. - Christian -- Christian Hammond - chi...@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...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en --- 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. -- 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...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en --- 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. -- 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 --- 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. -- 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 --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop
Re: Database upgrade issues - Possible fix
/python2.6', '/usr/lib64/python2.6/plat-linux2', '/usr/lib64/python2.6/lib-tk', '/usr/lib64/python2.6/lib-old', '/usr/lib64/python2.6/lib-dynload', '/usr/lib64/python2.6/site-packages', '/usr/lib64/python2.6/site-packages/gst-0.10', '/usr/lib64/python2.6/site-packages/gtk-2.0', '/usr/lib64/python2.6/site-packages/webkit-1.0', '/usr/lib/python2.6/site-packages'] Server time:Fri, 1 Mar 2013 19:08:48 + I may try it again on a pristine 1.5.5 database. --Steve On Wednesday, February 27, 2013 12:16:03 AM UTC-8, Christian Hammond wrote: Hi everyone, So some of you have hit database upgrade issues before when upgrading to 1.7 (or, in some cases, 1.6). We've managed to figure out solutions for some of you, but not all. I've spent a lot of time trying to figure out solutions, find the common cases, and figure out a fix. Today, I have one that should fix it for at least some of you. What I really need are volunteers to help test it. If you're having issues now, or have had issues in the past and still have a broken database dump handy, I'd appreciate your help. Heck, even if you have had no issues, and have an old database dump to test. I have a test version of Django Evolution up at http://downloads.reviewboard.org/temp/django-evolution/ This version has some new logic that tries to avoid applying database upgrades for things that are already in the database, which was the core problem most of you hit. If you can give this a try, here's what I'd like you to do: 1) Get an installation going with your broken or pre-upgrade database. 2) Install django_evolution from the above URL, using: $ sudo easy_install -U django_evolution -f http://downloads.reviewboard.org/temp/django-evolution/ 3) Attempt a Review Board upgrade (rb-site manage /path/to/site upgrade) 4) Assuming it works, try to access the site and make sure things generally work on it. Please then reply to this post with the following information: 1) The complete log output. 2) Whether you were testing with a dump from before a past broken upgrade attempt, or a dump made after that past upgrade attempt failed. For extra credit, if you have did have a working database dump, sanity-checking that you don't have any upgrade problems and that the site runs would also really help me out. Thanks! Sooner I get some feedback, the sooner I can put this problem to rest. - Christian -- Christian Hammond - chi...@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...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en --- 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. -- 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...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en --- 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. -- 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...@googlegroups.com javascript: For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en --- 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/groups/opt_out. -- 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
Re: Database upgrade issues - Possible fix
/lib/python2.6/site-packages/feedparser-5.1.3-py2.6.egg', '/usr/lib/python2.6/site-packages/ReviewBoard-1.7.6-py2.6.egg', '/usr/lib/python2.6/site-packages/pytz-2012j-py2.6.egg', '/usr/lib/python2.6/site-packages/paramiko-1.9.0-py2.6.egg', '/usr/lib/python2.6/site-packages/mimeparse-0.1.3-py2.6.egg', '/usr/lib/python2.6/site-packages/Markdown-2.2.1-py2.6.egg', '/usr/lib/python2.6/site-packages/docutils-0.10-py2.6.egg', '/usr/lib/python2.6/site-packages/django_pipeline-1.2.24-py2.6.egg', '/usr/lib/python2.6/site-packages/Djblets-0.7.11-py2.6.egg', '/usr/lib/python2.6/site-packages/Django-1.4.5-py2.6.egg', '/usr/lib/python2.6/site-packages/django_evolution-0.6.8-py2.6.egg', '/usr/lib64/python26.zip', '/usr/lib64/python2.6', '/usr/lib64/python2.6/plat-linux2', '/usr/lib64/python2.6/lib-tk', '/usr/lib64/python2.6/lib-old', '/usr/lib64/python2.6/lib-dynload', '/usr/lib64/python2.6/site-packages', '/usr/lib64/python2.6/site-packages/gst-0.10', '/usr/lib64/python2.6/site-packages/gtk-2.0', '/usr/lib64/python2.6/site-packages/webkit-1.0', '/usr/lib/python2.6/site-packages'] Server time:Fri, 1 Mar 2013 19:08:48 + I may try it again on a pristine 1.5.5 database. --Steve On Wednesday, February 27, 2013 12:16:03 AM UTC-8, Christian Hammond wrote: Hi everyone, So some of you have hit database upgrade issues before when upgrading to 1.7 (or, in some cases, 1.6). We've managed to figure out solutions for some of you, but not all. I've spent a lot of time trying to figure out solutions, find the common cases, and figure out a fix. Today, I have one that should fix it for at least some of you. What I really need are volunteers to help test it. If you're having issues now, or have had issues in the past and still have a broken database dump handy, I'd appreciate your help. Heck, even if you have had no issues, and have an old database dump to test. I have a test version of Django Evolution up at http://downloads.reviewboard.org/temp/django-evolution/ This version has some new logic that tries to avoid applying database upgrades for things that are already in the database, which was the core problem most of you hit. If you can give this a try, here's what I'd like you to do: 1) Get an installation going with your broken or pre-upgrade database. 2) Install django_evolution from the above URL, using: $ sudo easy_install -U django_evolution -f http://downloads.reviewboard.org/temp/django-evolution/ 3) Attempt a Review Board upgrade (rb-site manage /path/to/site upgrade) 4) Assuming it works, try to access the site and make sure things generally work on it. Please then reply to this post with the following information: 1) The complete log output. 2) Whether you were testing with a dump from before a past broken upgrade attempt, or a dump made after that past upgrade attempt failed. For extra credit, if you have did have a working database dump, sanity-checking that you don't have any upgrade problems and that the site runs would also really help me out. Thanks! Sooner I get some feedback, the sooner I can put this problem to rest. - Christian -- Christian Hammond - chi...@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...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en --- 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. -- 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...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en --- 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. -- 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
Re: Database upgrade issues - Possible fix
column 'accounts_profile.is_private' in 'field list') Exception Location:/usr/lib/python2.6/site-packages/MySQL_python-1.2.3-py2.6-linux-x86_64.egg/MySQLdb/connections.py in defaulterrorhandler, line 36Python Executable:/usr/bin/pythonPython Version:2.6.6Python Path: ['/var/www/reviewboard/conf', '/usr/lib64/python2.6/site-packages/JCC-2.14-py2.6-linux-x86_64.egg', '/usr/lib64/python2.6/site-packages/lucene-3.6.1-py2.6-linux-x86_64.egg', '/usr/lib/python2.6/site-packages/distribute-0.6.27-py2.6.egg', '/usr/lib/python2.6/site-packages/MySQL_python-1.2.3-py2.6-linux-x86_64.egg', '/usr/lib/python2.6/site-packages/recaptcha_client-1.0.6-py2.6.egg', '/usr/lib/python2.6/site-packages/python_dateutil-1.5-py2.6.egg', '/usr/lib/python2.6/site-packages/flup-1.0.3.dev_20110405-py2.6.egg', '/usr/lib/python2.6/site-packages/Pygments-1.5-py2.6.egg', '/usr/lib/python2.6/site-packages/PIL-1.1.7-py2.6-linux-x86_64.egg', '/usr/lib/python2.6/site-packages/pycrypto-2.6-py2.6-linux-x86_64.egg', '/usr/lib/python2.6/site-packages/feedparser-5.1.3-py2.6.egg', '/usr/lib/python2.6/site-packages/ReviewBoard-1.7.6-py2.6.egg', '/usr/lib/python2.6/site-packages/pytz-2012j-py2.6.egg', '/usr/lib/python2.6/site-packages/paramiko-1.9.0-py2.6.egg', '/usr/lib/python2.6/site-packages/mimeparse-0.1.3-py2.6.egg', '/usr/lib/python2.6/site-packages/Markdown-2.2.1-py2.6.egg', '/usr/lib/python2.6/site-packages/docutils-0.10-py2.6.egg', '/usr/lib/python2.6/site-packages/django_pipeline-1.2.24-py2.6.egg', '/usr/lib/python2.6/site-packages/Djblets-0.7.11-py2.6.egg', '/usr/lib/python2.6/site-packages/Django-1.4.5-py2.6.egg', '/usr/lib/python2.6/site-packages/django_evolution-0.6.8-py2.6.egg', '/usr/lib64/python26.zip', '/usr/lib64/python2.6', '/usr/lib64/python2.6/plat-linux2', '/usr/lib64/python2.6/lib-tk', '/usr/lib64/python2.6/lib-old', '/usr/lib64/python2.6/lib-dynload', '/usr/lib64/python2.6/site-packages', '/usr/lib64/python2.6/site-packages/gst-0.10', '/usr/lib64/python2.6/site-packages/gtk-2.0', '/usr/lib64/python2.6/site-packages/webkit-1.0', '/usr/lib/python2.6/site-packages'] Server time:Fri, 1 Mar 2013 19:08:48 + I may try it again on a pristine 1.5.5 database. --Steve On Wednesday, February 27, 2013 12:16:03 AM UTC-8, Christian Hammond wrote: Hi everyone, So some of you have hit database upgrade issues before when upgrading to 1.7 (or, in some cases, 1.6). We've managed to figure out solutions for some of you, but not all. I've spent a lot of time trying to figure out solutions, find the common cases, and figure out a fix. Today, I have one that should fix it for at least some of you. What I really need are volunteers to help test it. If you're having issues now, or have had issues in the past and still have a broken database dump handy, I'd appreciate your help. Heck, even if you have had no issues, and have an old database dump to test. I have a test version of Django Evolution up at http://downloads.reviewboard.org/temp/django-evolution/ This version has some new logic that tries to avoid applying database upgrades for things that are already in the database, which was the core problem most of you hit. If you can give this a try, here's what I'd like you to do: 1) Get an installation going with your broken or pre-upgrade database. 2) Install django_evolution from the above URL, using: $ sudo easy_install -U django_evolution -f http://downloads.reviewboard.org/temp/django-evolution/ 3) Attempt a Review Board upgrade (rb-site manage /path/to/site upgrade) 4) Assuming it works, try to access the site and make sure things generally work on it. Please then reply to this post with the following information: 1) The complete log output. 2) Whether you were testing with a dump from before a past broken upgrade attempt, or a dump made after that past upgrade attempt failed. For extra credit, if you have did have a working database dump, sanity-checking that you don't have any upgrade problems and that the site runs would also really help me out. Thanks! Sooner I get some feedback, the sooner I can put this problem to rest. - Christian -- Christian Hammond - chi...@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...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en --- 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
Database upgrade issues - Possible fix
Hi everyone, So some of you have hit database upgrade issues before when upgrading to 1.7 (or, in some cases, 1.6). We've managed to figure out solutions for some of you, but not all. I've spent a lot of time trying to figure out solutions, find the common cases, and figure out a fix. Today, I have one that should fix it for at least some of you. What I really need are volunteers to help test it. If you're having issues now, or have had issues in the past and still have a broken database dump handy, I'd appreciate your help. Heck, even if you have had no issues, and have an old database dump to test. I have a test version of Django Evolution up at http://downloads.reviewboard.org/temp/django-evolution/ This version has some new logic that tries to avoid applying database upgrades for things that are already in the database, which was the core problem most of you hit. If you can give this a try, here's what I'd like you to do: 1) Get an installation going with your broken or pre-upgrade database. 2) Install django_evolution from the above URL, using: $ sudo easy_install -U django_evolution -f http://downloads.reviewboard.org/temp/django-evolution/ 3) Attempt a Review Board upgrade (rb-site manage /path/to/site upgrade) 4) Assuming it works, try to access the site and make sure things generally work on it. Please then reply to this post with the following information: 1) The complete log output. 2) Whether you were testing with a dump from before a past broken upgrade attempt, or a dump made after that past upgrade attempt failed. For extra credit, if you have did have a working database dump, sanity-checking that you don't have any upgrade problems and that the site runs would also really help me out. Thanks! Sooner I get some feedback, the sooner I can put this problem to rest. - 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 --- 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.
1.6.13 to 1.7.1 upgrade issues: ERROR (EXTERNAL IP): Internal Server Error: /r/213/
Since upgrading to 1.7.1 all new reviews have been running into this issue (backtrace below). I did some digging into the traceback that was generated and found the following: reviewboard/scmtools/hg.py line 215, the version variable being passed to parse_version is None. This is coming from line 213 from mercurial.__version__ import version When I run the line above from the command line I get back 1.9, but for some reason it is not working from the web server. I have not changed any set up with the web server since upgrading from 1.6.13 to 1.7.1, but this wasn't an issue before. I have verified the rb-site was properly upgraded. Is there something I missed somewhere? To get it to work in the mean time I hardcoded the version number for mercurial, which seems to have mitigated the issue (and made me feel really dirty), but I'm still not sure why it thinks it should break itself. Traceback (most recent call last): File /usr/lib/python2.6/site-packages/Django-1.4.3-py2.6.egg/django/core/handlers/base.py, line 111, in get_response response = callback(request, *callback_args, **callback_kwargs) File /usr/lib/python2.6/site-packages/ReviewBoard-1.7.1-py2.6.egg/reviewboard/accounts/decorators.py, line 20, in _check return login_required(view_func)(*args, **kwargs) File /usr/lib/python2.6/site-packages/Djblets-0.7.8-py2.6.egg/djblets/auth/util.py, line 47, in _checklogin return view_func(request, *args, **kwargs) File /usr/lib/python2.6/site-packages/ReviewBoard-1.7.1-py2.6.egg/reviewboard/reviews/views.py, line 728, in review_detail 'screenshots': screenshots, File /usr/lib/python2.6/site-packages/ReviewBoard-1.7.1-py2.6.egg/reviewboard/reviews/views.py, line 124, in _make_review_request_context upload_diff_form = UploadDiffForm(review_request) File /usr/lib/python2.6/site-packages/ReviewBoard-1.7.1-py2.6.egg/reviewboard/reviews/forms.py, line 276, in __init__ data, *args, **kwargs) File /usr/lib/python2.6/site-packages/ReviewBoard-1.7.1-py2.6.egg/reviewboard/diffviewer/forms.py, line 51, in __init__ if self.repository.get_scmtool().get_diffs_use_absolute_paths(): File /usr/lib/python2.6/site-packages/ReviewBoard-1.7.1-py2.6.egg/reviewboard/scmtools/models.py, line 134, in get_scmtool return cls(self) File /usr/lib/python2.6/site-packages/ReviewBoard-1.7.1-py2.6.egg/reviewboard/scmtools/hg.py, line 31, in __init__ self.client = HgClient(repository.path, repository.local_site) File /usr/lib/python2.6/site-packages/ReviewBoard-1.7.1-py2.6.egg/reviewboard/scmtools/hg.py, line 215, in __init__ if parse_version(version) = parse_version(1.2): File /usr/lib/python2.6/site-packages/distribute-0.6.30-py2.6.egg/pkg_resources.py, line 1984, in parse_version for part in _parse_version_parts(s.lower()): TypeError: 'NoneType' object is not callable -- 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: 1.6.13 to 1.7.1 upgrade issues: ERROR (EXTERNAL IP): Internal Server Error: /r/213/
Hi Brian, Just to sanity check, when you run that manually, is it also using Python 2.6? It seems weird that we'd be able to import that file but not get the version. In my copy here, it's nothing but a straight-forward variable assignment in a file called __version__.py. It'd be interesting to add some logging there to print mercurial.__version__.__file__ and then look in there to see what it says. Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Thu, Jan 3, 2013 at 7:55 AM, Brian Armstrong kf7...@gmail.com wrote: Since upgrading to 1.7.1 all new reviews have been running into this issue (backtrace below). I did some digging into the traceback that was generated and found the following: reviewboard/scmtools/hg.py line 215, the version variable being passed to parse_version is None. This is coming from line 213 from mercurial.__version__ import version When I run the line above from the command line I get back 1.9, but for some reason it is not working from the web server. I have not changed any set up with the web server since upgrading from 1.6.13 to 1.7.1, but this wasn't an issue before. I have verified the rb-site was properly upgraded. Is there something I missed somewhere? To get it to work in the mean time I hardcoded the version number for mercurial, which seems to have mitigated the issue (and made me feel really dirty), but I'm still not sure why it thinks it should break itself. Traceback (most recent call last): File /usr/lib/python2.6/site-packages/Django-1.4.3-py2.6.egg/django/core/handlers/base.py, line 111, in get_response response = callback(request, *callback_args, **callback_kwargs) File /usr/lib/python2.6/site-packages/ReviewBoard-1.7.1-py2.6.egg/reviewboard/accounts/decorators.py, line 20, in _check return login_required(view_func)(*args, **kwargs) File /usr/lib/python2.6/site-packages/Djblets-0.7.8-py2.6.egg/djblets/auth/util.py, line 47, in _checklogin return view_func(request, *args, **kwargs) File /usr/lib/python2.6/site-packages/ReviewBoard-1.7.1-py2.6.egg/reviewboard/reviews/views.py, line 728, in review_detail 'screenshots': screenshots, File /usr/lib/python2.6/site-packages/ReviewBoard-1.7.1-py2.6.egg/reviewboard/reviews/views.py, line 124, in _make_review_request_context upload_diff_form = UploadDiffForm(review_request) File /usr/lib/python2.6/site-packages/ReviewBoard-1.7.1-py2.6.egg/reviewboard/reviews/forms.py, line 276, in __init__ data, *args, **kwargs) File /usr/lib/python2.6/site-packages/ReviewBoard-1.7.1-py2.6.egg/reviewboard/diffviewer/forms.py, line 51, in __init__ if self.repository.get_scmtool().get_diffs_use_absolute_paths(): File /usr/lib/python2.6/site-packages/ReviewBoard-1.7.1-py2.6.egg/reviewboard/scmtools/models.py, line 134, in get_scmtool return cls(self) File /usr/lib/python2.6/site-packages/ReviewBoard-1.7.1-py2.6.egg/reviewboard/scmtools/hg.py, line 31, in __init__ self.client = HgClient(repository.path, repository.local_site) File /usr/lib/python2.6/site-packages/ReviewBoard-1.7.1-py2.6.egg/reviewboard/scmtools/hg.py, line 215, in __init__ if parse_version(version) = parse_version(1.2): File /usr/lib/python2.6/site-packages/distribute-0.6.30-py2.6.egg/pkg_resources.py, line 1984, in parse_version for part in _parse_version_parts(s.lower()): TypeError: 'NoneType' object is not callable -- 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: 1.6.13 to 1.7.1 upgrade issues: ERROR (EXTERNAL IP): Internal Server Error: /r/213/
Correct, Python 2.6.6. Everything else works, is also the weird thing. I hardcoded a version number if it came back as None (I guess I could add some logging to that if statement too) and it just keeps going. It generates the diffs fine, all the other integration options seem to work. So I have no idea what it could be. I'll add your logging and see if it comes back with anything interesting. On Thursday, January 3, 2013 2:40:03 PM UTC-7, Christian Hammond wrote: Hi Brian, Just to sanity check, when you run that manually, is it also using Python 2.6? It seems weird that we'd be able to import that file but not get the version. In my copy here, it's nothing but a straight-forward variable assignment in a file called __version__.py. It'd be interesting to add some logging there to print mercurial.__version__.__file__ and then look in there to see what it says. Christian -- Christian Hammond - chi...@chipx86.com javascript: Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Thu, Jan 3, 2013 at 7:55 AM, Brian Armstrong kf7...@gmail.comjavascript: wrote: Since upgrading to 1.7.1 all new reviews have been running into this issue (backtrace below). I did some digging into the traceback that was generated and found the following: reviewboard/scmtools/hg.py line 215, the version variable being passed to parse_version is None. This is coming from line 213 from mercurial.__version__ import version When I run the line above from the command line I get back 1.9, but for some reason it is not working from the web server. I have not changed any set up with the web server since upgrading from 1.6.13 to 1.7.1, but this wasn't an issue before. I have verified the rb-site was properly upgraded. Is there something I missed somewhere? To get it to work in the mean time I hardcoded the version number for mercurial, which seems to have mitigated the issue (and made me feel really dirty), but I'm still not sure why it thinks it should break itself. Traceback (most recent call last): File /usr/lib/python2.6/site-packages/Django-1.4.3-py2.6.egg/django/core/handlers/base.py, line 111, in get_response response = callback(request, *callback_args, **callback_kwargs) File /usr/lib/python2.6/site-packages/ReviewBoard-1.7.1-py2.6.egg/reviewboard/accounts/decorators.py, line 20, in _check return login_required(view_func)(*args, **kwargs) File /usr/lib/python2.6/site-packages/Djblets-0.7.8-py2.6.egg/djblets/auth/util.py, line 47, in _checklogin return view_func(request, *args, **kwargs) File /usr/lib/python2.6/site-packages/ReviewBoard-1.7.1-py2.6.egg/reviewboard/reviews/views.py, line 728, in review_detail 'screenshots': screenshots, File /usr/lib/python2.6/site-packages/ReviewBoard-1.7.1-py2.6.egg/reviewboard/reviews/views.py, line 124, in _make_review_request_context upload_diff_form = UploadDiffForm(review_request) File /usr/lib/python2.6/site-packages/ReviewBoard-1.7.1-py2.6.egg/reviewboard/reviews/forms.py, line 276, in __init__ data, *args, **kwargs) File /usr/lib/python2.6/site-packages/ReviewBoard-1.7.1-py2.6.egg/reviewboard/diffviewer/forms.py, line 51, in __init__ if self.repository.get_scmtool().get_diffs_use_absolute_paths(): File /usr/lib/python2.6/site-packages/ReviewBoard-1.7.1-py2.6.egg/reviewboard/scmtools/models.py, line 134, in get_scmtool return cls(self) File /usr/lib/python2.6/site-packages/ReviewBoard-1.7.1-py2.6.egg/reviewboard/scmtools/hg.py, line 31, in __init__ self.client = HgClient(repository.path, repository.local_site) File /usr/lib/python2.6/site-packages/ReviewBoard-1.7.1-py2.6.egg/reviewboard/scmtools/hg.py, line 215, in __init__ if parse_version(version) = parse_version(1.2): File /usr/lib/python2.6/site-packages/distribute-0.6.30-py2.6.egg/pkg_resources.py, line 1984, in parse_version for part in _parse_version_parts(s.lower()): TypeError: 'NoneType' object is not callable -- 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...@googlegroups.com javascript: 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
Database upgrade issues
Hi guys, I wanted to condense the three active threads on database upgrade issues. The things you all have in common is that you're upgrading from older versions using an older Django Evolution that all had a bug causing blank hinted schema evolutions, which could cause problems when upgrading. So for each of you still having the hinted evolution problem, can you do the following: 1) Do a full SQL backup of your database 2) Run: $ rb-site manage /path/to/site shell from django_evolution.models import Version print Version.objects.all() Paste that for me. Now, here's where your backup comes in. Do this: $ rb-site manage /path/to/site shell from django_evolution.models import Version Version.objects.exclude(evolutions__pk__gt=0).delete() Then re-do the rb-site upgrade, reload the web server, and see if that works better. Test the site, make sure you don't have any database errors, and report back. I'm hoping this fixes the problem for you. If so, I can integrate this into the upgrade process for future upgrades. (Not that you should ever hit this again, since it's fixed in django-evolution.) 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: Database upgrade issues
Hi Christian, Here is what the output for the version Python 2.7.1+ (r271:86832, Apr 11 2011, 18:13:53) [GCC 4.5.2] on linux2 Type help, copyright, credits or license for more information. (InteractiveConsole) from django_evolution.models import Version print Version.objects.all() [Version: Hinted version, updated on 2012-12-27 19:00:56+00:00, Version: Hinted version, updated on 2012-10-25 05:40:26+00:00, Version: Stored version, updated on 2012-10-25 05:40:26+00:00, Version: Stored version, updated on 2011-08-08 17:07:01+00:00] I was able to successfully execute the commands in step 2 and now have a working 1.7.1 RB! A quick test does not show any issues as of yet, however I will keep an eye out for any. Thank you for your time and assistance on resolving this issue! -- 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: Database upgrade issues
Upon further testing, it seems something has changed with this release and LDAP authentication. I was able to log into RB with a local user, however all LDAP users can not log in. Do you know what has changed with the LDAP backend authentication? The RB log shows the following message 2012-12-28 06:30:38,031 - WARNING - LDAP error: The specified object does not exist in the Directory or provided invalid credentials: (emailAddress=user-email) -- 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 2810 in reviewboard: Upgrade issues from 1.6.3 to 1.6.14
Updates: Labels: Component-Deployment Comment #1 on issue 2810 by trowb...@gmail.com: Upgrade issues from 1.6.3 to 1.6.14 http://code.google.com/p/reviewboard/issues/detail?id=2810 (No comment was entered for this change.) -- 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.
Upgrade issues from 1.5.7 to 1.6.5
I'm getting the following error while trying to upgrade my 1.5.7 install
to the newer 1.6.5 package during 'rb-site upgrade'.
I am using django_evolution 0.6.7. This error is resulting in an outage
situation, so I could really use some help quickly :(
File /usr/bin/rb-site, line 9, in module
load_entry_point('ReviewBoard==1.6.5', 'console_scripts',
'rb-site')()
File /usr/lib/python2.6/site-packages/reviewboard/cmdline/rbsite.py,
line 1760, in main
command.run()
File /usr/lib/python2.6/site-packages/reviewboard/cmdline/rbsite.py,
line 1650, in run
site.migrate_database()
File /usr/lib/python2.6/site-packages/reviewboard/cmdline/rbsite.py,
line 353, in migrate_database
self.run_manage_command(evolve, [--noinput, --execute])
File /usr/lib/python2.6/site-packages/reviewboard/cmdline/rbsite.py,
line 469, in run_manage_command
execute_manager(reviewboard.settings, [__file__, cmd] + params)
File
/usr/lib/python2.6/site-packages/django/core/management/__init__.py,
line 438, in execute_manager
utility.execute()
File
/usr/lib/python2.6/site-packages/django/core/management/__init__.py,
line 379, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File
/usr/lib/python2.6/site-packages/django/core/management/base.py, line
191, in run_from_argv
self.execute(*args, **options.__dict__)
File
/usr/lib/python2.6/site-packages/django/core/management/base.py, line
220, in execute
output = self.handle(*args, **options)
File
/usr/lib/python2.6/site-packages/django_evolution/management/commands/evolve.py,
line 60, in handle
self.evolve(*app_labels, **options)
File
/usr/lib/python2.6/site-packages/django_evolution/management/commands/evolve.py,
line 140, in evolve
database))
File /usr/lib/python2.6/site-packages/django_evolution/mutations.py,
line 426, in mutate
return self.add_column(app_label, proj_sig, database)
File /usr/lib/python2.6/site-packages/django_evolution/mutations.py,
line 434, in add_column
self.field_attrs, model)
File /usr/lib/python2.6/site-packages/django_evolution/mutations.py,
line 33, in create_field
related_model_sig = proj_sig[related_app_name][related_model_name]
KeyError: 'site'
--
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: Upgrade issues from 1.5.7 to 1.6.5
Hi Stephen,
Hmm, that's concerning. My upgrade simulations aren't reproducing that.
The same issue should be hit for any 1.6 release.
Is this for the packages or FedoraHosted?
It almost sounds like the syncdb didn't set up the site app. We're there any
warnings? Do you see those in the database?
Christian
On Apr 23, 2012, at 8:32, Stephen Gallagher step...@gallagherhome.com wrote:
I'm getting the following error while trying to upgrade my 1.5.7 install
to the newer 1.6.5 package during 'rb-site upgrade'.
I am using django_evolution 0.6.7. This error is resulting in an outage
situation, so I could really use some help quickly :(
File /usr/bin/rb-site, line 9, in module
load_entry_point('ReviewBoard==1.6.5', 'console_scripts',
'rb-site')()
File /usr/lib/python2.6/site-packages/reviewboard/cmdline/rbsite.py,
line 1760, in main
command.run()
File /usr/lib/python2.6/site-packages/reviewboard/cmdline/rbsite.py,
line 1650, in run
site.migrate_database()
File /usr/lib/python2.6/site-packages/reviewboard/cmdline/rbsite.py,
line 353, in migrate_database
self.run_manage_command(evolve, [--noinput, --execute])
File /usr/lib/python2.6/site-packages/reviewboard/cmdline/rbsite.py,
line 469, in run_manage_command
execute_manager(reviewboard.settings, [__file__, cmd] + params)
File
/usr/lib/python2.6/site-packages/django/core/management/__init__.py,
line 438, in execute_manager
utility.execute()
File
/usr/lib/python2.6/site-packages/django/core/management/__init__.py,
line 379, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File
/usr/lib/python2.6/site-packages/django/core/management/base.py, line
191, in run_from_argv
self.execute(*args, **options.__dict__)
File
/usr/lib/python2.6/site-packages/django/core/management/base.py, line
220, in execute
output = self.handle(*args, **options)
File
/usr/lib/python2.6/site-packages/django_evolution/management/commands/evolve.py,
line 60, in handle
self.evolve(*app_labels, **options)
File
/usr/lib/python2.6/site-packages/django_evolution/management/commands/evolve.py,
line 140, in evolve
database))
File /usr/lib/python2.6/site-packages/django_evolution/mutations.py,
line 426, in mutate
return self.add_column(app_label, proj_sig, database)
File /usr/lib/python2.6/site-packages/django_evolution/mutations.py,
line 434, in add_column
self.field_attrs, model)
File /usr/lib/python2.6/site-packages/django_evolution/mutations.py,
line 33, in create_field
related_model_sig = proj_sig[related_app_name][related_model_name]
KeyError: 'site'
--
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: Upgrade issues from 1.5.7 to 1.6.5
On Mon, 2012-04-23 at 11:25 -0700, Christian Hammond wrote:
Hi Stephen,
Hmm, that's concerning. My upgrade simulations aren't reproducing that.
The same issue should be hit for any 1.6 release.
Is this for the packages or FedoraHosted?
This is happening from the RPMs I created for EPEL 6. They are identical
to the 1.6.5 sources except for three custom patches (attached). They
are minimally-invasive.
I also have a slightly unorthodox settings_local.py file (also attached,
portions redacted). This is because my patch for including other
apps/middleware is only in the 1.7 branch.
It almost sounds like the syncdb didn't set up the site app. We're
there any warnings? Do you see those in the database?
I'm not sure where to look for warnings and or what I need from the
database. Please clarify.
Slightly more complete output (this was with django_evolution 0.6.5):
[sgallagh@hosted03 conf]$ sudo rb-site upgrade /srv/reviewboard
Rebuilding directory structure
/usr/lib/python2.6/site-packages/django/db/__init__.py:60:
DeprecationWarning: Short names for ENGINE in database configurations
are deprecated. Prepend default.ENGINE with 'django.db.backends.'
DeprecationWarning
Upgrading from version 1.5.7
Updating database. This may take a while.
Creating tables ...
Creating table accounts_localsiteprofile
Creating table attachments_fileattachment
Creating table reviews_fileattachmentcomment
Upgrading Review Board from 1.5.7 to 1.6.5
There are unapplied evolutions for sessions.
There are unapplied evolutions for accounts.
There are unapplied evolutions for reviews.
There are unapplied evolutions for scmtools.
Loading FAS groups...
FAS groups loaded. Don't forget to set FAS_USERNAME and FAS_PASSWORD to
a low-privilege account.
Adding baseline version for new models
Project signature has changed - an evolution is required
Installing custom SQL ...
Installing indexes ...
No fixtures found.
Registering new SCM Tool Plastic SCM
(reviewboard.scmtools.plastic.PlasticTool) in database
Traceback (most recent call last):
File /usr/bin/rb-site, line 9, in module
load_entry_point('ReviewBoard==1.6.5', 'console_scripts',
'rb-site')()
File /usr/lib/python2.6/site-packages/reviewboard/cmdline/rbsite.py,
line 1760, in main
command.run()
File /usr/lib/python2.6/site-packages/reviewboard/cmdline/rbsite.py,
line 1650, in run
site.migrate_database()
File /usr/lib/python2.6/site-packages/reviewboard/cmdline/rbsite.py,
line 353, in migrate_database
self.run_manage_command(evolve, [--noinput, --execute])
File /usr/lib/python2.6/site-packages/reviewboard/cmdline/rbsite.py,
line 469, in run_manage_command
execute_manager(reviewboard.settings, [__file__, cmd] + params)
File
/usr/lib/python2.6/site-packages/django/core/management/__init__.py,
line 438, in execute_manager
utility.execute()
File
/usr/lib/python2.6/site-packages/django/core/management/__init__.py,
line 379, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File
/usr/lib/python2.6/site-packages/django/core/management/base.py, line
191, in run_from_argv
self.execute(*args, **options.__dict__)
File
/usr/lib/python2.6/site-packages/django/core/management/base.py, line
220, in execute
output = self.handle(*args, **options)
File
/usr/lib/python2.6/site-packages/django_evolution/management/commands/evolve.py,
line 60, in handle
self.evolve(*app_labels, **options)
File
/usr/lib/python2.6/site-packages/django_evolution/management/commands/evolve.py,
line 140, in evolve
database))
File /usr/lib/python2.6/site-packages/django_evolution/mutations.py,
line 418, in mutate
return self.add_column(app_label, proj_sig, database)
File /usr/lib/python2.6/site-packages/django_evolution/mutations.py,
line 426, in add_column
self.field_attrs, model)
File /usr/lib/python2.6/site-packages/django_evolution/mutations.py,
line 33, in create_field
related_model_sig = proj_sig[related_app_name][related_model_name]
KeyError: 'site'
And again after updating to django_evolution 0.6.7 (to be sure):
[sgallagh@hosted03 conf]$ sudo rb-site upgrade /srv/reviewboard
Rebuilding directory structure
/usr/lib/python2.6/site-packages/django/db/__init__.py:60:
DeprecationWarning: Short names for ENGINE in database configurations
are deprecated. Prepend default.ENGINE with 'django.db.backends.'
DeprecationWarning
Upgrading from version 1.6.5
Updating database. This may take a while.
Creating tables ...
There are unapplied evolutions for sessions.
There are unapplied evolutions for accounts.
There are unapplied evolutions for reviews.
There are unapplied evolutions for scmtools.
Loading FAS groups...
FAS groups loaded. Don't forget to set FAS_USERNAME and FAS_PASSWORD to
a low-privilege account.
Project signature has changed - an evolution is required
Installing custom SQL ...
Installing indexes ...
No fixtures found.
Traceback (most recent call last):
File /usr/bin/rb-site, line 9, in module
Re: Upgrade issues from 1.5.7 to 1.6.5
It's your settings_local. Overriding that entirely is a recipe for disaster, as
we add to that. If things are missing (the site app among a few in this case),
things will blow up.
You probably should just dynamically take what's in there, convert to a list,
and insert your models at one index before the last.
Christian
On Apr 23, 2012, at 11:36, Stephen Gallagher step...@gallagherhome.com wrote:
On Mon, 2012-04-23 at 11:25 -0700, Christian Hammond wrote:
Hi Stephen,
Hmm, that's concerning. My upgrade simulations aren't reproducing that.
The same issue should be hit for any 1.6 release.
Is this for the packages or FedoraHosted?
This is happening from the RPMs I created for EPEL 6. They are identical
to the 1.6.5 sources except for three custom patches (attached). They
are minimally-invasive.
I also have a slightly unorthodox settings_local.py file (also attached,
portions redacted). This is because my patch for including other
apps/middleware is only in the 1.7 branch.
It almost sounds like the syncdb didn't set up the site app. We're
there any warnings? Do you see those in the database?
I'm not sure where to look for warnings and or what I need from the
database. Please clarify.
Slightly more complete output (this was with django_evolution 0.6.5):
[sgallagh@hosted03 conf]$ sudo rb-site upgrade /srv/reviewboard
Rebuilding directory structure
/usr/lib/python2.6/site-packages/django/db/__init__.py:60:
DeprecationWarning: Short names for ENGINE in database configurations
are deprecated. Prepend default.ENGINE with 'django.db.backends.'
DeprecationWarning
Upgrading from version 1.5.7
Updating database. This may take a while.
Creating tables ...
Creating table accounts_localsiteprofile
Creating table attachments_fileattachment
Creating table reviews_fileattachmentcomment
Upgrading Review Board from 1.5.7 to 1.6.5
There are unapplied evolutions for sessions.
There are unapplied evolutions for accounts.
There are unapplied evolutions for reviews.
There are unapplied evolutions for scmtools.
Loading FAS groups...
FAS groups loaded. Don't forget to set FAS_USERNAME and FAS_PASSWORD to
a low-privilege account.
Adding baseline version for new models
Project signature has changed - an evolution is required
Installing custom SQL ...
Installing indexes ...
No fixtures found.
Registering new SCM Tool Plastic SCM
(reviewboard.scmtools.plastic.PlasticTool) in database
Traceback (most recent call last):
File /usr/bin/rb-site, line 9, in module
load_entry_point('ReviewBoard==1.6.5', 'console_scripts',
'rb-site')()
File /usr/lib/python2.6/site-packages/reviewboard/cmdline/rbsite.py,
line 1760, in main
command.run()
File /usr/lib/python2.6/site-packages/reviewboard/cmdline/rbsite.py,
line 1650, in run
site.migrate_database()
File /usr/lib/python2.6/site-packages/reviewboard/cmdline/rbsite.py,
line 353, in migrate_database
self.run_manage_command(evolve, [--noinput, --execute])
File /usr/lib/python2.6/site-packages/reviewboard/cmdline/rbsite.py,
line 469, in run_manage_command
execute_manager(reviewboard.settings, [__file__, cmd] + params)
File
/usr/lib/python2.6/site-packages/django/core/management/__init__.py,
line 438, in execute_manager
utility.execute()
File
/usr/lib/python2.6/site-packages/django/core/management/__init__.py,
line 379, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File
/usr/lib/python2.6/site-packages/django/core/management/base.py, line
191, in run_from_argv
self.execute(*args, **options.__dict__)
File
/usr/lib/python2.6/site-packages/django/core/management/base.py, line
220, in execute
output = self.handle(*args, **options)
File
/usr/lib/python2.6/site-packages/django_evolution/management/commands/evolve.py,
line 60, in handle
self.evolve(*app_labels, **options)
File
/usr/lib/python2.6/site-packages/django_evolution/management/commands/evolve.py,
line 140, in evolve
database))
File /usr/lib/python2.6/site-packages/django_evolution/mutations.py,
line 418, in mutate
return self.add_column(app_label, proj_sig, database)
File /usr/lib/python2.6/site-packages/django_evolution/mutations.py,
line 426, in add_column
self.field_attrs, model)
File /usr/lib/python2.6/site-packages/django_evolution/mutations.py,
line 33, in create_field
related_model_sig = proj_sig[related_app_name][related_model_name]
KeyError: 'site'
And again after updating to django_evolution 0.6.7 (to be sure):
[sgallagh@hosted03 conf]$ sudo rb-site upgrade /srv/reviewboard
Rebuilding directory structure
/usr/lib/python2.6/site-packages/django/db/__init__.py:60:
DeprecationWarning: Short names for ENGINE in database configurations
are deprecated. Prepend default.ENGINE with 'django.db.backends.'
DeprecationWarning
Upgrading from version 1.6.5
Updating database. This may take a while.
Creating tables ...
There are unapplied
Re: Upgrade issues from 1.5.7 to 1.6.5
Maybe I'm getting mixed up between 1.6.x and 1.7. It could be that we only added site in 1.6. We can get that change into 1.6.x. I was hesitant to make too many more changes to 1.6.x, but we'll be doing a larger 1.6.x release hopefully this week, so I'll try to remember to slip that one in. Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Mon, Apr 23, 2012 at 11:46 AM, Stephen Gallagher step...@gallagherhome.com wrote: On Mon, 2012-04-23 at 11:41 -0700, Christian Hammond wrote: It's your settings_local. Overriding that entirely is a recipe for disaster, as we add to that. If things are missing (the site app among a few in this case), things will blow up. Eep, that's weird. I could have sworn I added the site app, but I somehow missed it. Guess that explains that. Thanks! You say among a few. Were there others that I missed that you see? You probably should just dynamically take what's in there, convert to a list, and insert your models at one index before the last. As noted, I submitted http://reviews.reviewboard.org/r/2630/ half a year ago, but it only made it to master (not 1.6.x). That would obviously be my preferred approach to this :) -- 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: Upgrade issues from 1.5.7 to 1.6.5
On Mon, 2012-04-23 at 12:01 -0700, Christian Hammond wrote: Maybe I'm getting mixed up between 1.6.x and 1.7. It could be that we only added site in 1.6. We can get that change into 1.6.x. I was hesitant to make too many more changes to 1.6.x, but we'll be doing a larger 1.6.x release hopefully this week, so I'll try to remember to slip that one in. Thanks for your help and quick replies. We're back up and running again on Fedora Hosted. It's appreciated :) -- 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: Upgrade issues from 1.5.7 to 1.6.5
On Mon, Apr 23, 2012 at 12:25 PM, Stephen Gallagher step...@gallagherhome.com wrote: On Mon, 2012-04-23 at 12:01 -0700, Christian Hammond wrote: Maybe I'm getting mixed up between 1.6.x and 1.7. It could be that we only added site in 1.6. We can get that change into 1.6.x. I was hesitant to make too many more changes to 1.6.x, but we'll be doing a larger 1.6.x release hopefully this week, so I'll try to remember to slip that one in. Thanks for your help and quick replies. We're back up and running again on Fedora Hosted. It's appreciated :) Awesome, glad to hear it :) 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: 1.0.8 - 1.5 upgrade issues with repository management
Thanks a lot! Removing this tool solved the issues. I've added it a
year ago trying to setup demo and forgot about that.
-- Sergey
On Oct 13, 8:41 am, Christian Hammond chip...@chipx86.com wrote:
It sounds like you have the localfile scmtool installed in your database,
which is really only for testing and hasn't been maintained in forever. You
need to remove the database entry for that in scmtools_tool.
Were you using this SCMTool for anything?
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board -http://www.reviewboard.org
VMware, Inc. -http://www.vmware.com
On Tue, Oct 12, 2010 at 3:48 AM, sergius sergey.serg...@googlemail.comwrote:
I've got next issue after upgrade. Any operation with repositories
(edit/add) leads to next error:
TemplateSyntaxError at /admin/db/scmtools/repository/59/
Caught ImproperlyConfigured while rendering: Error importing SCM Tool
reviewboard.scmtools.localfile: No module named scmtools.core
Any help would be greatly appreciated :)
Traceback:
Environment:
Request Method: GET
Request URL:http://reviewboard-server/admin/db/scmtools/repository/59/
Django Version: 1.2.1
Python Version: 2.6.2
Installed Applications:
['django.contrib.admin',
'django.contrib.auth',
'django.contrib.contenttypes',
'django.contrib.markup',
'django.contrib.sites',
'django.contrib.sessions',
'djblets.datagrid',
'djblets.feedview',
'djblets.log',
'djblets.siteconfig',
'djblets.util',
'djblets.webapi',
'reviewboard.accounts',
'reviewboard.admin',
'reviewboard.changedescs',
'reviewboard.diffviewer',
'reviewboard.iphone',
'reviewboard.notifications',
'reviewboard.reports',
'reviewboard.reviews',
'reviewboard.scmtools',
'reviewboard.webapi',
'django_evolution']
Installed Middleware:
('django.middleware.gzip.GZipMiddleware',
'django.middleware.common.CommonMiddleware',
'django.middleware.doc.XViewMiddleware',
'django.middleware.http.ConditionalGetMiddleware',
'django.middleware.locale.LocaleMiddleware',
'django.contrib.sessions.middleware.SessionMiddleware',
'django.contrib.auth.middleware.AuthenticationMiddleware',
'djblets.siteconfig.middleware.SettingsMiddleware',
'reviewboard.admin.middleware.LoadSettingsMiddleware',
'djblets.log.middleware.LoggingMiddleware',
'reviewboard.admin.middleware.CheckUpdatesRequiredMiddleware',
'reviewboard.admin.middleware.X509AuthMiddleware')
Template error:
In template /usr/local/lib/python2.6/dist-packages/ReviewBoard-1.5-
py2.6.egg/reviewboard/templates/admin/scmtools/repository/
change_form.html, error at line 46
Caught ImproperlyConfigured while rendering: Error importing SCM
Tool reviewboard.scmtools.localfile: No module named scmtools.core
36 : {{field}}{% if not forloop.last %},{% endif %}
37 : {% endfor %}
38 : {% endspaceless %} ]{% if not forloop.last %},{% endif
%}
39 : {% endfor %}
40 : }{% endspaceless %}
41 :
42 : var TOOLS_FIELDS = { {% spaceless %}
43 : none: [ raw_file_url, username, password ],
44 : {% for tool in adminform.form.tool.field.queryset %}
45 : {{tool.id}}: [ {% spaceless %}
46 : {% if tool.supports_raw_file_urls %}
47 : raw_file_url,
48 : {% endif %}
49 : username, password
50 : {% endspaceless %} ]{% if not forloop.last %},{% endif
%}
51 : {% endfor %}
52 : }{% endspaceless %}
53 :
54 : var HOSTING_SERVICE_TOOLS = { {% spaceless %}
55 : {% for id, info in adminform.form.HOSTING_SERVICE_INFO.items
%}
56 : {{id}}: [ {% spaceless %}
Traceback:
File /usr/local/lib/python2.6/dist-packages/Django-1.2.1-py2.6.egg/
django/core/handlers/base.py in get_response
100. response = callback(request,
*callback_args, **callback_kwargs)
File /usr/local/lib/python2.6/dist-packages/Django-1.2.1-py2.6.egg/
django/contrib/admin/sites.py in root
512. return self.model_page(request, *url.split('/',
2))
File /usr/local/lib/python2.6/dist-packages/Django-1.2.1-py2.6.egg/
django/views/decorators/cache.py in _wrapped_view_func
69. response = view_func(request, *args, **kwargs)
File /usr/local/lib/python2.6/dist-packages/Django-1.2.1-py2.6.egg/
django/contrib/admin/sites.py in model_page
531. return admin_obj(request, rest_of_url)
File /usr/local/lib/python2.6/dist-packages/Django-1.2.1-py2.6.egg/
django/contrib/admin/options.py in __call__
1196. return self.change_view(request, unquote(url))
File /usr/local/lib/python2.6/dist-packages/Django-1.2.1-py2.6.egg/
django/utils/decorators.py in _wrapper
21. return decorator(bound_func)(*args, **kwargs)
File /usr/local/lib/python2.6/dist-packages/Django-1.2.1-py2.6.egg/
django/utils/decorators.py in _wrapped_view
76. response
Re: 1.0.8 - 1.5 upgrade issues with repository management
It sounds like you have the localfile scmtool installed in your database,
which is really only for testing and hasn't been maintained in forever. You
need to remove the database entry for that in scmtools_tool.
Were you using this SCMTool for anything?
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Tue, Oct 12, 2010 at 3:48 AM, sergius sergey.serg...@googlemail.comwrote:
I've got next issue after upgrade. Any operation with repositories
(edit/add) leads to next error:
TemplateSyntaxError at /admin/db/scmtools/repository/59/
Caught ImproperlyConfigured while rendering: Error importing SCM Tool
reviewboard.scmtools.localfile: No module named scmtools.core
Any help would be greatly appreciated :)
Traceback:
Environment:
Request Method: GET
Request URL: http://reviewboard-server/admin/db/scmtools/repository/59/
Django Version: 1.2.1
Python Version: 2.6.2
Installed Applications:
['django.contrib.admin',
'django.contrib.auth',
'django.contrib.contenttypes',
'django.contrib.markup',
'django.contrib.sites',
'django.contrib.sessions',
'djblets.datagrid',
'djblets.feedview',
'djblets.log',
'djblets.siteconfig',
'djblets.util',
'djblets.webapi',
'reviewboard.accounts',
'reviewboard.admin',
'reviewboard.changedescs',
'reviewboard.diffviewer',
'reviewboard.iphone',
'reviewboard.notifications',
'reviewboard.reports',
'reviewboard.reviews',
'reviewboard.scmtools',
'reviewboard.webapi',
'django_evolution']
Installed Middleware:
('django.middleware.gzip.GZipMiddleware',
'django.middleware.common.CommonMiddleware',
'django.middleware.doc.XViewMiddleware',
'django.middleware.http.ConditionalGetMiddleware',
'django.middleware.locale.LocaleMiddleware',
'django.contrib.sessions.middleware.SessionMiddleware',
'django.contrib.auth.middleware.AuthenticationMiddleware',
'djblets.siteconfig.middleware.SettingsMiddleware',
'reviewboard.admin.middleware.LoadSettingsMiddleware',
'djblets.log.middleware.LoggingMiddleware',
'reviewboard.admin.middleware.CheckUpdatesRequiredMiddleware',
'reviewboard.admin.middleware.X509AuthMiddleware')
Template error:
In template /usr/local/lib/python2.6/dist-packages/ReviewBoard-1.5-
py2.6.egg/reviewboard/templates/admin/scmtools/repository/
change_form.html, error at line 46
Caught ImproperlyConfigured while rendering: Error importing SCM
Tool reviewboard.scmtools.localfile: No module named scmtools.core
36 : {{field}}{% if not forloop.last %},{% endif %}
37 : {% endfor %}
38 : {% endspaceless %} ]{% if not forloop.last %},{% endif
%}
39 : {% endfor %}
40 : }{% endspaceless %}
41 :
42 : var TOOLS_FIELDS = { {% spaceless %}
43 : none: [ raw_file_url, username, password ],
44 : {% for tool in adminform.form.tool.field.queryset %}
45 : {{tool.id}}: [ {% spaceless %}
46 : {% if tool.supports_raw_file_urls %}
47 :raw_file_url,
48 : {% endif %}
49 :username, password
50 : {% endspaceless %} ]{% if not forloop.last %},{% endif
%}
51 : {% endfor %}
52 : }{% endspaceless %}
53 :
54 : var HOSTING_SERVICE_TOOLS = { {% spaceless %}
55 : {% for id, info in adminform.form.HOSTING_SERVICE_INFO.items
%}
56 : {{id}}: [ {% spaceless %}
Traceback:
File /usr/local/lib/python2.6/dist-packages/Django-1.2.1-py2.6.egg/
django/core/handlers/base.py in get_response
100. response = callback(request,
*callback_args, **callback_kwargs)
File /usr/local/lib/python2.6/dist-packages/Django-1.2.1-py2.6.egg/
django/contrib/admin/sites.py in root
512. return self.model_page(request, *url.split('/',
2))
File /usr/local/lib/python2.6/dist-packages/Django-1.2.1-py2.6.egg/
django/views/decorators/cache.py in _wrapped_view_func
69. response = view_func(request, *args, **kwargs)
File /usr/local/lib/python2.6/dist-packages/Django-1.2.1-py2.6.egg/
django/contrib/admin/sites.py in model_page
531. return admin_obj(request, rest_of_url)
File /usr/local/lib/python2.6/dist-packages/Django-1.2.1-py2.6.egg/
django/contrib/admin/options.py in __call__
1196. return self.change_view(request, unquote(url))
File /usr/local/lib/python2.6/dist-packages/Django-1.2.1-py2.6.egg/
django/utils/decorators.py in _wrapper
21. return decorator(bound_func)(*args, **kwargs)
File /usr/local/lib/python2.6/dist-packages/Django-1.2.1-py2.6.egg/
django/utils/decorators.py in _wrapped_view
76. response = view_func(request, *args,
**kwargs)
File /usr/local/lib/python2.6/dist-packages/Django-1.2.1-py2.6.egg/
django/utils/decorators.py in bound_func
17. return func(self, *args2, **kwargs2)
File /usr/local/lib/python2.6/dist-packages/Django-1.2.1-py2.6.egg/
Re: Upgrade issues
Hi there, Upgrading from an svn install I'm also hitting that one ... How did you solved it ? manually editing the database ? Regards, Benoit On Mon, Dec 8, 2008 at 20:12, Chris Clarkchris.cl...@ingres.com wrote: Christian Hammond wrote: This was due to a bug I'm currently fixing. I should have it in in about 15 mins. I'm not sure which this referred to. I've pulled (new) headrevs - I still get the problem with htdocs and an existing review not viewable anymore. BUT I know how to deal with htdocs (I'll start using the new rb-site script). RE the review not visible anymore I now know what the problem is! If you have any reviews in Draft, i.e not yet published, and you are pre change description on review update, at the time of the evolve. With sqlite the evolve appears to use the string 'changedesc_id' for the reviews_reviewrequestdraft.changedesc_id column (supposed to be integer or null). For the draft reviews I've simple updated all the reviews_reviewrequestdraft.changedesc_id columns to NULL if they == 'changedesc_id' - I've not looked any further into this or checked other database engines. Summary of the problem: upgrade from release of RB that does not have the change description field on updated reviews using sqlite have an existing review, that is in draft (with some updated diffs) you are logged in as the review owner you evolve the database view review Error traceback (from debug on, so result go to web browser) TemplateSyntaxError at /r/62/ Caught an exception while rendering: invalid literal for int(): changedesc_id Original Traceback (most recent call last): File C:\svn\django\django\template\debug.py, line 71, in render_node result = node.render(context) File C:\svn\django\django\template\debug.py, line 87, in render output = force_unicode(self.filter_expression.resolve(context)) File C:\svn\django\django\template\__init__.py, line 535, in resolve obj = self.var.resolve(context) File C:\svn\django\django\template\__init__.py, line 676, in resolve value = self._resolve_lookup(context) File C:\svn\django\django\template\__init__.py, line 705, in _resolve_lookup current = getattr(current, bit) File C:\svn\django\django\db\models\fields\related.py, line 248, in __get__ rel_obj = QuerySet(self.field.rel.to).get(**params) File C:\svn\django\django\db\models\query.py, line 297, in get clone = self.filter(*args, **kwargs) File C:\svn\django\django\db\models\query.py, line 483, in filter return self._filter_or_exclude(False, *args, **kwargs) File C:\svn\django\django\db\models\query.py, line 501, in _filter_or_exclude clone.query.add_q(Q(*args, **kwargs)) File C:\svn\django\django\db\models\sql\query.py, line 1224, in add_q can_reuse=used_aliases) File C:\svn\django\django\db\models\sql\query.py, line 1167, in add_filter self.where.add((alias, col, field, lookup_type, value), connector) File C:\svn\django\django\db\models\sql\where.py, line 48, in add params = field.get_db_prep_lookup(lookup_type, value) File C:\svn\django\django\db\models\fields\__init__.py, line 202, in get_db_prep_lookup return [self.get_db_prep_value(value)] File C:\svn\django\django\db\models\fields\__init__.py, line 353, in get_db_prep_value return int(value) ValueError: invalid literal for int(): changedesc_id Request Method: GET Request URL: http://clach04-745.ingres.prv:8000/r/62/ Exception Type: TemplateSyntaxError Exception Value: Caught an exception while rendering: invalid literal for int(): changedesc_id Original Traceback (most recent call last): File C:\svn\django\django\template\debug.py, line 71, in render_node result = node.render(context) File C:\svn\django\django\template\debug.py, line 87, in render output = force_unicode(self.filter_expression.resolve(context)) File C:\svn\django\django\template\__init__.py, line 535, in resolve obj = self.var.resolve(context) File C:\svn\django\django\template\__init__.py, line 676, in resolve value = self._resolve_lookup(context) File C:\svn\django\django\template\__init__.py, line 705, in _resolve_lookup current = getattr(current, bit) File C:\svn\django\django\db\models\fields\related.py, line 248, in __get__ rel_obj = QuerySet(self.field.rel.to).get(**params) File C:\svn\django\django\db\models\query.py, line 297, in get clone = self.filter(*args, **kwargs) File C:\svn\django\django\db\models\query.py, line 483, in filter return self._filter_or_exclude(False, *args, **kwargs) File C:\svn\django\django\db\models\query.py, line 501, in _filter_or_exclude clone.query.add_q(Q(*args, **kwargs)) File C:\svn\django\django\db\models\sql\query.py, line 1224, in add_q can_reuse=used_aliases) File C:\svn\django\django\db\models\sql\query.py, line 1167, in add_filter self.where.add((alias, col, field, lookup_type, value),
Re: Upgrade issues
I went to the admin part and looked for something that looks like 'reviews_reviewrequestdraft.changedesc_id' visited the right page (http://server/admin/db/reviews/reviewrequestdraft/), did nothing, saved, and it's gone ... thanks anyway for pointing the right database ... On Fri, Jul 17, 2009 at 15:38, Benal.ya...@gmail.com wrote: Hi there, Upgrading from an svn install I'm also hitting that one ... How did you solved it ? manually editing the database ? Regards, Benoit On Mon, Dec 8, 2008 at 20:12, Chris Clarkchris.cl...@ingres.com wrote: Christian Hammond wrote: This was due to a bug I'm currently fixing. I should have it in in about 15 mins. I'm not sure which this referred to. I've pulled (new) headrevs - I still get the problem with htdocs and an existing review not viewable anymore. BUT I know how to deal with htdocs (I'll start using the new rb-site script). RE the review not visible anymore I now know what the problem is! If you have any reviews in Draft, i.e not yet published, and you are pre change description on review update, at the time of the evolve. With sqlite the evolve appears to use the string 'changedesc_id' for the reviews_reviewrequestdraft.changedesc_id column (supposed to be integer or null). For the draft reviews I've simple updated all the reviews_reviewrequestdraft.changedesc_id columns to NULL if they == 'changedesc_id' - I've not looked any further into this or checked other database engines. Summary of the problem: upgrade from release of RB that does not have the change description field on updated reviews using sqlite have an existing review, that is in draft (with some updated diffs) you are logged in as the review owner you evolve the database view review Error traceback (from debug on, so result go to web browser) TemplateSyntaxError at /r/62/ Caught an exception while rendering: invalid literal for int(): changedesc_id Original Traceback (most recent call last): File C:\svn\django\django\template\debug.py, line 71, in render_node result = node.render(context) File C:\svn\django\django\template\debug.py, line 87, in render output = force_unicode(self.filter_expression.resolve(context)) File C:\svn\django\django\template\__init__.py, line 535, in resolve obj = self.var.resolve(context) File C:\svn\django\django\template\__init__.py, line 676, in resolve value = self._resolve_lookup(context) File C:\svn\django\django\template\__init__.py, line 705, in _resolve_lookup current = getattr(current, bit) File C:\svn\django\django\db\models\fields\related.py, line 248, in __get__ rel_obj = QuerySet(self.field.rel.to).get(**params) File C:\svn\django\django\db\models\query.py, line 297, in get clone = self.filter(*args, **kwargs) File C:\svn\django\django\db\models\query.py, line 483, in filter return self._filter_or_exclude(False, *args, **kwargs) File C:\svn\django\django\db\models\query.py, line 501, in _filter_or_exclude clone.query.add_q(Q(*args, **kwargs)) File C:\svn\django\django\db\models\sql\query.py, line 1224, in add_q can_reuse=used_aliases) File C:\svn\django\django\db\models\sql\query.py, line 1167, in add_filter self.where.add((alias, col, field, lookup_type, value), connector) File C:\svn\django\django\db\models\sql\where.py, line 48, in add params = field.get_db_prep_lookup(lookup_type, value) File C:\svn\django\django\db\models\fields\__init__.py, line 202, in get_db_prep_lookup return [self.get_db_prep_value(value)] File C:\svn\django\django\db\models\fields\__init__.py, line 353, in get_db_prep_value return int(value) ValueError: invalid literal for int(): changedesc_id Request Method: GET Request URL: http://clach04-745.ingres.prv:8000/r/62/ Exception Type: TemplateSyntaxError Exception Value: Caught an exception while rendering: invalid literal for int(): changedesc_id Original Traceback (most recent call last): File C:\svn\django\django\template\debug.py, line 71, in render_node result = node.render(context) File C:\svn\django\django\template\debug.py, line 87, in render output = force_unicode(self.filter_expression.resolve(context)) File C:\svn\django\django\template\__init__.py, line 535, in resolve obj = self.var.resolve(context) File C:\svn\django\django\template\__init__.py, line 676, in resolve value = self._resolve_lookup(context) File C:\svn\django\django\template\__init__.py, line 705, in _resolve_lookup current = getattr(current, bit) File C:\svn\django\django\db\models\fields\related.py, line 248, in __get__ rel_obj = QuerySet(self.field.rel.to).get(**params) File C:\svn\django\django\db\models\query.py, line 297, in get clone = self.filter(*args, **kwargs) File C:\svn\django\django\db\models\query.py, line 483, in filter return self._filter_or_exclude(False, *args, **kwargs) File
Upgrade issues
I've just moved to rev 1623 in trunk (I was at 1519). I do like the new manual upgrade required screen that pops up (settings.py has been updated to change the location for htdocs/media/uploaded/images). Very slick and should saves lots of admin hair pulling :-) However when I first loaded the main page (and review page) it appeared to be messed up in Google Chrome and IE6 (to the point that diffs are not usable). This turned out to be because the whole of the htdocs directory had moved (changes to settings.py), not just the upload dir. REM this is new with heads revs as of 5th dec 2008 REM rev 1623 mkdir C:\svn\django\htdocs\media\uploaded\images mkdir C:\svn\django\htdocs\media\rb\images xcopy /S /Y C:\svn\django\reviewboard\htdocs C:\svn\django\htdocs I'm assuming I can still run from SVN without the deployment tool pre RB 1.0 - is this a bad assumption? Before the change RB was using (on this Windows box) C:\svn\django\reviewboard\htdocs. The good thing is that the manual upgrade required web page helped me work out what was going in. I also had some problems with the evolve, it worked but accessing (old) reviews (against svn) I get errors about bad change description/numbers :-(. Oddly the old reviews with my work in progress SCMTool are fine. I'm planning on starting a fresh db but I have copies (sqlitedb) if there is interest in debugging this. It isn't bothering me but I thought I would mention it (rather than logging a bug/issue). The pull from trunk also updated dbjlets, etc. I don't need fixes but wanted to share this in case other people hit this too (and in case I'm deploying incorrectly). Thanks! Chris --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en -~--~~~~--~~--~--~---
Re: Upgrade issues
Hey Chris. This was due to a bug I'm currently fixing. I should have it in in about 15 mins. We've moved to using rb-site for site installations recently, and a recent change to settings.py has it look for htdocs in the parent directory of wherever settings_local.py is stored. This is due to the rb-site install directory structure (sitedir/conf/settings_local.py, sitedir/htdocs/, ...). I'm making it smarter so it will only do that if settings_local.py and settings.py aren't in the same directory. I would really recommend at this point using rb-site to do any site installs, even if you're using svn. You can run python setup.py install from your SVN checkout to get things installed so you can use rb-site. This will maintain your tree, get everything put into the right locations, and keep media files up-to-date. The GettingStarted guide has more info for migrating to this. Christian -- Christian Hammond - [EMAIL PROTECTED] VMware, Inc. On Fri, Dec 5, 2008 at 5:13 PM, Chris Clark [EMAIL PROTECTED] wrote: I've just moved to rev 1623 in trunk (I was at 1519). I do like the new manual upgrade required screen that pops up (settings.py has been updated to change the location for htdocs/media/uploaded/images). Very slick and should saves lots of admin hair pulling :-) However when I first loaded the main page (and review page) it appeared to be messed up in Google Chrome and IE6 (to the point that diffs are not usable). This turned out to be because the whole of the htdocs directory had moved (changes to settings.py), not just the upload dir. REM this is new with heads revs as of 5th dec 2008 REM rev 1623 mkdir C:\svn\django\htdocs\media\uploaded\images mkdir C:\svn\django\htdocs\media\rb\images xcopy /S /Y C:\svn\django\reviewboard\htdocs C:\svn\django\htdocs I'm assuming I can still run from SVN without the deployment tool pre RB 1.0 - is this a bad assumption? Before the change RB was using (on this Windows box) C:\svn\django\reviewboard\htdocs. The good thing is that the manual upgrade required web page helped me work out what was going in. I also had some problems with the evolve, it worked but accessing (old) reviews (against svn) I get errors about bad change description/numbers :-(. Oddly the old reviews with my work in progress SCMTool are fine. I'm planning on starting a fresh db but I have copies (sqlitedb) if there is interest in debugging this. It isn't bothering me but I thought I would mention it (rather than logging a bug/issue). The pull from trunk also updated dbjlets, etc. I don't need fixes but wanted to share this in case other people hit this too (and in case I'm deploying incorrectly). Thanks! Chris --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en -~--~~~~--~~--~--~---
