(onenote) Regular broken package due to different installer being downloaded

[pauby]

The automated download of OneNote results in one of two installers (it's random) being downloaded which it then calculates the checksum of. If at runtime the other installer is downloaded, the checksum is invalid and the package can't install.

See this comment.

Brain dump of how to fix this

1. During the automated install we download BOTH installers (keep retrying until we get both of them) and embed the checksum of both of them in the package.
2. Can we distribute the installers? Highly unlikely but we're clutching at straws here.
3. We pick one installer to use and at runtime try and either download that particular installer (which I'm sure was tried and didn't work) or we keep downloading until we get the right one. I prefer doing this on the 'server' end (see 1. above) rather than the client end but is an option.

I think OneNote is just a bad example of a package.

[github-actions]

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue will be closed in 14 days if it continues to be inactive.