Closed Bug 1034216 Opened 6 years ago Closed 6 years ago
Sign and dev deploy the Firefox update hotfix (v20140527
+++ This bug was initially created as a clone of Bug #1028388 +++ We have a new version of the hotfix that needs signing. It's attached. Please sign and deploy to the dev/staging server like was done before.
Feel free to resolve the bug when deployed.
This file has the same version number than the one that was previously uploaded. AMO doesn't handle this well, it requires a new version number.
argh, I'm doing something wrong... nthomas, halp! :)
I don't think you are. Previously we've had simpler hotfixes where QA in staging didn't hit any issues, but now we're iterating and hitting an AMO requirement we didn't know about before. Jorge, are you referring to the version number in install.rdf, or the filename ?
Flags: needinfo?(nthomas) → needinfo?(jorge)
Looks like that may be the same thing, almost https://hg.mozilla.org/releases/firefox-hotfixes/file/fc3c622aff83/v20140527.01/install.rdf
The version number on install.rdf is what I care about, and I checked that it was the same as the one that was previously uploaded to AMO -dev.
gps, please bump the version in install.rdf and attach a new xpi to sign.
Assignee: rail → gps
I bumped the <em:version> to "20140527.01.1" I hope this does the trick! Will we need to do this in the final hotfix as well? Should I commit this source change?
(In reply to Gregory Szorc [:gps] from comment #9) > Will we need to do this in the final hotfix as well? Should I commit this > source change? It's not necessary to do this for the final hotfix, since I haven't uploaded anything to production so far.
Better to not change anything between staging QA and production though. Over to Jorge for upload.
Assignee: rail → jorge
Uploaded and published. Back to Rail.
Assignee: jorge → rail
Back to :gps, I'm not sure what are the next steps here.
If this is uploaded, there's nothing left to do except verify it works. I'll call this done. Reopen if we can't install.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
I was attempting to install the hotfix via the official hotfix deployment mechanism via the dev server. But I seem to be running into the issues described in bug 1031516.
I tried installing the hotfix via the dev update server again today and can confirm it is working. You have to perform up to 3 background update checks before it gets pulled depending on what version of Firefox you are on. But it works. My Firefox 12 install pulled v20121019.01, v20130826.01, and finally v20140527.01.1.
You need to log in before you can comment on or make changes to this bug.