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.