Re: Issue 3486 in reviewboard: Upgrade 2.0 to 2.0.3 fails

2014-08-13 Thread reviewboard


Comment #9 on issue 3486 by robottom...@gmail.com: Upgrade 2.0 to 2.0.3  
fails

http://code.google.com/p/reviewboard/issues/detail?id=3486

We had the same issue going from 2.0 to 2.0.5 using postgres as the  
database.  We followed this workaround and it worked.


--
You received this message because this project is configured to send all  
issue notifications to this address.

You may adjust your notification preferences at:
https://code.google.com/hosting/settings

--
You received this message because you are subscribed to the Google Groups 
reviewboard-issues group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at http://groups.google.com/group/reviewboard-issues.
For more options, visit https://groups.google.com/d/optout.


Re: Issue 3486 in reviewboard: Upgrade 2.0 to 2.0.3 fails

2014-07-31 Thread reviewboard


Comment #8 on issue 3486 by chip...@gmail.com: Upgrade 2.0 to 2.0.3 fails
http://code.google.com/p/reviewboard/issues/detail?id=3486

What database?

Happen to have a dump of your 2.0.1 available still?

--
You received this message because this project is configured to send all  
issue notifications to this address.

You may adjust your notification preferences at:
https://code.google.com/hosting/settings

--
You received this message because you are subscribed to the Google Groups 
reviewboard-issues group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at http://groups.google.com/group/reviewboard-issues.
For more options, visit https://groups.google.com/d/optout.


Re: Issue 3486 in reviewboard: Upgrade 2.0 to 2.0.3 fails

2014-07-30 Thread reviewboard


Comment #7 on issue 3486 by rick...@gmail.com: Upgrade 2.0 to 2.0.3 fails
http://code.google.com/p/reviewboard/issues/detail?id=3486

Got the same issue when upgrading from 2.0.1 to 2.0.5. Manually fixed with  
Abhishek's commands.


--
You received this message because this project is configured to send all  
issue notifications to this address.

You may adjust your notification preferences at:
https://code.google.com/hosting/settings

--
You received this message because you are subscribed to the Google Groups 
reviewboard-issues group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at http://groups.google.com/group/reviewboard-issues.
For more options, visit https://groups.google.com/d/optout.


Re: Issue 3486 in reviewboard: Upgrade 2.0 to 2.0.3 fails

2014-07-28 Thread reviewboard


Comment #5 on issue 3486 by abhishek.mukher.g: Upgrade 2.0 to 2.0.3 fails
http://code.google.com/p/reviewboard/issues/detail?id=3486

This, from the sounds of it, might have been fixed by 2.0.5? The release  
notes suggest django-evolutions changes. not sure if that encompasses  
this or not.


--
You received this message because this project is configured to send all  
issue notifications to this address.

You may adjust your notification preferences at:
https://code.google.com/hosting/settings

--
You received this message because you are subscribed to the Google Groups 
reviewboard-issues group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at http://groups.google.com/group/reviewboard-issues.
For more options, visit https://groups.google.com/d/optout.


Re: Issue 3486 in reviewboard: Upgrade 2.0 to 2.0.3 fails

2014-07-28 Thread reviewboard

Updates:
Status: Fixed

Comment #6 on issue 3486 by trowb...@gmail.com: Upgrade 2.0 to 2.0.3 fails
http://code.google.com/p/reviewboard/issues/detail?id=3486

Yes, this should be fixed by 2.0.5

--
You received this message because this project is configured to send all  
issue notifications to this address.

You may adjust your notification preferences at:
https://code.google.com/hosting/settings

--
You received this message because you are subscribed to the Google Groups 
reviewboard-issues group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at http://groups.google.com/group/reviewboard-issues.
For more options, visit https://groups.google.com/d/optout.


Re: Issue 3486 in reviewboard: Upgrade 2.0 to 2.0.3 fails

2014-07-18 Thread reviewboard


Comment #1 on issue 3486 by abhishek.mukher.g: Upgrade 2.0 to 2.0.3 fails
http://code.google.com/p/reviewboard/issues/detail?id=3486

I had this issue as well. I don't quite get what django evolutions is up  
to; it seems like it's trying to drop a constraint instead of an index. I'm  
not honestly sure what the difference is in terms of postgresql since one  
has to be backed by the other anyways. I was able to get around this with  
the following psqls, followed by running the upgrade again. Not my fault if  
this doesn't work; just sayin':


reviewboard= BEGIN;
BEGIN
reviewboard= DROP INDEX scmtools_repository_df00fa5c;
DROP INDEX
reviewboard= ALTER TABLE scmtools_repository ADD CONSTRAINT  
scmtools_repository_df00fa5c UNIQUE (path, local_site_id);
NOTICE:  ALTER TABLE / ADD UNIQUE will create implicit  
index scmtools_repository_df00fa5c for table scmtools_repository

ALTER TABLE
reviewboard= \d scmtools_repository;
   Table public.scmtools_repository
   Column   |  Type  | 
Modifiers

++--
 id | integer| not null default  
nextval('scmtools_repository_id_seq'::regclass)

 name   | character varying(64)  | not null
 path   | character varying(255) | not null
 mirror_path| character varying(255) | not null
 raw_file_url   | character varying(255) | not null
 username   | character varying(32)  | not null
 password   | character varying(128) | not null
 tool_id| integer| not null
 bug_tracker| character varying(256) | not null
 encoding   | character varying(32)  | not null
 visible| boolean| not null
 local_site_id  | integer|
 public | boolean| not null
 extra_data | text   |
 hosting_account_id | integer|
Indexes:
scmtools_repository_pkey PRIMARY KEY, btree (id)
scmtools_repository_97c59b73 UNIQUE, btree (name, local_site_id)
scmtools_repository_df00fa5c UNIQUE, btree (path, local_site_id)
scmtools_repository_hosting_account_id btree (hosting_account_id)
scmtools_repository_local_site_id btree (local_site_id)
scmtools_repository_tool_id btree (tool_id)
Foreign-key constraints:
scmtools_repository_hosting_account_id_fkey FOREIGN KEY  
(hosting_account_id) REFERENCES hostingsvcs_hostingserviceaccount(id)  
DEFERRABLE INITIALLY DEFERRED
scmtools_repository_local_site_id_fkey FOREIGN KEY (local_site_id)  
REFERENCES site_localsite(id) DEFERRABLE INITIALLY DEFERRED
scmtools_repository_tool_id_fkey FOREIGN KEY (tool_id) REFERENCES  
scmtools_tool(id) DEFERRABLE INITIALLY DEFERRED


reviewboard= ALTER TABLE scmtools_repository DROP CONSTRAINT  
scmtools_repository_df00fa5c;

ALTER TABLE
reviewboard= ROLLBACK;
ROLLBACK
reviewboard= BEGIN;
BEGIN
reviewboard= DROP INDEX scmtools_repository_df00fa5c;
DROP INDEX
reviewboard= ALTER TABLE scmtools_repository ADD CONSTRAINT  
scmtools_repository_df00fa5c UNIQUE (path, local_site_id);
NOTICE:  ALTER TABLE / ADD UNIQUE will create implicit  
index scmtools_repository_df00fa5c for table scmtools_repository

ALTER TABLE
reviewboard= COMMIT;


--
You received this message because this project is configured to send all  
issue notifications to this address.

You may adjust your notification preferences at:
https://code.google.com/hosting/settings

--
You received this message because you are subscribed to the Google Groups 
reviewboard-issues group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at http://groups.google.com/group/reviewboard-issues.
For more options, visit https://groups.google.com/d/optout.


Issue 3486 in reviewboard: Upgrade 2.0 to 2.0.3 fails

2014-07-17 Thread reviewboard

Status: New
Owner: 
Labels: Type-Defect Priority-Medium

New issue 3486 by drzo...@gmail.com: Upgrade 2.0 to 2.0.3 fails
http://code.google.com/p/reviewboard/issues/detail?id=3486

What version are you running?
2.0

What's the URL of the page containing the problem?
All, unable to access after upgrade. See log below.

