Closed apizz closed 3 years ago
@apizz I looked into this....a while ago (year plus?).... From everything I was able to determine, the issue is because of HP still utilizing an FTP source and the connection not being terminated correctly (if I remember correctly).
On my system, it does actually download a file, but it stays a tmp<...>
file name. If you add .pkg
to the end, it's a 100% valid and usable .pkg.
Sometimes it works for me, but most of the time it fails.
Thanks for the info. That is interesting. I tested this today and it appears to not produce the same error with AutoPkgr 1.5.4, but does produce an error with 1.5.5.
I've been seeing it for a long time.... I'll see if I can go back in history and see what versions of autopkg I've been experiencing it on.
Weird. I ran some more tests this AM and I now can't reproduce. Running latest AutoPkgr 1.5.6. Going to go ahead then and close this out.
Recently I've started to see failures with the
HPPrinterDrivers.download
recipe when run with AutoPkgr.In my testing, I can confirm that the URL based on the Product Number in the current recipe collects the desired hp printer essentials S pkg installer. However, it appears to almost immediately fail when the actual download begins. The error produced in AutoPkgr is below:
Conversely, simply
curl
ing the same URL without any flags except to output to a PKG file does not produce any errors. I can also confirm that running solely with the autopkg binary does not produce the same error.I post this here because the issue appears when running the recipe, but I'm fairly certain it's not a problem with the recipe or the shared processor.
Running the recipe solely with autopkg with the command below produces the following output: