Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AutoPkgr 1.5.6 - forgets that Filewave Importer is installed #668

Closed
jaw4uz opened this issue Mar 3, 2021 · 8 comments
Closed

AutoPkgr 1.5.6 - forgets that Filewave Importer is installed #668

jaw4uz opened this issue Mar 3, 2021 · 8 comments

Comments

@jaw4uz
Copy link

jaw4uz commented Mar 3, 2021

On previous versions, the FilewaveImporter was installed and working. After updating to Autopkgr 1.5.6 the indicator shows that it is not installed.
Screen Shot 2021-03-03 at 7 35 51 AM

Clicking install returns this error message.
Screen Shot 2021-03-03 at 7 36 23 AM

I confirmed that the Filewave repo was present
Screen Shot 2021-03-03 at 7 37 09 AM

@homebysix
Copy link
Collaborator

Likely the same root cause as #665.

@jaw4uz, could you try replacing the /Library/AutoPkg/autopkg file with this one? I've got a PR open and would like to confirm whether it solves the issue you're encountering.

@jaw4uz
Copy link
Author

jaw4uz commented Mar 3, 2021

@homebysix Replacing the autopkg file worked after replacing the file I clicked on install FilewaveImporter and it installed and now shows as active. Clicking Install VirusTotalAnalyzer installed it and now it shows as active. Right clicking on a git repo and clicking "Update this repo only" now works also.

@homebysix
Copy link
Collaborator

Great, thank you for testing! I expect to release AutoPkg 2.3.1 tonight with the fix.

@jfuchtm
Copy link

jfuchtm commented Mar 4, 2021

Does not appear that the 2.3.1 build resolved this.

@jfuchtm
Copy link

jfuchtm commented Mar 4, 2021

Or I should say the FileWaveImporter still requires install everytime AutoPkgr is shutdown and reopened.

@homebysix
Copy link
Collaborator

After discussing with @shawnhonsberger we determined there are two unrelated issues, which were both reported around the same time. AutoPkg 2.3.1 resolves #666, but does not resolve this one (#668).

@shawnhonsberger
Copy link
Contributor

shawnhonsberger commented Mar 5, 2021

Hi @jaw4uz and @jfuchtm . This should be resolved in today's 1.5.7 release. Thanks for your help and patience! https://github.com/lindegroup/autopkgr/releases/latest

@blackthroat
Copy link

This is confirmed working for me now with 1.5.7. Thanks @shawnhonsberger!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants