AutoPkg repeatedly reporting 'copying' the same updates

[John Lockwood]

This is not doing any harm but according to the reports I get, Autopkg (via AutoPkgr) is copying some updates every single time it runs. Since the update is exactly the same one as previously copied it has no effect in Munki and hence no effect to users. It is however annoying and does result in a report when no actual updates has been added.

The following packages were copied:

• /Users/munkiadmin/Library/AutoPkg/Cache/local.munki.AzulZuluOpenJRE17-Intel/AzulZuluJavaJRE17_17.0.0.35_jre_x86-17.28.13.0.pkg
• /Users/munkiadmin/Library/AutoPkg/Cache/local.munki.AzulZuluOpenJRE17-ARM/AzulZuluJavaJRE17_17.0.7.7_jre_arm-17.42.19.0.pkg
• /Users/munkiadmin/Library/AutoPkg/Cache/local.munki.Microsoft Word 365/Microsoft_Word_16.73.23051401.pkg
• /Users/munkiadmin/Library/AutoPkg/Cache/local.munki.Microsoft PowerPoint 365/Microsoft_PowerPoint_16.73.23051401.pkg
• /Users/munkiadmin/Library/AutoPkg/Cache/local.munki.Microsoft Outlook 365/Microsoft_Outlook_16.73.23052700.pkg
• /Users/munkiadmin/Library/AutoPkg/Cache/local.munki.Microsoft OneNote 365/Microsoft_OneNote_16.73.23051401.pkg
• /Users/munkiadmin/Library/AutoPkg/Cache/local.munki.Microsoft Excel 365/Microsoft_Excel_16.73.23051401.pkg

Having looked closer at the Autopkg cache directories, it looks like one thing that is common to the above is that it looks like AutoPkg is redownloading the original installer each time and then generating a new pkg file also each time. In the case of the Microsoft ones, the original download was a pkg file, in the case of the Java files it was a dmg which contained a pkg.

The 'generated' pkg is an identical size but has a changed file name from the original which contains the version number of the app in question. The above list is of the generated pkgs.

I have checked the actual Munki repo and its copy has a date reflecting the first time the relevant version was added via AutoPkg, so despite what AutoPkg/Autopkgr reported it would appear it was not (re)copied.

Whilst the above report is sent by AutoPkgr I would feel that it is based on output from AutoPkg itself. Technically it has copied the original pkg each time, but clearly it has not copied it to the Munki repo since it has correctly detected that version has already been added.

This is on a Mac mini running macOS 12.6.6, Autopkg 2.7.2 and AutoPkgr 1.6

[Gregory Neagle]

“copied” is what an AutoPkg pkg recipe does if the download actually produces a package and no PkgCreator step is needed. “copied” does _not_ imply importing into your Munki repo. Items imported into your Munki repo are preceded in the summary with "The following new items were imported into Munki:”

-Greg

--
You received this message because you are subscribed to the Google Groups "autopkg-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to autopkg-discu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/autopkg-discuss/37ccf47a-2143-4bd5-9604-4fd33b87d735n%40googlegroups.com.