@jihem you'r new PKGBUILD send me this output :
sudo pacman -U vmware-workstation.tar.xz loading packages... error: missing package metadata in vmware-workstation.tar.xz error: 'vmware-workstation.tar.xz': invalid or corrupted package
Git Clone URL: | https://aur.archlinux.org/vmware-workstation.git (read-only, click to copy) |
---|---|
Package Base: | vmware-workstation |
Description: | The industry standard for running multiple operating systems as virtual machines on a single Linux PC. |
Upstream URL: | https://www.vmware.com/products/workstation-for-linux.html |
Keywords: | dkms ovftool player vmplayer vmware workstation |
Licenses: | custom |
Conflicts: | vmware-modules-dkms, vmware-ovftool, vmware-patch, vmware-systemd-services |
Provides: | vmware-ovftool |
Submitter: | synthead |
Maintainer: | JulianXhokaxhiu |
Last Packager: | JulianXhokaxhiu |
Votes: | 212 |
Popularity: | 3.00 |
First Submitted: | 2017-02-10 19:04 (UTC) |
Last Updated: | 2025-04-03 21:57 (UTC) |
« First ‹ Previous 1 .. 48 49 50 51 52 53 54 55 56 57 58 .. 71 Next › Last »
@jihem you'r new PKGBUILD send me this output :
sudo pacman -U vmware-workstation.tar.xz loading packages... error: missing package metadata in vmware-workstation.tar.xz error: 'vmware-workstation.tar.xz': invalid or corrupted package
@jihem Thank you. I will compare this against mine to learn why my work would not build.
@CaskAle13c Actually, I already made a PKGBUILD. If you really want it now, you can download it here: (EDIT: this link is not useful anymore)
But I didn't test it well, so you could see some bugs or missing functionalities.
@jihem I have been very frustrated by trying to update the pkgbuild myself. I keep getting "cp: target 'vmware-workstation-server/vmware-wssc-adminTool' is not a directory" errors on directory structures that are identical in version 15 to what they were in 14. It seems to get stuck here:
cp -r \ vmware-workstation/bin/ \ vmware-vmx/{,s}bin/ \ vmware-vix-core/bin/ \ vmware-vprobe/bin/ \ vmware-workstation-server/{vmware-hostd,vmware-vim-cmd,vmware-wssc-adminTool} \ #vmware-network-editor-ui/bin/ \ vmware-player-app/bin/ \ "$pkgdir/usr/bin"
Aside from the vmware-network-editor-ui/bin/* directory which I commented out. Everything in this cp block seems to be identical to v.14.
Since you may not get to it till the weekend, have you any thoughts on why it wont even build for me>
I will probably update the package this week-end, because I want to check if all functionalities work correctly and I don't have enough time for the moment.
I don't like the new icons. :(
New build is 15.0.0-10134415 Hashes for VMware-Workstation-Full-15.0.0-10134415.x86_64.bundle MD5SUM: 462e8db2a6d0df59af8ebac3af609235 SHA1SUM: a3de1f597b5facd4a8c084da5717786f88133154 SHA256SUM: 00c50710ef23a88fdff2d6c81554820d45797c62c8d72630cd2c69fd43014d94
vmware-netcfg binary doesn't seem to exist in 15. vmware-network-editor-ui/bin path no longer exists and a quick search didn't find it in the extracted bundle.
vmware-vix-core/vix-perl.tar.nogz doesn't exist anymore.
vmware-tools-freebsd are no longer included in the package.
vmmon and vmnet patches for DKMS apply. vmnet cleanly, vmmon with a line offset. vmmon and vmnet build and insmod OK.
https://blogs.vmware.com/workstation/2018/09/workstation-15-is-here.html
Check new version, (GREAT NEW ICONS!)
Just a question...
Does anyone else have to manually start networks and usbarbitrator services after update? I think it was not required before... I have this issue for several updates already :/ Or am I imagining things (meaning it was always the case)?
Regs and kudos for all the good work that goes into maintaining this!
Looks like upstream librsvg fixed the bug as of v2.44.1. VMware works again for me without the LD_LIBRARY_PATH variable set.
Pinned Comments
jihem commented on 2020-02-10 17:29 (UTC) (edited on 2021-06-19 13:19 (UTC) by jihem)
After the first installation, please:
1) install the appropriate headers package(s) for your installed kernel(s): linux-headers for default kernel, linux-lts-headers for LTS kernel...
2) reboot or load vmw_vmci and vmmon kernel modules (modprobe -a vmw_vmci vmmon)
3) Enable the services you need (using .service units to activate them during boot or .path units to activate them when a VM is started) :
vmware-networks: to have network access inside VMs
vmware-usbarbitrator: to connect USB devices inside VMs