-
-
Notifications
You must be signed in to change notification settings - Fork 44
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
Is the default yum repo path correct? #49
Comments
I see new bits in |
It appears that since version 10 of vmware tools, new releases of vmware tools are no longer linked to versions of ESX. At the same time, the release directory only contains version 10.x releases. It'd be nice if they'd updated some docs in https://packages.vmware.com/tools/docs/manuals/index.html or provided a clear explanation in an updated https://packages.vmware.com/tools/versions |
Good find. That explains things. I guess for now we could have |
VMware have changed the layout of packages.vmware.com necessitating a change to this module to use the new location for the latest package releases. This PR could however break users who are specifying releases before version 10, so you might want to build a more complicated change which checks the specified version if there is one and selects either esx/$version or releases/$version...
Hi
From what I can tell, (for RHEL6) the module is using
https://packages.vmware.com/tools/esx/latest/rhel6/x86_64/index.html
It appears these packages haven't been updated since August?
Have vmware done some reorganising?
Perhaps
https://packages.vmware.com/tools/releases/latest/rhel6/x86_64/index.html is the correct url these days?
Not sure.
The text was updated successfully, but these errors were encountered: