Closed
Bug 1021697
Opened 10 years ago
Closed 11 months ago
update verify fails when from and to are the same version number
Categories
(Release Engineering :: Release Automation: Updates, defect, P2)
Release Engineering
Release Automation: Updates
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: bhearsum, Unassigned)
References
Details
(Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2439] )
From bug 908134: (In reply to Nick Thomas [:nthomas] from comment #91) > Update verify needs to learn how to test build1 -> build2 partials, at the > moment the filenames are the same so we overwrite build1 with build2. We > unpack build1 (actually build2), and unsurprisingly the partial doesn't > apply on top of it.
Updated•10 years ago
|
Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2433]
Updated•10 years ago
|
Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2433] → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2439]
Comment 2•9 years ago
|
||
We've sometimes done buildN -> buildN+1 updates for the beta channel, but I think we avoid update verification failures because we update the buildID in block in <releases> in the patcher config, and never test that path. eg http://hg.mozilla.org/build/tools/rev/bc3083265318
Updated•6 years ago
|
Component: Release Automation: Other → Release Automation: Updates
Comment 3•11 months ago
|
||
We don't do build1→build2 partials, and I don't know that there are any plans to change that, so calling this wontfix.
Status: NEW → RESOLVED
Closed: 11 months ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•