What steps will reproduce the problem?
1. easy_install --index-url=https://pypi.mycopany.com -U ReviewBoard
2.  rb-site upgrade /srv/reviewboard-env/reviewboard.mycompany/
3.

What is the expected output? What do you see instead?
Expect: no error.

Actual: output of running rb-site upgrade:
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 ...
Upgrading Review Board from 2.0 to 2.0.3
There are unapplied evolutions for accounts.
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)
CommandError: Error applying evolution:  
constraint scmtools_repository_df00fa5c of relation scmtools_repository  
does not exist



When Accessing review board I get this:
Traceback (most recent call last):

   
File /usr/lib/python2.6/site-packages/Django-1.6.5-py2.6.egg/django/core/handlers/base.py,  
line 88, in get_response

response = middleware_method(request)

   
File /srv/reviewboard-env/lib/python2.6/site-packages/ReviewBoard-2.0.3-py2.6.egg/reviewboard/accounts/middleware.py,  
line 14, in process_request

user = request.user.get_profile()

   
File /srv/reviewboard-env/lib/python2.6/site-packages/ReviewBoard-2.0.3-py2.6.egg/reviewboard/accounts/models.py,  
line 284, in _get_profile

self._profile = Profile.objects.get(user=self)

   
File /usr/lib/python2.6/site-packages/Django-1.6.5-py2.6.egg/django/db/models/manager.py,  
line 151, in get

return self.get_queryset().get(*args, **kwargs)

   
File /usr/lib/python2.6/site-packages/Django-1.6.5-py2.6.egg/django/db/models/query.py,  
line 304, in get

num = len(clone)

   
File /usr/lib/python2.6/site-packages/Django-1.6.5-py2.6.egg/django/db/models/query.py,  
line 77, in __len__

self._fetch_all()

   
File /usr/lib/python2.6/site-packages/Django-1.6.5-py2.6.egg/django/db/models/query.py,  
line 857, in _fetch_all

self._result_cache = list(self.iterator())

   
File /usr/lib/python2.6/site-packages/Django-1.6.5-py2.6.egg/django/db/models/query.py,  
line 220, in iterator

for row in compiler.results_iter():

   
File /usr/lib/python2.6/site-packages/Django-1.6.5-py2.6.egg/django/db/models/sql/compiler.py,  
line 713, in results_iter

for rows in self.execute_sql(MULTI):

   
File /usr/lib/python2.6/site-packages/Django-1.6.5-py2.6.egg/django/db/models/sql/compiler.py,  
line 786, in execute_sql

cursor.execute(sql, params)

   
File /usr/lib/python2.6/site-packages/Django-1.6.5-py2.6.egg/django/db/backends/util.py,  
line 53, in execute

return self.cursor.execute(sql, params)

   
File /usr/lib/python2.6/site-packages/Django-1.6.5-py2.6.egg/django/db/utils.py,  
line 99, in __exit__

six.reraise(dj_exc_type, dj_exc_value, traceback)

   
File /usr/lib/python2.6/site-packages/Django-1.6.5-py2.6.egg/django/db/backends/util.py,  
line 53, in execute

return self.cursor.execute(sql, params)

ProgrammingError: column accounts_profile.should_send_email does not exist
LINE 1: ..._id, accounts_profile.first_time_setup_done, accounts_...

What operating system are you using? What browser?


Please provide any additional information below.
Some info from our reviewdatabase. The  scmtools_repository_df00fa5c  
constrain is an index, and it seems to exist:



reviewboard= \dS+ scmtools_repository

Table public.scmtools_repository
   Column   |  Type  | 
Modifiers | Storage  | Stats target |  
Description

++--+--+--+-
 id | integer| not null default  
nextval('scmtools_repository_id_seq'::regclass) | plain|  |
 name   | character varying(64)  | not  
null | extended  
|  |
 path   | character varying(255) | not  
null | extended  
|  |
 mirror_path| character varying(255) | not  
null | extended  
|  |
 raw_file_url   | character varying(255) | not  
null | extended  
|