Closed
Bug 453572
Opened 16 years ago
Closed 16 years ago
packaging updates found by package-compare
Categories
(SeaMonkey :: Installer, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
seamonkey2.0a1
People
(Reporter: kairo, Assigned: kairo)
References
Details
Attachments
(1 file)
4.58 KB,
patch
|
mcsmurf
:
review+
standard8
:
approval-seamonkey2.0a1+
|
Details | Diff | Splinter Review |
The new package-compare target introduced by bug 451185 uncovered a few errors in esp. the Windows package manifest. Those are mainly files we list that don't exist any more, but we should correct that manifest even if our packages aren't actually wrong.
![]() |
Assignee | |
Comment 1•16 years ago
|
||
Here's the patch to fix up both the Windows manifest and the removed-files.in file.
Attachment #336763 -
Flags: review?
![]() |
Assignee | |
Updated•16 years ago
|
Attachment #336763 -
Flags: review? → review?(bugzilla)
Updated•16 years ago
|
Attachment #336763 -
Flags: review?(bugzilla) → review+
Comment 2•16 years ago
|
||
Comment on attachment 336763 [details] [diff] [review] fix up the packages files and removed-files.in Keep the nsAxSecurityPolicy.js entry, it's still in the tree and is included when activex is built (in some cases). Rest looks good.
![]() |
Assignee | |
Updated•16 years ago
|
Attachment #336763 -
Flags: approval-seamonkey2.0a1?
Comment 3•16 years ago
|
||
Comment on attachment 336763 [details] [diff] [review] fix up the packages files and removed-files.in I think these are low risk, testing should pick up any obvious mistakes (not that there appear to be any), and I believe having the appropriate files in removed-files.in will protect against problems if anyone should decide to install it in the same directory as SM 1.x or earlier.
Attachment #336763 -
Flags: approval-seamonkey2.0a1? → approval-seamonkey2.0a1+
![]() |
Assignee | |
Comment 4•16 years ago
|
||
Pushed as http://hg.mozilla.org/comm-central/rev/a993f310afb4
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•