| Summary: | Make MSI pass validation without warnings/errors | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | Marc Bauer <marc.bau> |
| Component: | Installation | Assignee: | Not Assigned <libreoffice-bugs> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | critical | CC: | michael.meeks, timar74 |
| Priority: | medium | ||
| Version: | 4.0.1.2 release | ||
| Hardware: | All | ||
| OS: | Windows (All) | ||
| Whiteboard: | |||
| Crash report or crash signature: | Regression By: | ||
| Attachments: | MSI Validation bugs | ||
|
Description
Marc Bauer
2013-03-26 11:09:27 UTC
Created attachment 77044 [details]
MSI Validation bugs
MSI Validation bugs
Hi Marc, - is there anything that is stopping you actually install & use the MSI file however - does anything really break ? :-) IIRC we bundle a large number of languages which can cause some issues and is on the limit of what MSI can support. Andras may have some input on the warnings too - anything jump out at you as being actually problematic there Andras ? Setup is completly broken. I cannot add the MSI to a GPO. So to be clear - all is completly broken. See https://bugs.freedesktop.org/show_bug.cgi?id=62758 Start fixing validation bugs can be seen as a start point to get the issues solved. This includeds using invalid LCIDs of Valencia that should be LCID 2051 and not 3xxxx (In reply to comment #3) > Start fixing validation bugs can be seen as a start point to get the issues > solved. This includeds using invalid LCIDs of Valencia that should be LCID > 2051 and not 3xxxx The Valencian LCID (introduced in Windows 8) was corrected on the other day in master. On the other hand, invalid language codes in MSI are mostly harmless. I do not want to go through of the long list you attached, but none of those errors/warnings caused your deployment problem. See the answer in bug 62757. This is not an invalid bug report. There are tons of validation errors and if you think they are harmless or not, they are still valid bugs that need to be fixed. No, they are not valid bugs. Creating a working installer and creating a warning/error free installer are two separate things. It is not possible to pass all ICE tests. For example we need to install 64-bit components, while the installer is marked as 32-bit. Even merge modules from Microsoft (VC runtime modules) are not warning free. Also, ICE33: FOO contexts should be registered via the BAR table. What if I rework the whole installer to pass this test? I would spend 1-2 days for nothing. The registry settings will be set either way. |