New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Burn should support bundle supersedence for patch bundles #4779
Comments
Please upload logs from uninstalling patch 1.0.3.0 and post the link here.
|
As mentioned everything works fine except that after rolling back Patch 1.0.3.0, I expect Patch 1.0.2.0 to show in 'installed Updates' Uninstalling Patch 1.0.3.0 generates the following 3 files
Please let me know if more files are needed. Is there a better way to upload code, screenshots ect to this forum? Robs_Demo_Product_20150601165750.log [02D4:0954][2015-06-01T16:57:49]i001: Burn v3.9.1208.0, Windows v6.2 (Build 9200: Service Pack 0), path: C:\ProgramData\Package Cache{78f4c67f-ab2b-4777-b2ab-424ccf00fb14}\Bootstrapper1.exe, cmdline: '-burn.unelevated BurnPipe.{8E8C64F5-4392-4086-9C82-73AA1DC9D9AA} {8F22C238-3472-4FE2-B37D-20A345D54F9B} 2464 -repair -quiet -burn.ancestors={04bc6ff4-d573-4857-8e10-107edf27492a} -burn.embedded BurnPipe.{339E076E-C9AE-421F-8E36-F4141B86DFAB} {4525C8D9-EE28-4E9C-96E3-2AC9DBDA8C8B} 2616' Robs_Demo_Product_1.0.3.0_20150601165748.log [0A74:0BB4][2015-06-01T16:57:48]i001: Burn v3.9.1208.0, Windows v6.2 (Build 9200: Service Pack 0), path: C:\ProgramData\Package Cache{04bc6ff4-d573-4857-8e10-107edf27492a}\Bootstrapper1.exe, cmdline: '-burn.unelevated BurnPipe.{142CEA2D-5C80-45B5-A3FF-00A0D5C42FBD} {FDA1DF25-3C30-4A41-8514-18E0DA1BAAFC} 2616 /uninstall'
|
It's hard to tell what's going on but it looks like you have related bundles with updated .msi packages? Please post a .zip file with sample authoring and all the logs for install and patch install and patch uninstall and we can see if we can figure out what's happening. |
|
I uploaded the source of my demo project here Apart from the source, there are screenshots and log files as well.
|
The link to the uploaded demo is expiring soon, therefore I reposed the upload here
|
latest upload here
|
Burn doesn't support "bundle supersedence." When one bundle upgrades a lower-versioned bundle with the same upgrade code, the lower-versioned bundle is uninstalled. You can see that when installing 1.3: the 1.2 bundle is uninstalled with command-line switches
I'll turn this into a feature request. Bundle supersedence might be an interesting feature.
|
|
Great, thanks.
|
It's a fairly complicated change. There would have to be a new type of related bundle (BOOTSTRAPPER_RELATION_TYPE) that tells the bundle to hide itself in ARP but not uninstall itself like during a normal upgrade when it's another patch bundle that's being installed. And when a patch bundle is uninstalled, it would have to determine which patch bundle is the latest in sequence.
|
thanks bob,
|
Someone has to design and implement the feature. If you're interested in doing that, you can move the feature forward. If not, you'll be waiting for someone else to get interested enough to do the work.
|
Needs a WIP to discuss design. |
Deploying Patches via burn, supersede is on.
So far so good
Now, uninstalling Patch 1.0.3.0 -> installation reverts back to patch 2 condition, but patch 1.0.2.0 does not show in ‘view installed updates’.
This has been reported as fixed WiX v3.9 (http://wixtoolset.org/issues/4033/), but I still got the error in v3.9.1208.0
The text was updated successfully, but these errors were encountered: