-
Notifications
You must be signed in to change notification settings - Fork 206
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
MSOfficeMacProduct fails to download delta updates #338
Comments
Logging for later in possible fix to minimize regex use in delta: <key>Baseline Version</key>
<string>16.33.20011301</string>
<key>Update Version</key>
<string>16.36.20041300</string> |
Glad this is already created, confirming it's still an issue. Putting thought into the right way to respond... |
Ok, so we don't have an easy way with JUST the feed to tell what the most recent previous 'stable' version (at time of observation 16.43.20110804) before 'latest' (16.44.20121301), we should therefore probably just deprecate the functionality/remove that value from the set of acceptable keys for the processor to operate on. I'll spin up one that looks at macadmins.software/office_history.xml since at present the URL pointed to by the value associated with the "Location" key has a predictable format. |
Actually have code in an internal version of this processor where we get both the delta + full release capable items. I'll see if I can get it cleaned up and made public. |
Describe the problem
Using the MSOfficeMacProduct recipe/processor fails to download Delta Updates
Preferences contents
See prefs of https://gist.github.com/WardsParadox/5ef7fc32daba0f177fcd0b6411343088
(Token is sanitized to different values)
AutoPkg output
See output of https://gist.github.com/WardsParadox/5ef7fc32daba0f177fcd0b6411343088
(Token is sanitized to different values)
Expected behavior
Autopkg should download the update. Looking at the requested XML, it seems like the keys the processor is looking for are no longer there.
Version (please complete the following information):
The text was updated successfully, but these errors were encountered: