-
Notifications
You must be signed in to change notification settings - Fork 7
KeyError on package with leading zero's #29
Comments
It looks like it's the call to LooseVersion (packaging.version import parse as LooseVersion) that's modifying the string. I tweaked get_newest_package() to print out version before and after calling LooseVersion: `def get_newest_pkg(options):
And I got the following:
Because version has been changed it's then not a key in versions. From doing a bit of reading it seems that packaging.version.parse splits the string on "." and then converts to int. At that point 00 becomes 0 and version is now not a key in the versions dict. Not sure how that can be fixed though. |
I may be able to use |
Thanks Graham, your work is much appreciated. |
This issue persists on the general 2.2.0 release:
Is this the same problem as the adobe issue from my initial bug report, or a separate one? |
Is there anything I can do to help this issue progress? |
Are you prepared to have AutoPkg as a dependency for jss_helper? |
@grahampugh for me, it wouldn't be a problem. Their use is not independent in my environment |
@krispayne please try https://github.com/jssimporter/jss_helper/releases/tag/2.2.1b1 (no package yet, but the only file that changed is |
Looks like the new tools.py lib worked in the case I was having with Zoom above. Let me demote the adobe policy and test that one, too |
👍 The original adobe policy also works. Thanks! |
The package is
Adobe Acrobat DC-20.006.20034.pkg
going toAdobe Acrobat DC-20.006.20042.pkg
This is the first time I've had issues with Acrobat in this regard. Maybe something is different about the way that version numbers are interpreted in the new version of jss_helper?
The text was updated successfully, but these errors were encountered: