AutoPkgr Returning Syntax Error

Tonydig11
New Contributor III

I recently update my AutoPkgr server to 12.6 and I am not getting an error. Looks like a Python error. I did replace the "is not" with "!=" in the 2 scripts but then got a "Failed Local Trust" error. Anything I can do to get this fixed??

 

/Library/AutoPkg/JSSImporter/jss/auth.py:61: SyntaxWarning: "is not" with a literal. Did you mean "!="? if r.status_code is not 401:

/Library/AutoPkg/JSSImporter/jss/jssobject.py:531: SyntaxWarning: "is not" with a literal. Did you mean "!="? if self.can_put and self.id is not "0":

Failed local trust verification.

3 REPLIES 3

honestpuck
Contributor

Tony,

Some things to notice here.

First, it's not a syntax error, it's a warning. That means the code will run, just nag you about the `is not` syntax.

Second, "failed local trust verification" means that a recipe has changed since you last created an override for it. The logs should tell you which one. Give https://github.com/autopkg/autopkg/wiki/AutoPkg-and-recipe-parent-trust-info and https://github.com/lindegroup/autopkgr/wiki/Overrides-and-Trust-Info  a quick read.

Third, JSSImporter is now considered deprecated. Graham Pugh has developed a modern alternative, JamfUploader. Have a look at https://github.com/grahampugh/jamf-upload/wiki for details.

 

 

Tonydig11
New Contributor III

Thank you for the info.  I first removed all of my local over rides and was not able to create a new over ride. I did forget the error but said something about deprecation. So I moved to uninstalling Jamf Importer. I then attempted to install Jamf Uploader as you suggested and was presented with the error attached.

 

Screen Shot 2022-10-11 at 11.12.25 AM.png

honestpuck
Contributor

Tony,

I think you should go right back to basics.

On the command line, can you build a package from a recipe? If not, you need to figure out why and fix that. Then you need to see if you can create an override, if not why not? Fix that.

Then you can try and get JamfUploader working from the command line.

Once you have all that running you might be able to integrate it all with Autopkgr, until then Autopkgr will just get in the way. Autopkgr doesn't make it easier to get all the things working, it just hides details.