Issue with new .PKG #140

Closed
opened 2026-01-19 18:31:40 +00:00 by michael · 2 comments
Owner

Originally created by @jladders on GitHub.

I am using 1.0RC-322 with no issues.

I have just uploaded 1.0-368 and it's just skipped through everything. Back to 1.0RC-322 and fine again.

Was hoping not to test every .PKG every time it came out.

Originally created by @jladders on GitHub. I am using 1.0RC-322 with no issues. I have just uploaded 1.0-368 and it's just skipped through everything. Back to 1.0RC-322 and fine again. Was hoping not to test every .PKG every time it came out.
Author
Owner

@scriptingosx commented on GitHub:

I believe, as an admin, it is our job to test everything every time there is an update, especially when it is a free tool that is provided "as is."

That said, can you share the log?

@scriptingosx commented on GitHub: I believe, as an admin, it is our job to test _everything_ _every time_ there is an update, especially when it is a free tool that is provided "as is." That said, can you share the log?
Author
Owner

@jladders commented on GitHub:

Very true, you are right it is good practise.

Let me see if I can get you something this week

@jladders commented on GitHub: Very true, you are right it is good practise. Let me see if I can get you something this week
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: jamf/Setup-Manager#140