Arch Linux User Repository

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

I will not waste any more of my precious time, if you can't comprehend the most obvious.

@wantilles: But this doesn't mean, that these versioned dependencies are necessary in this case. The most important reason why these versioned dependencies need urgently be removed from this package is simply because the system can't be updated by pacman -Syu. This is reason enough to remove them. It's really not nice to always force the user to first uninstall this package and then, after the system update, reinstall this package again. The other reason is simply because if this package is updated every user should also update virtualbox. You can expect that every user, at least every Arch user, knows that he has to do so. The best is updating the whole system regularly and not only a single package. Updating a single package can always break something. See Gentoo's revdep-rebuild, which should be run after every update. And because there's only one version of a package in the repos it simply isn't necessary to have versioned dependencies in this package. It's simply not necessary. If someone updates only this package without using his eyes and brain then it's his own fault and not a wrong dependency. It's different on Gentoo where several older versions are kept in the portage tree and where a new package version can be put into a different slot. In this case versioned dependencies are useful and necessary, but not on Arch Linux.

Version dependencies are discouraged. That does not mean that if they are NECESSARY, you should not use them. And yes, each virtualbox extension REQUIRES a base virtualbox base package OF THE EXACT SAME VERSION - NOT something OLDER.

I never said that it does not happen. I said that it is the wrong reason to change correct deps -> to wrong deps -> in a binary distro like Arch. If we were a source distro, like Gentoo, then yes, it would be a correct reason to do something about this.

@wantilles: I am right, because I tested it. pacman -Syu doesn't work and pacman -Syud is the worst thing you can do if it's possible anyway. And versioned dependencies are discouraged anyway. Arch Linux is not Gentoo where you can put different versions into different slots. Arch Linux has only one version of one package in the repos. And if a package is updated then it can be assumed that the dependencies are updated, too. So you can assume that everybody has the latest versions installed. If someone only updates virtualbox-ext-oracle without updating virtualbox, he's on his own.

Cyberpatrol is wrong. You never change correct dependencies, to wrong ones, because the package has not been built yet. You can built the package with -d switch.

@cyberpatrol:you are right. i meet the problem too. have to delete virtualbox-ext-oracle and then packer -Syu.

It would be nice if you would change the line depends=("virtualbox=$pkgver") to depends=("virtualbox") It's because the system can't be updated neither with clyde -Syua nor with pacman -Syu, because it always says that virtualbox-ext-oracle requires virtualbox=4.0.0 even if the latest version in the repos is 4.0.2. And Arch Linux is a rolling release system with only one, the latest, version in the repos. So it can be assumed, that everybody regularly runs a full system update and has the latest version installed. If not, it's the user's problem. The problem is that virtualbox can't be updated from 4.0.0 to 4.0.2 because virtualbox-ext-oracle 4.0.0 is installed and requires virtualbox 4.0.0. So pacman can't update virtualbox and can't resolve the dependency. And virtualbox-ext-oracle can't be updated from 4.0.0 to 4.0.2 because virtualbox 4.0.0 is still installed and can't be updated to 4.0.2. This problem might not appear if virtualbox-ext-oracle would be in [extra], too.

I agree seblu, it's all very strange. That line in my fstab is from about three years ago, so I don't doubt that it's outdated now. But none of the threads in the vbox forums were of any use in solving the greyed out usb devices problem. Their mods just repeat to install the extension pack and make user a member of the vboxusers group, reboot and then usb should work. It's only when checking the groups that I noticed the ID change. Anyway, thank you for maintaining the virtualbox packages. They are very useful to me and I would be lost without them.

strange. i believe new virtualbox use /dev/bus/usb instead of /proc/bus/usb.