Closed
Bug 1322664
Opened 8 years ago
Closed 7 years ago
Add entries to browser/installer/removed-files.in to facilitate 32bit -> 64bit Windows upgrades
Categories
(Release Engineering :: Release Requests, defect)
Release Engineering
Release Requests
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: nthomas, Assigned: nthomas)
References
Details
This is to figure out if we need to modify removed-files.in to smooth these architecture changing updates. There are two cases that might need handling: * partial updates, eg I built a 49.0.2 win32 --> 50.0.2 win64 partial, and the manifest had these extra lines (compared to the win64 -> win64 case): +add "qipcap64.dll" +remove "wow_helper.exe" +remove "breakpadinjector.dll" +remove "D3DCompiler_43.dll" ** this should work fine as is, but need to check if this would have left anything else behind after the partial was applied * complete updates may need the three remove instructions above. IIRC the updater will remove the files listed in the (already on disk) precomplete file, cleaning up the existing install before adding the new files in complete mar. So this could be a no-op too. Testing of actual updates required. Leaving this in a RelEng component until we know what is needed.
Comment 1•8 years ago
|
||
You shouldn't need to add any entries to removed-files.in and this bug should be wontfix If you create a partial, the files in the x64 build will be compared to the files in the x86 build. This will automatically create remove instructions. When the client gets the complete the precomplete file will the remove instructions.
Comment 2•8 years ago
|
||
(In reply to Robert Strong [:rstrong] (use needinfo to contact me) from comment #1) >... > When the client gets the complete the precomplete file will the remove > instructions. When the client gets the complete the precomplete file will add the remove instructions.
Assignee | ||
Comment 3•8 years ago
|
||
Fantastic. This was just filed out of an (over) abundance of caution, and maybe should have been title 'test 32 -> 64bit updates to look for anything strange'.
Comment 4•7 years ago
|
||
WONTFIX as per Robert's comment 1. We will just need to verify that the generated remove instructions work correctly we test the upgrade.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
Assignee | ||
Comment 5•7 years ago
|
||
How/where are we recording that we will do that check ?
Comment 6•7 years ago
|
||
(In reply to Nick Thomas [:nthomas] from comment #5) > How/where are we recording that we will do that check ? We will have a manual test plan for Softvision QA and we can include these checks. I'll make sure you have the opportunity to review the test plan so we describe the checks correctly.
Comment 7•7 years ago
|
||
Note: I suggest doing a diff of a 64 bit install against an install that has updated from 32 to 64 bit. Off the top of my head the only files that should be different are the install.log, uninstall.log, and the uninstall.update files.
You need to log in
before you can comment on or make changes to this bug.
Description
•