Closed davidbpirie closed 1 month ago
Ideally you could change the version check mechanism to not curl
the binary, which I imagine could be an error-prone process in general since compiled binaries aren't made to have directly parseable text. Possible alternatives would be to query the tool itself by running /path/to/RemoteUpdateManager --help
, or to extract the Info.plist content using an Apple-supported workflow such as launchctl plist /path/to/RemoteUpdateManager
, then parsing that output. But I don't think either of these are currently offered in AutoPkg processors, so you'd have to write your own shared processor (though I could imagine that adding launchctl plist
support for Versioner would be a useful addition to that processor's functionality).
Recipe continues to fail with the above error in AutoPkg 2.7.2, but I've submitted #89 to address this issue by switching to the BinaryFileVersioner
shared processor, which uses launchctl plist
to read version data in an approved manner and avoids the curl
error in my testing.
RemoteUpdateManager.pkg is failing under AutoPkg 2.7 in the URLTextSearcher processor:
I had another mac running AutoPkg 2.3.1 and tried it there and it completed successfully, so I believe it to be caused by a change to AutoPkg which now includes Python 3.10.6 and PyObjc 8.5.