My story:
With b1, I had a significant number of apps that would not update with munki (I can’t remember the number now but it was in the low double-digits — not every single application failed to update.)
When b2 came out, I did an EACS install and clean installed our 300+ apps and as the weeks after that went by ended up with a much smaller number of apps (only 4) that would not update (most updated — including ones that would not update under b1. Microsoft Edge was one that was a problem in b1 *and* b2 (but, frustratingly, not all the time, but often enough on multiple computers).
When b3 came out, I updated from b2 to b3 — and those 4 app updates installed without issue. Though, admittedly, I did not try relaunching those 4 apps *again* after the update to b3 — I just ran munki to see if the 4 apps would update — and they did.
I then EACS’ed b3 today and installed the 300+ apps we deploy here.. We have 18 specific apps in “testing”, so I launched the older “production” versions of those 18 after the EACS, switched the catalogs to testing — and ran munki and — 17 of the 18 apps updated (I was honestly disappointed one was left…and it was *not* Edge...)
We made no changes to anything munki-related here — it’s exactly the same stock munki version/configuration we’ve been using since your last public release, but this one update has the same “Error -1” I would see in /var/log/install.log that the other apps generated when they failed to install:
2022-07-07 19:21:59-04 ultron shove[3049]: Error relinking file (primary): /Library/InstallerSandboxes/.PKInstallSandboxManager/DE10B3B0-25AB-4BCE-BC0F-FDADC81D7250.activeSandbox/Root/Applications/Resolume Wire/Wire.app/Contents/_CodeSignature/CodeResources to /Applications/Resolume Wire/Wire.app/Contents/_CodeSignature/CodeResources, error = 1
So we don’t know if Apple is loosening the app update restrictions now for specific applications as they get reported or what. I’m hoping they post something in future developer notes to indicate what the plans are.
All that said in a round-about, long-winded way: I’m suggesting that if you held on to the full installers of b1 and b2 (Mr. Macintosh’s web site still has links if they are still valid?) — you might be able to replicate the initial issue with b1 (or b2?) to see if your munki change works there? From my experience, b1 was the most problematic, b2 got better and (so far) b3 is even better.
- Steve
> You received this message because you are subscribed to the Google Groups "munki-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to
munki-discus...@googlegroups.com.
> To view this discussion on the web visit
https://groups.google.com/d/msgid/munki-discuss/0B0CA4FC-4555-4B60-809F-CA3D760AB0D2%40mac.com.