293646 - Unable to update a Firefox theme (Curacao)

Status: RESOLVED WORKSFORME

(addons.mozilla.org Graveyard :: Administration, defect)

Description

[Red_Fat_Lazy_Cat]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b2) Gecko/20050313 Firefox/1.0+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b2) Gecko/20050313 Firefox/1.0+

I'm trying to update Curacao (using the Add New Version form, NOT submitting it
as a new theme) but keep getting the following error after Step Two:

Error! The Name for your extension or theme already exists in the Update
database. Cannot Continue, aborting.

Looks like for some reason the system treats the updated JAR as a completely new
submission...

Reproducible: Always

Comment 1

[alanjstr]

https://do-not-add.mozilla.org/themes/moreinfo.php?id=100

The login is your bugzilla email address.

Comment 2

[Red_Fat_Lazy_Cat]

Tried several times after the UMO url change but the error's still there.

Comment 3

[alanjstr]

Did you change the GUID?

Comment 4

[Red_Fat_Lazy_Cat]

No, i didn't change the GUID.

Comment 5

[Red_Fat_Lazy_Cat]

Now i've got a suspicion that the error i keep getting is related to
https://bugzilla.mozilla.org/show_bug.cgi?id=275918. My second theme, Red Cats,
doesn't have this triple category thing and there wasn't any problem with
updating it.

Comment 6

[alanjstr]

*** Bug 294798 has been marked as a duplicate of this bug. ***

Comment 7

[alanjstr]

What version are you trying to upload?  Do you have a place where I can download
it from so I can test?

Comment 8

[Red_Fat_Lazy_Cat]

(In reply to comment #7)
> What version are you trying to upload?  Do you have a place where I can download
> it from so I can test?

Version 2.0.2. Here is the link:
http://www.bluecatsgraphics.com/bcgfft/ffmisc/files/curacao2_0_2.jar

Comment 9

[alanjstr]

This really shouldn't be failing like this, but it is.

::diff install.rdf install.rdf2

8c8
<     <em:version>1.15</em:version>
---
>     <em:version>2.0.2</em:version>
22c22
<     <em:description>Exotic combination of blue and brown</em:description>
---
>     <em:description>An exotic but exquisite alliance of blue and brown</em:des
cription>
28c28
<     <em:internalName>Curacao/1.15</em:internalName>
---
>     <em:internalName>Curacao/2.0.2</em:internalName>

Comment 10

[Cameron]

Addon is now listed on UMO. Red_Fat_Lazy_Cat can you explain how you got around/resolved this issue?

Comment 11

[Cameron]

(In reply to comment #10)
> Addon is now listed on UMO. Red_Fat_Lazy_Cat can you explain how you got
> around/resolved this issue?
> 

er crap. nvm. 2005 vs 2004. whoops.

continue as if i never touched this bug... :S

Comment 12

[Michael Morgan [:morgamic]]

Mass change - bugs to be read / (re)confirmed.

Comment 13

[Cameron]

AMO bugspam. Correcting QA contacts on OLD bugs ([e-mail])

-> Correct QA contact ([e-mail])

Filtermeplzkthx

Comment 14

[Mike Shaver (:shaver emeritus)]

WFM: it's updated on the site now, seems to be working fine for the author.

Comment 15

[Red_Fat_Lazy_Cat]

(In reply to comment #14)
> WFM: it's updated on the site now, seems to be working fine for the author.
> 

Nope, it still doesn't work for me. After trying to update the theme to no avail, I gave up and submitted version 3 of Curacao as a separate entry. So the bug is still there.....

Comment 16

[Mike Shaver (:shaver emeritus)]

Freaky.  fligtar: gonna hand this to you for a test in the Remora code, hope that's OK.

Comment 17

[Red_Fat_Lazy_Cat]

Things are getting worse and worse. I was trying to update version 3 of Curacao which I submitted _separately_ and got the same notorious error: "The Name for your extension or theme already exists in the Update database."

So there are two versions of Curacao in the AMO database now (GUIDs are as displayed in Control Panel):

Curacao   {5B445CF0-F69F-4fdd-8317-3E4D7BDF687A} /erroneous
Curacao 3 {cc6ef5ab-35be-4300-bd07-d12850fc97ff} /correct

Neither can be updated. Any ideas on what's going on?

Comment 18

[Justin Scott [:fligtar]]

Can you attach or link to the file you're having problems with?

(In reply to comment #17)
> Things are getting worse and worse. I was trying to update version 3 of Curacao
> which I submitted _separately_ and got the same notorious error: "The Name for
> your extension or theme already exists in the Update database."

Yes, that would make sense.. if you submitted something called "Curacao" separately from the original "Curacao", the error is applicable.

Comment 19

[Red_Fat_Lazy_Cat]

(In reply to comment #18)
> Can you attach or link to the file you're having problems with?

Sure! Here is the version I was trying to submit:
http://www.bluecatsgraphics.com/bcgfxt/fxmisc/files/curacao3_1_67.jar
 
> (In reply to comment #17)
> > Things are getting worse and worse. I was trying to update version 3 of Curacao
> > which I submitted _separately_ and got the same notorious error: "The Name for
> > your extension or theme already exists in the Update database."
> 
> Yes, that would make sense.. if you submitted something called "Curacao"
> separately from the original "Curacao", the error is applicable.
> 

Actually, the second Curacao was submitted under the name of "Curacao 3" so there _is_ a distinction, even though a subtle one. But it doesn't make any difference whatsoever. When there was just one Curacao, I got the same error.....

Comment 20

[Cameron]

Marking this ASSIGNED when it is assigned to nobody is meaningless. 

WORKSFORME on my test installation. 

If I change the em:Id in http://www.bluecatsgraphics.com/bcgfxt/fxmisc/files/curacao3_1_67.jar to {5B445CF0-F69F-4fdd-8317-3E4D7BDF687A} I can upload it as an update to add-on 100 with no problem. 

If I upload it as an update to add-on 3663, I need to change the add-on name to Curaco 3 at step two (since it automatically fills it as Curaco as that is the name in install.rdf)

Just to confirm - you're sure you uploading it as an update to the existing theme, not as a new theme? (You do so from the Item Overview page at https://addons.mozilla.org/developers/itemoverview.php?id=100)

Comment 21

[Justin Scott [:fligtar]]

What Cameron said worked fine for me as well... I was able to upload the file to both themes by using the corresponding GUIDs.

I think this is something specific to this theme and not really a Dev CP bug.

Also, it doesn't really matter whether you select to update or add a new theme - it will automatically choose the correct mode based on the GUID in install.rdf.

Comment 22

[Red_Fat_Lazy_Cat]

(In reply to comment #20)
> Marking this ASSIGNED when it is assigned to nobody is meaningless. 
> 
> WORKSFORME on my test installation. 
> 
> If I change the em:Id in
> http://www.bluecatsgraphics.com/bcgfxt/fxmisc/files/curacao3_1_67.jar to
> {5B445CF0-F69F-4fdd-8317-3E4D7BDF687A} I can upload it as an update to add-on
> 100 with no problem. 
> 
> If I upload it as an update to add-on 3663, I need to change the add-on name to
> Curaco 3 at step two (since it automatically fills it as Curaco as that is the
> name in install.rdf)
> 

Whoops. That solved the problem--many thanks! What a stupid oversight on my part. I got so entirely used to the script automatically filling in all the fields for me.....

As for the first Curacao aka add-on 100, I'm still somewhat puzzled. Okay, it's now obvious I have to change the GUID to {5B445CF0-F69F-4fdd-8317-3E4D7BDF687A} to update it successfully. The thing is, when we developers first got access to the CP, every add-on  was assigned a randomly generated GUID (at least it looked randomly generated to me) and this GUID got overwritten with the real one after updating the add-on from the CP for the first time. Correct me if I'm wrong but that's how it worked with my other theme, Red Cats, so I expected the same modus operandi when I was trying to update Curacao. Oh well. My only guess is that either something went wrong or this feature was turned off.

Happy Holidays to y'all! :)

Comment 23

[Cameron]

I suggest you choose one of the listings to continue with and delete all the versions associated with the other one. You could leave a note telling users to get the latest version from your chosen listing.