Red Hat Bugzilla – Bug 984136
Provide MSI machine installer for client
Last modified: 2015-09-22 09:09 EDT
spin of from 885200
Mass windows deployment of spice client via msi
MSI installers are a great way for AD Administrators to deploy items like the SPICE/Desktop Viewer application to all the relevant users/systems en mass
+MSI is the recommended practice using Windows Installer mechanism.
There will be two separate .msi installers: one for mingw-remote-viewer and other for usbclerk (handled at bug 984137).
virt-viewer version scheme doesn't match very well with windows minor update mechanism. Currently, we will need to bump 0.5.6 -> 0.5.7 to perform update. We may want to switch v-v version scheme. See also this thread: https://www.redhat.com/archives/virt-tools-list/2013-July/msg00138.html
though the current MSI installs fine, upgrade is currently broken. This can be verified by taking candidate build version. After upgrade, some files will be missing such as remote-viewer.exe!
I am moving back this bug to assign, I think I know what's going on, and I will submit a new build asap.,
In case someone read this later, I think the reason is that we have multiple file in the same components (multiple files share the same generated component UUID), and we get hit by this:
This bug is currently attached to errata RHEA-2013:15512. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to
minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.
Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:
* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')
Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.
For further details on the Cause, Consequence, Fix, Result format please refer to:
Thanks in advance.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.