Munki 5.7 Beta 1 Release

117 views
Skip to first unread message

Greg Neagle

unread,
May 3, 2022, 12:43:18 AM5/3/22
to 'Gregory Neagle' via munki-discuss, munki-dev

MiqViq

unread,
May 4, 2022, 6:19:44 AM5/4/22
to munki-dev
This seems not to work on macOS 10.13 High Sierra anymore?

Tested this on 2 Macs, after installing munkitools 5.7.0.4415 beta 1 on macOS 10.13 High Sierra:

An annoying GUI dialog that just comes up all the time:
Python quit unexpectedly

managedsoftwareupdate --version
Segmentation fault: 11

/usr/local/munki/Python.framework/Versions/3.10/Resources/Python.app/Contents/MacOS/Python -V
Python 3.10.4
 
Possibly some issue with PyObjC or too high minimum version when Python was built?

As standard Python 3.10 seems to work with 10.9 can we still keep the same minimum as previously, if technically possible (10.11?).

-Miq Viq
tiistai 3. toukokuuta 2022 klo 7.43.18 UTC+3 gregn...@mac.com kirjoitti:

Greg Neagle

unread,
May 4, 2022, 11:29:45 AM5/4/22
to munki-dev
Thanks for the report. It’s going to be difficult for me to test on anything below 10.14. If this isn’t a simple fix, I may just drop support for macOS < 10.14 in Munki 5.7. It’s really only me working on this!

-Greg

MiqViq

unread,
May 4, 2022, 12:53:34 PM5/4/22
to munki-dev
Hi Greg,

I think it would be OK for Munki 5.7 to support macOS 10.14+.
But if you provide newer betas I can test even down to OS X 10.11 if needed.
I have plenty of old Macs around to test on. 

-Miq Viq

Greg Neagle

unread,
May 4, 2022, 12:58:20 PM5/4/22
to munki-dev
Without a <10.14 machine to test on, or more detailed info on what exactly is failing, I would have zero idea what changes to make for “newer betas [you] can test even down to OS X 10.11”

-Greg

--
Find related discussion groups here:
https://github.com/munki/munki/wiki/Discussion-Group
---
You received this message because you are subscribed to the Google Groups "munki-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to munki-dev+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/munki-dev/81f5da79-1a76-48f7-81d4-7e6ccbd16725n%40googlegroups.com.

MiqViq

unread,
May 4, 2022, 1:03:17 PM5/4/22
to munki-dev
OK, should I create an issue in munki-github for this?
Then I could possibly provide more detailed information what is broken?

-MiqViq

Greg Neagle

unread,
May 4, 2022, 1:04:32 PM5/4/22
to munki-dev
That would probably be good.

-Greg

Beth Shirk

unread,
May 4, 2022, 3:37:05 PM5/4/22
to 'Greg Neagle' via munki-dev
I’m seeing the same issue in 10.14 (though not 10.15). Same symptoms that MiqViq reported below. 

I’ll keep my eyes open for a Github issue and can provide more information there.

- Beth


MiqViq

unread,
May 4, 2022, 3:54:50 PM5/4/22
to munki-dev
Sorry but I am too lazy to make this an github-issue...

I tested building relocatable_python (I changed the pyobjc-requirement only, I did not change other pip requirements) using included bash-script and found out the following:

Crashes on macOS 10.13.6
pyobjc==8.2

OK on macOS 10.13.6
pyobjc==8.5
pyobjc==8.4
pyobjc==8.3
pyobjc==8.1
pyobjc==7.3

OK means that managedsoftwareupdate --version gives valid output, other thatn that I do not know...

Test builds were done both on macOS 11.6.5 and macOS 10.15.7.

Maybe it is safe to use pyobjc==8.5 wiht the next beta?

-MiqViq

MiqViq

unread,
May 4, 2022, 4:15:39 PM5/4/22
to munki-dev
..and I can confirm that 5.7 beta 1 with pyobjc 8.2 crashes on Mojave too.

-MiqViq

Greg Neagle

unread,
May 4, 2022, 5:11:29 PM5/4/22
to munki-dev
Thank you for this.

I tried building a new Python.framework with PyObjC==8.5 and encountered this issue (under Xcode 13.2.1/macOS 12.3.1/Apple silicon):

  error: subprocess-exited-with-error

  

  × Running setup.py install for pyobjc-framework-ScreenCaptureKit did not run successfully.
  exit code: 1
  ╰─> [25 lines of output]
      running install
      running build
      running build_py
      overriding build_packages to copy PyObjCTest
      creating build
      creating build/lib.macosx-10.9-universal2-3.10
      creating build/lib.macosx-10.9-universal2-3.10/ScreenCaptureKit
      copying Lib/ScreenCaptureKit/_metadata.py -> build/lib.macosx-10.9-universal2-3.10/ScreenCaptureKit
      copying Lib/ScreenCaptureKit/__init__.py -> build/lib.macosx-10.9-universal2-3.10/ScreenCaptureKit
      creating build/lib.macosx-10.9-universal2-3.10/PyObjCTest
      copying PyObjCTest/test_scshareablecontent.py -> build/lib.macosx-10.9-universal2-3.10/PyObjCTest
      copying PyObjCTest/test_screencaputurekit.py -> build/lib.macosx-10.9-universal2-3.10/PyObjCTest
      copying PyObjCTest/test_scerror.py -> build/lib.macosx-10.9-universal2-3.10/PyObjCTest
      copying PyObjCTest/__init__.py -> build/lib.macosx-10.9-universal2-3.10/PyObjCTest
      copying PyObjCTest/test_scstream.py -> build/lib.macosx-10.9-universal2-3.10/PyObjCTest
      running build_ext
      building 'ScreenCaptureKit._ScreenCaptureKit' extension
      creating build/temp.macosx-10.9-universal2-3.10
      creating build/temp.macosx-10.9-universal2-3.10/Modules
      clang -Wno-unused-result -Wsign-compare -Wunreachable-code -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -arch arm64 -arch x86_64 -g -I/Users/Shared/munki-git/munki/Python.framework/Versions/3.10/include/python3.10 -c Modules/_ScreenCaptureKit.m -o build/temp.macosx-10.9-universal2-3.10/Modules/_ScreenCaptureKit.o -Wno-deprecated-declarations -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.1.sdk -DPyObjC_BUILD_RELEASE=1201 -Werror
      Modules/_ScreenCaptureKit.m:7:9: fatal error: 'ScreenCaptureKit/ScreenCaptureKit.h' file not found
      #import <ScreenCaptureKit/ScreenCaptureKit.h>
              ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      1 error generated.
      error: command '/usr/bin/clang' failed with exit code 1
      [end of output]

  

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: legacy-install-failure

× Encountered error while trying to install package.
╰─> pyobjc-framework-ScreenCaptureKit

