Missing minimum_os_version in pkginfo

[David Vandenborn]

Hi,

I recently started using Munki 7 (version 7.0.3) on macOS 26.1.

When importing a .pkg file, I noticed that the generated pkginfo no longer includes the minimum_os_version key if the OS version isn’t defined in the installer package.

This behavior appears with Microsoft installer packages such as CompanyPortal-Installer.pkg and Microsoft_AutoUpdate_4.81.25111027_Updater.pkg.

However, when importing a .dmg that contains an application, the minimum_os_version key is still generated as expected.

Is this change by design or is it a bug?

Additional details that may be relevant:
- The repo already contained previous versions of these packages.
- The Microsoft packages have never included a proper minimum OS version. When importing them in Munki 6, the key was automatically generated with the value 10.15.
- Example package (Microsoft Edge): https://go.microsoft.com/fwlink/?linkid=2093504

David

[Gregory Neagle]

I’m curious what your expectation is here. If a package does not include a minimum OS version, what would you expect `makepkginfo` to make up as the minimum OS version?

-Greg

> --
> 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 visit https://groups.google.com/d/msgid/munki-discuss/3A890B97-3F7C-4BE9-BC65-7FC27A6878E3%40yahoo.com.

[Gregory Neagle]

I just downloaded your example package, and ran both Munki 7 and Munki 6’s `makepkginfo` against it.

The pkginfo generated by Munki 7’s `makepkginfo` did not have a minimum_os_version key/value.

The pkginfo generated by Munki 6’s `makepkginfo` did have minimum_os_version:

<key>minimum_os_version</key>
<string>10.5.0</string>

In 2025 that’s not particularly _useful_, and I bet it’s also _wrong_, in that I really doubt Microsoft Edge 142.0.3595.65 runs on Mac OS X 10.5.

So I think the current behavior is arguably an improvement: Munki doesn’t know what the minimum os version is, and doesn’t guess.

There was a historical reason for the minimum_os_version of “10.5.0”. I started writing was would become Munki back when we had a fair number of macOS 10.4.x and macOS 10.5.x machines. macOS 10.5 introduced “flat” packages, and these could not be installed by macOS 10.4’s Installer. So it was useful (at the time) to flag any flat packages as requiring a minimum OS of 10.5. Here in 2025, that’s not particularly useful.

-Greg

[David Vandenborn]

Hi Greg,

So I think the current behavior is arguably an improvement: Munki doesn’t know what the minimum os version is, and doesn’t guess.

I’m completely fine with the new behavior. It’s good to know that the absence of the minimum_os_version key is intentional.

I had gotten used to editing the default value of 10.5.0 when importing packages that didn’t specify an OS version.

Going forward with Munki 7, I’ll just add the key manually if it’s missing.

David Vandenborn

-- 
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 visit https://groups.google.com/d/msgid/munki-discuss/697E3A6F-E335-43FA-BDF1-6C75ADFC1BC0%40mac.com.

[Patrick Gallagher]

Autopkg recipes often include this value. 

Sent from Gmail Mobile

To view this discussion visit https://groups.google.com/d/msgid/munki-discuss/1239C3E3-FBEC-4965-9228-983B8F8631A2%40yahoo.com.

[Alan]

I did some spot-checking on a few Munki AutopPkg recipes, and it seems most of those specified minimum_os_versions aren't 10.5.

To view this discussion visit https://groups.google.com/d/msgid/munki-discuss/CAF4aQ0Tgm9hXw-FxsO_GjE%2Br6byr6v-U-md%3Dp_nA%3Dj6pqr9%3DPg%40mail.gmail.com.