GitHub - rmanly/nonmounted-dmg-autopkg-fix: A fix for the dmg mounting errors found during an autopkg run.

rmanly / nonmounted-dmg-autopkg-fix Public

Notifications You must be signed in to change notification settings
Fork 0
Star 2

A fix for the dmg mounting errors found during an autopkg run.

Notifications

Name		Name	Last commit message	Last commit date
Latest commit History 15 Commits
sample hdiutil output		sample hdiutil output
README		README
detach_nonmounted_dmg.py		detach_nonmounted_dmg.py
org.glenbrook225.detach_nonmounted_dmg.plist		org.glenbrook225.detach_nonmounted_dmg.plist

Repository files navigation

This script is intended to stop the dmg mounting errors encountered from time to time during autopkg recipe runs. 

The following snippet is an example generated via AutoPkgr's email notification system.

'Error in local.munki.glenbrook225.Motion: Processor: MunkiImporter: Error: creating pkginfo for /Volumes/Storage/AutoPkg/Cache/local.munki.glenbrook225.Motion/Motion-5.4.dmg failed: Could not mount /Volumes/Storage/AutoPkg/Cache/local.munki.glenbrook225.Motion/Motion-5.4.dmg!'

It works by checking the output of the `hdiutil info` command to see if dmgs are mounted or not. If the dmg info is available but not mounted then this is probably an error and the script will attempt to detach the device associated with the dmg.

I intend to run this on my autopkging computer an hour or so before AutoPkgr runs every morning in order to ensure a clean run.