Closed
Bug 1213944
Opened 9 years ago
Closed 9 years ago
Flame FOTA builds will have to include the signature of the v4 and up for the key.
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1213824
People
(Reporter: nhirata, Unassigned)
References
Details
Attachments
(2 files)
IMG_1237.JPG
1. create an xml file to point to the FOTA build and point the device to the xml.
2. download the mar file
Expected: the device updates gecko-gaia
Actual: error sha1_check failed.
|
Reporter | |
Comment 1•9 years ago
|
||
xml file used for those interested in setting up their own test quickly.
|
|
Reporter | |
Comment 2•9 years ago
|
||
see https://bugzilla.mozilla.org/show_bug.cgi?id=1213331#c22
The variable FOTA_FINGERPRINTS="qcom/flame/flame:4.4.2/KOT49H/eng.cltbld.20150527.043015:userdebug/test-keys" needs to be added.
No longer blocks: 1211965
|
|
Reporter | |
Updated•9 years ago
|
Flags: needinfo?(catlee)
|
|
Reporter | |
Comment 3•9 years ago
|
||
Alexandre has a patch for buildbot to have the key.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
|
||
Updated•9 years ago
|
Flags: needinfo?(catlee)
|
Assignee | |
Updated•7 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•