Closed Bug 1021697 Opened 11 years ago Closed 2 years ago

update verify fails when from and to are the same version number

Categories

(Release Engineering :: Release Automation, defect, P2)

defect

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.
Blocks: 908134
See Also: → 996137
Needed for release on beta.
Priority: -- → P2
Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2433]
Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2433] → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2439]
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
Component: Release Automation: Other → Release Automation: Updates

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: 2 years ago
Resolution: --- → WONTFIX
Component: Release Automation: Updates → Release Automation
You need to log in before you can comment on or make changes to this bug.