note: This is an issue with the package mentioned above, not pip.
hint: See above for output from the failure.
Traceback (most recent call last):
  File "/tmp/relocatable-python-git/make_relocatable_python_framework.py", line 108, in <module>
    main()
  File "/tmp/relocatable-python-git/make_relocatable_python_framework.py", line 94, in main
    install_extras(
  File "/private/tmp/relocatable-python-git/locallibs/install.py", line 109, in install_extras
    install_requirements(requirements_file, framework_path, version)
  File "/private/tmp/relocatable-python-git/locallibs/install.py", line 74, in install_requirements
    subprocess.check_call(cmd)
  File "/Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.8/lib/python3.8/subprocess.py", line 364, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/Users/Shared/munki-git/munki/Python.framework/Versions/3.10/bin/python3.10', '-s', '-m', 'pip', 'install', '-r', '/Users/Shared/munki-git/munki/code/tools/py3_requirements.txt']' returned non-zero exit status 1.

"ScreenCaptureKit” is not required for Munki to function, but it would be nice to get a clean build, if for no other reason than eliminating questions/issues from people running `make_munki_mpkg.sh`.

I’ll try PyObjC==8.4 next.

-Greg

Greg Neagle

unread,
May 4, 2022, 5:47:28 PM5/4/22
to munki-dev
Also seeing this with PyObjC 8.5:

$ sudo managedsoftwareupdate
Traceback (most recent call last):
  File "/usr/local/munki/managedsoftwareupdate", line 59, in <module>
    from munkilib import appleupdates
  File "/usr/local/munki/munkilib/appleupdates/__init__.py", line 5, in <module>
    from .core import *
  File "/usr/local/munki/munkilib/appleupdates/core.py", line 23, in <module>
    from . import au
  File "/usr/local/munki/munkilib/appleupdates/au.py", line 43, in <module>
    from . import dist
  File "/usr/local/munki/munkilib/appleupdates/dist.py", line 33, in <module>
    from LaunchServices import LSFindApplicationForInfo
ModuleNotFoundError: No module named 'LaunchServices'


Greg Neagle

unread,
May 4, 2022, 7:36:08 PM5/4/22
to munki-dev
All right. After a lot of trial-and-error, I have a build of Munki 5.7 with PyObjC 8.5. It seems to work as expected under macOS 10.14.6, whereas an install of 5.7.0.4415 (Beta 1) fails with "Segmentation fault: 11”. No testing on macOS < 10.14 as I don’t currently have access to a machine I can test.

I’ll have a new Beta 2 available shortly.

-Greg

MiqViq

unread,
May 5, 2022, 2:06:33 AM5/5/22
to munki-dev
Hi Greg,

I tested the latest munkitools 5.7 b2 on various macOS versions.
Testing was done only using command managedsoftwareupdate --version.

10.15.7 Catalina - OK
11.6.5 Big Sur - OK
12.3.1 Monterey - OK

All these older systems returned munki version without Segmentation Fault 11-error and are probably OK too:
10.11.6 El Capitan - OK
10.12.6 Sierra - OK
10.13.6 High Sierra - OK
10.14.6 Mojave - OK


-MiqViq

Greg Neagle

unread,
May 5, 2022, 11:00:26 AM5/5/22
to munki-dev, 'Gregory Neagle' via munki-discuss
Thanks for this update. It would be extraordinarily helpful to have test results for more than `managedsoftwareupdate —version`. I tested both `managedsoftwareupdate` and `managedsoftwareupdate —installonly` on a test Mojave machine (and they worked as expected).

Readers: please test!

-Greg

Beth Shirk

unread,
May 5, 2022, 11:20:27 AM5/5/22
to via munki-discuss, munki-dev
I tested b2 on 10.12.6 and 10.14.6, launching Managed Software Center and installing and uninstalling an app while viewing the log. Looked and functioned as expected, no errors.

I figure it’s safe to assume that 10.13.6 would be fine as well.

I don’t have access to an 10.11.6 VM (I tried but my version of Fusion just laughed at me).

Thanks for this fix, Greg.

- Beth

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/B2DFE3FF-B246-4DF8-9FA1-C0274A53A9BD%40mac.com.

Greg Neagle

unread,
May 5, 2022, 11:23:07 AM5/5/22
to munki-...@googlegroups.com, munki-dev
Thanks for the testing.

There have really almost no changes to Managed Software Center.app and MunkiStatus.app since 5.6.4, and they are Swift apps anyway, and would not be affected by the Python and PyObjC changes. It’s the command-line tools that seem to have been affected, and will require the most testing.

-Greg

Beth Shirk

unread,
May 5, 2022, 12:35:26 PM5/5/22
to munki-dev, via munki-discuss
Makes sense. I tested managedsoftwareupdate with the following options on both 10.12.6 and 10.14.6 and found no issues:

—checkonly (with varying levels of verbosity)
—installonly
—quiet
—show-config
—set-bootstrap-mode
—clear-bootstrap-mode

- Beth

MiqViq

unread,
May 6, 2022, 3:23:41 AM5/6/22
to munki-dev
 I tested managedsoftwareupdate with the following options on 10.11.6, 10.12.6 and 10.13.6 and did not find any issues:

--checkonly -vvvvv
--installonly
--auto
--show-config
--set-bootstrap-mode
--clear-bootstrap-mode

Also MSC GUI seems to work ok, did not test all possible scenarios with GUI app.

-MiqViq

MiqViq

unread,
May 6, 2022, 3:24:50 AM5/6/22
to munki-dev
And my testing on legacy OS versions was done with munki 5.7.b2

-MiqViq
Reply all
Reply to author
Forward
0 new messages