Arch Linux User Repository

The update requires manual intervention once. We have news on virtualbox-ext-vnc, the same applies for this package.

https://archlinux.org/news/virtualbox-ext-vnc-7212-2-requires-manual-intervention/

Please build in a clean environment, and the version dependency is not an issue: https://wiki.archlinux.org/title/DeveloperWiki:Building_in_a_clean_chroot

7.2.14-1: extpack never gets installed, /usr/share/virtualbox/extensions/ stays empty and the hook fails with "Not a regular file: /usr/share/virtualbox/extensions/". Upstream dropped the "VM_" from the filename; package()/.install still use the old name. Please update the glob. Workaround — install straight from Oracle:

ver=$(VBoxManage --version | grep -oP '^\d+\.\d+\.\d+')
curl -O "https://download.virtualbox.org/virtualbox/${ver}/Oracle_VirtualBox_Extension_Pack-${ver}.vbox-extpack"
sudo VBoxManage extpack install --replace "Oracle_VirtualBox_Extension_Pack-${ver}.vbox-extpack"

The update requires manual intervention once. We have news on virtualbox-ext-vnc, the same applies for this package.

https://archlinux.org/news/virtualbox-ext-vnc-7212-2-requires-manual-intervention/

@Ketchup901, the point is that we shouldn't need to go through all of this nonsense if the PKGBUILD was updated correctly like @Healing_Hands suggested. Even if 1008 people say to clean build, that's deflecting the issue that is entirely with the PKGBUILD.

How to update this:

1. Clone the repo
2. Build in a clean chroot: https://wiki.archlinux.org/title/DeveloperWiki:Building_in_a_clean_chroot (just use pkgctl build)
3. Update virtualbox, skipping dependency version checks (pacman -Syd virtualbox)
4. Install the package from step 2
5. Update the rest of your system.

No need to overcomplicate things.

The PKGBUILD for this package does not follow best practices as outlined in ArchWiki. Section 4.1 of the ArchWiki page on PKGBUILD:
https://wiki.archlinux.org/title/PKGBUILD#depends

4.1 depends
An array of packages that must be installed for the software to build and run. Dependencies defined inside the package() function are only required to run the software.

Since the virtualbox package is not required to build the package, the depends line should be moved inside the package() function.

Is this dependency issue ever going to get addressed ? It still locks up pacman completely on every update, and I don't know how you could possibly argue that is intended behavior.

MartinX3, the fact that you didn't understand eworm's post doesn't make them wrong. Building in a clean chroot and adding to a local repo DOES work just fine. Your stupid helper script will not.

@eworm: Wrong, doesn't fix the issue.

I won't be able to upgrade to virtualbox 7.2.5, if virtualbox-ext-oracle 7.2.4 is still installed.

Because first system packages get upgraded and THEN AFTER AUR packages get upgraded.

To the the system upgrades won't work because the already installed old virtualbox-ext-oracle requires virtualbox 7.2.4, so I can't upgrade virtualbox to 7.2.5.

I have to remove this AUR package first, to be able to upgrade my system package virtualbox....

Please build in a clean environment, and the version dependency is not an issue: https://wiki.archlinux.org/title/DeveloperWiki:Building_in_a_clean_chroot

Also, the pinned comment suggests that a hardcoded version number isn't there when it is. It's just dynamically hardcoded instead of manually done.