Arch Linux User Repository

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

@mikers: How many times do I need to explain this? No versioned dependencies in AUR! Not even in makedepends! Keep your system regularly up-to-date and you won't have any problems. Otherwise edit the PKGBUILD locally by yourself. And makedepends are not needed here, because there doesn't need to be built anything. Makedepends is for packages which are needed to build (compile) a package, but not for running this software, and which can be uninstalled after the package is built. This is not the case here. And if it was the case, what sense does it make to build a package with a newer version than the installed one? It makes no sense, because the package could then easily be broken. And usually there is a reason why a package is not moved from [testing] to the stable repos. @seblu: It would be nice if you would follow the stable repos and not [testing] resp. [community-testing].

Hey I know this is a rather discussed topic already, but what if this package had a makedepends=("virtualbox-$pkgver")? As the current version of VirtualBox has still not left testing in the main repositories, this will at least stop automated AUR wrappers from building this package, but it will not prevent upgrading either virtualbox or virtualbox-ext-oracle.

I don't really know about that, but you seem to have a good point cyberpatrol.

No, please, not again a versioned dependency! This just causes big trouble with updating the system like discussed very often. @monson: Arch Linux is a rolling release distro which has only one (the newest) version of each package in the repos. So it can be assumed that everybody has the newest version installed. Keep your system up-to-date and regularly run `pacman -Syu` or even better `yaourt -Syua` and you won't have any problems with that. With versioned dependencies you regularly need to manually uninstall this package to be able to run a `pacman -Syu` and manuall reinstall it afterwards.

To be convenient to most people, I think it's better to modify to depends=("virtualbox=$pkgver"), as the "virtualbox_bin" PKGBUILD already provides=("virtualbox=${pkgver}").

qs9rx: Now virtualbox_bin is already in repo. Just try to update virtualbox_bin first, and this package hereafter, it should work. However I'm sure seblu will fix it soon.

yes it did not check. You can find why in previous comment.

Proceed with installation? [Y/n] (1/1) checking package integrity [#########################################################] 100% (1/1) checking for file conflicts [#########################################################] 100% 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100% (1/1) upgrading virtualbox-ext-oracle [#########################################################] 100% 0%... Progress state: NS_ERROR_FAILURE VBoxManage: error: Failed to install "/usr/share/virtualbox/extensions/Oracle_VM_VirtualBox_Extension_Pack-4.1.0.vbox-extpack": VBoxExtPackRegister returned VERR_VERSION_MISMATCH, pReg=00000000 ErrInfo='VirtualBox version mismatch - expected 4.1 got 4.0' error: command failed to execute correctly --------------------------------------------- pacman -Qs gives me local/virtualbox 4.0.12-1 local/virtualbox-additions 4.0.12-1 local/virtualbox-ext-oracle 4.1.0-1 So I guess it did not check for the needed vbox version which is not in the repositories yet (just released today).