Arch Linux User Repository

There is no version dependency on this package on purpose! You could read comments back from 2011 to understand why.

@ram Never expect miss-matched ext packs to work. The real solution there would have been to upgrade your virtualbox rather than downgrade this, but that just shows you have your system in some unsupported partial-upgrade scenario. Downgrading this to match worked but the important point isn't that their is anything wrong with the new version, just that they have to match.

hi! happy 2022!

I had problems with usb-ehci not working using vbox 6.1.30 and ext-oracle 6.1.32. manual downgrade to ext-oracle 6.1.30 made it work.

cheers + happy hacking

For those interested, here is a patch that should apply cleanly via git am to almost any version of this package (it should rebase easily on the master branch even when it gets bumped) that will version lock the built package to VB:

From 5fa2ca3d0511ef0d15075705b6d396f3dfe5df09 Mon Sep 17 00:00:00 2001
From: Caleb Maclennan <caleb@alerque.com>
Date: Tue, 18 Jan 2022 16:05:31 +0300
Subject: [PATCH] Lock to matched version

Signed-off-by: Caleb Maclennan <caleb@alerque.com>
---
 PKGBUILD | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/PKGBUILD b/PKGBUILD
index 9bbb182..4416794 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -7,13 +7,14 @@ pkgdesc='Oracle VM VirtualBox Extension Pack'
 arch=('any')
 url='https://www.virtualbox.org/'
 license=('custom:PUEL')
-depends=('virtualbox')
+depends=("virtualbox=$pkgver")
 optdepends=('rdesktop: client to connect vm via RDP')
 options=('!strip')
 install=virtualbox-ext-oracle.install
 source=("https://download.virtualbox.org/virtualbox/$pkgver/Oracle_VM_VirtualBox_Extension_Pack-$pkgver.vbox-extpack")
 noextract=("Oracle_VM_VirtualBox_Extension_Pack-$pkgver.vbox-extpack")
 sha256sums=('ba9dd35434c5cac3b99c53708b10ab07fa8a2fb2995b4515ad81f2d7c465c5ec')
+pkgrel=$pkgrel.1

 prepare() {
   # shrink uneeded cpuarch
-- 
2.34.1

I understand why this package does not lock the virtualbox dependency to the same version (since as an AUR package it would block system updates using pacman), but I think that only makes sense for AUR packages. If you happen to host your own package repository or use one that packages this, having the version locked (i.e. depends=("virtualbox=$pkgver")) makes a lot of sense. It will block system updates until the package repository has the proper matching version. This may make sense for systems where VB usage is important or if you know the repository will be updated to match [community] bumps.

Is it possible that there is no support for 32bit systems anymore? I have a WinXP 32bit VM that refuses to install the expansion pack in the VM. Version 6.1.26 did work, though.

hello friends I had the same error from Daniel-I everything is due to compactness between versions the virtualbox-ext-oracle is not compact with the version of virtual box that you download from the official repositories ... to be clearer we must validate our version of virtualbox with the following command

VBoxManage -v

in my case I have version 6.1.26r145957 of virtualbox

on the next virtualbox page you will find the old builds

https://www.virtualbox.org/wiki/Download_Old_Builds_6_1

here each release has its respective extension pack

In my case, as I mentioned above, I have version 6.1.26 for which I downloaded the following extension pack

https://download.virtualbox.org/virtualbox/6.1.26/Oracle_VM_VirtualBox_Extension_Pack-6.1.26.vbox-extpack

once we download it, we only install it with the following command in the location where it is located

sudo VBoxManage extpack install Oracle_VM_VirtualBox_Extension_Pack-6.1.26.vbox-extpack

With update to Virtualbox 6.1.28. I rebuilt and installed this package and all is well.

installed with virtualbox-bin 6.1.26-1, but still VirtualBox shows no extension pack installed :(

In hindsight, could the issue be related to version matching?

VirtualBox and all it's other packages are v6.1.26 while this package has been updated to 6.1.28... so perhaps this package update was made ahead of VirtualBox (in my Manjaro/pamac repositories anyway) being updated, and will be relevant once VirtualBox itself is updated to 6.1.28?

I wasn't sure how to downgrade an AUR package initially, but found a post that helped me to navigate the snapshots, download the three 6.1.26 package files, and run makepkg -scri... which successfully restored a working extension within Virtualbox!