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

TeamViewer wrong version detection #173

Open
ofirgalcon opened this issue Mar 3, 2021 · 4 comments
Open

TeamViewer wrong version detection #173

ofirgalcon opened this issue Mar 3, 2021 · 4 comments
Assignees

Comments

@ofirgalcon
Copy link

It appear to download the latest version but calls it v1.0

@jpiel
Copy link

jpiel commented Mar 3, 2021

If you talk about the munki recipe, this seems to be fixed with the last version updated a few hours ago.

But i had to delete and remake the override. Probably because the parent hierarchy changed ???

@opus-nbonenberger
Copy link

@hansen-m @hjuutilainen Looks like it still does not work and is stuck in an update loop. I have deleted the repo cache on my Autopkg installation to fetch the newest Teamviewer.munki.recipe and I removed all TeamViewer from my munki Repo. After the recipe was executed, TeamViewer was again present in the muni repo, but the clients are fetching and running the pkg constantly. This is especially bugging because the TeamViewer app opens after each update run.

@hjuutilainen hjuutilainen self-assigned this Mar 8, 2021
@hjuutilainen
Copy link
Contributor

It seems that the recipe is not creating a Munki installs item correctly so Munki is expecting all of the package receipts to be present after installation. Probably some of them are skipped when installing the package and Munki keeps reinstalling it over and over again. You can correct this immediately by adding an installs item to your pkginfo (use /Applications/TeamViewer.app) or marking some of the receipts as optional. I'll update the recipe so that future AutoPkg runs will create the item correctly.

@hansen-m
Copy link
Contributor

hansen-m commented Mar 8, 2021

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