@samueldy fixed, thanks for reporting.
When updating to 7.2.6-1, hashes are wrong for some files:
==> Validating source files with sha256sums...
VirtualBox-7.2.6-172322-Linux_amd64.run ... Passed
VirtualBoxSDK-7.2.6-172322.zip ... Passed
VBoxAuth-g72af1bf.h ... FAILED
VBoxAuthPAM-g72af1bf.c ... FAILED
VBoxAuthSimple-g72af1bf.cpp ... FAILED
dkms.conf ... Passed
vboxreload ... Passed
60-vboxdrv.rules ... Passed
vboxweb.service ... Passed
virtualbox.modprobe ... Passed
virtualbox.sysusers ... Passed
LICENSE.sdk ... Passed
013-Makefile.patch ... Passed
==> ERROR: One or more files did not pass the validity check!
@Xiaozhu1337 sorry, but CachyOS is not supported. Please seek help in your distribution support channels. At the time of writing, the Arch Linux linux package is at version 6.14, and everything is working fine.
Hi mikaelblomkvists, "pamac" is unsupported software, so you need to know how to use it. Btw. yaourt, yet another unsupported AUR helper, is outdated since years, but still gets the correct version.
• rocketmouse@archlinux ~
$ yaourt -S virtualbox-bin
==> Downloading virtualbox-bin PKGBUILD from AUR...
x .SRCINFO
x 013-Makefile.patch
x 60-vboxdrv.rules
x LICENSE.sdk
x PKGBUILD
x dkms.conf
x vboxreload
x vboxweb.service
x virtualbox.sysusers
virtualbox-bin 7.1.2-1 (Tue 18 Aug 11:16:55 CEST 2015)
[snip]
You are the packager set by the PACKAGER variable in /etc/makepkg.conf .
FWIW if building a package from AUR fails, then before writing a comment, you not only need to build without an AUR helper, you even must build in a clean chroot.
Regards, Ralf
@dbermond here you have, the command pamac info virtualbox-bin-guest-iso returns among other what's below. The packager information is missing. Upgrading this package brings no effect, I upgraded it 5 times already, and it keeps showing as the older 7.1.0-1.
pamac info virtualbox-bin-guest-iso
Name : virtualbox-bin-guest-iso
...
Version : 7.1.0-1
...
Packager : Unknown Packager
Maintainer : dbermond
@mikaelblomkvists sorry, but I could not understand anything that you mean. Patching the package too much? My name is not at metadata? Pacman does not warn about updates for AUR packages, so it looks like you are using something unsupported, like an AUR helper or a distribution other than Arch Linux.
When you patch too much, so that you patch own version identifier, then you hacked a package manager.
This package claims its version is 7.1.2-1 but in fact the version that gets installed is 7.1.0-1. I updated it 4 times already, but the package manager still claims there is an update for this package available.
@dbermond your name is not present the package metadata btw.
@sf1nk5 @whmblr I could reproduce your issue, and the segmentation fault you were getting should be fixed now after the last update.
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。
Notice:
To avoid crashes when upgrading Guest Additions from version 6.x to 7.x on Windows guests, uninstall the old Guest Additions first, then reboot, and then install the new ones. It's recommended to do all these operations in Safe Mode. See this upstream bug ticket for more details.