Version detection question #938
jelockwood
started this conversation in
General
Replies: 2 comments 1 reply
-
Isn’t this more of a Munki issue?
And, you’re likely hitting something like: https://github.com/munki/munki/wiki/FAQ#q-i-keep-seeing-warnings-like-warning-could-not-process-item-office2011_update-1442-for-update-no-pkginfo-found-in-catalogs-production-yet-there-is-definitely-an-item-named-office2011_update-1442-in-the-production-catalog-what-is-happening
Regards,
Ben.
[Jamf]<https://www.jamf.com/>
Ben Toms
Principal Software Engineer
Remote, UK
[Phone]
0800 368 9330
[Email]
***@***.******@***.***>
[Web]
www.jamf.com<https://www.jamf.com/>
[Facebook]<https://www.facebook.com/jamfsoftware/> [Twitter] <https://twitter.com/JamfSoftware> [LinkedIn] <https://www.linkedin.com/company/jamf-software> [Jamf YouTube] <https://www.youtube.com/user/jamfmedia>
From: jelockwood ***@***.***>
Date: Wednesday, 17 April 2024 at 10:01
To: autopkg/autopkg ***@***.***>
Cc: Subscribed ***@***.***>
Subject: [autopkg/autopkg] Version detection question (Discussion #938)
In the Mac world at least it is more common for version numbers of software to use a format like 1.0, 1.1, 1.2.1, etc.
A tool for which I have previously written an AutoPkg recipe called Smartmontools however uses a format like 7.4, and 7.4-1
This has resulted in my recipe treating both as 7.4 with the -1 portion being skipped.
Whilst arguably the developer is using the wrong format :) does anyone have a suggestion for how to handle this in a set of AutoPkg recipies?
See - https://github.com/jelockwood/recipes/tree/master/SMART%20Monitoring
and - https://sourceforge.net/projects/smartmontools/files/
—
Reply to this email directly, view it on GitHub<#938>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AASZZTTANIBDD5IWXEWLG5LY5Y27BAVCNFSM6AAAAABGK4F3RGVHI2DSMVQWIX3LMV43ERDJONRXK43TNFXW4OZWGUYTQMJZGI>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
-
It's not a Munki issue:
It's more likely he's describing the issue with the PkgCreator processor that is quite opinionated about what are legal characters in a package version, but I'd invite @jelockwood to elaborate. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
In the Mac world at least it is more common for version numbers of software to use a format like 1.0, 1.1, 1.2.1, etc.
A tool for which I have previously written an AutoPkg recipe called Smartmontools however uses a format like 7.4, and 7.4-1
This has resulted in my recipe treating both as 7.4 with the -1 portion being skipped.
Whilst arguably the developer is using the wrong format :) does anyone have a suggestion for how to handle this in a set of AutoPkg recipies?
See - https://github.com/jelockwood/recipes/tree/master/SMART%20Monitoring
and - https://sourceforge.net/projects/smartmontools/files/
Beta Was this translation helpful? Give feedback.
All reactions