Open user1233445 opened 1 year ago
It looks like AutoPkg version 2.7, which was released on 22 August, breaks JSSImporter, presumably because AutoPkg now includes a much newer version of python3. If you are still using JSSImporter, you're going to have to stay on (or revert to) an older version of AutoPkg.
The alternative to JSSImporter is JamfUploader, isn't it? I also tried to install this in autopkg, but It doesn't seem to be installed correctly. However thank you for the information.
JamfUploader is a replacement, but not a plug-in alternative. You have to learn how it works and probably write your own .jamf
recipes. I've been trying to publicise this for the past 18 months, along with the deprecation of JSSImporter.
I recommend you start here: https://github.com/grahampugh/jamf-upload/wiki/JamfUploader-AutoPkg-Processors
The setup of JamfUploader is not yet fully working in AutoPkgr. I recommend you follow the manual setup procedure as shown in the wiki above. After that, you should be able to run .jamf
recipes - just completely ignore the settings page in AutoPkgr.
Thank you very much, I will look into JamfUploader.
No problem. In the meantime you can just reinstall an older version of AutoPkg - they still work.
If anyone pushes a Pull Request that fixes this, I will implement it. I'm not going to fix and test it myself though.
I'm pretty sure I didn't muck with anything else and it's working for me, but I need to test a little more. I'll probably write .jamf
recipes in the near future, but I just don't have time right now :(
Nevermind, still broken, checking what's needed.
Hi, as soon as I install the JSSimporter or want to update a repo, I get the following error message:
Do you have an idea how I can solve this issue?