Arch Linux User Repository

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

@seblu: Thanks. But, please, follow the stable virtualbox in [community], not in [community-testing], if it goes there first. @Musikolo: pacman -Syu does the job without the need of a versioned dependency in an AUR package.

@seblu: I don't know whether it will help to find a hybrid solution, but wouldn't be enough by doing this? depends=("virtualbox" >= 4) Please, let me know if I'm wrong, but with this, the problem of upgrading with pacman -Syu should be fix and, also, pleople having virtualbox-3.x will be force to upgrade to 4.x. Best regards!

@cyberpatrol, lrm: you're right. i will fix.

I'm with cyberpatrol. The versioned dependency just causes trouble and doesn't save anyone from anything. If someone updates their aur without doing pacman -Syu first then they deserve what they get, IMO :).

@seblu: Your impression is wrong. But I know the reason for this updating issue. I explained it quite detailed, and I've tested it, at least with the =. I don't know, yet, if I can downgrade both packages and test it again. But I don't think that this is necessary, if you read Mektub's and shivmeister's latest comments. Shivmeister is, btw., an Arch Linux developer. So I guess you can believe him, if you don't believe me. Mektub has already tried it with >= and he had to remove the version number, because it didn't work for him with >=. And shivmeister explained to you why versioned dependencies are sometimes needed and why they should be avoided otherwise. And you just need to think logical. Then you will see why also >= can't work. And keep in mind the issue is not updating only this package with yaourt. The issue is a complete system update with pacman -Syu or clyde -Syua which is simply not possible. These are facts and not my ego. And another point: If you really want to become a TU then you should know that.

@cyberpatrol: long time ago? This package have 3 weeks... Please be serious. I don't test every cases. I invite you to try and tell me if their is issues. I have the impression that you want us to do it your way and not otherwise.

@seblu: Did you test it with pacman -Syu when virtualbox in [community] was updated, too? Just updating virtualbox-ext-oracle with yaourt could bring wrong results, which don't help with this issue. This issue has to do with circular dependencies. Btw., it's long ago that virtualbox was updated from 3 to 4 and this update is/was done by pacman -Syu, too. So there's definitely no need anymore for this versioned dependency. It was infact not needed before to get a correct transition from 3 to 4, just because of the rolling release and because there's only one version of a package in the repos. It can be expected from Arch users to update their systems regularly and not only update one single package from AUR. So it's definitely the best to remove these versioned dependency, and it's btw. Arch plolicy. Believe me.

so, i make a test with a fake 4.0.3 version of virtualbox... rwolf ~/scm/archrep/virtualbox_bin $ yaourt -U virtualbox_bin-4.0.3-1-x86_64.pkg.tar.xz resolving dependencies... looking for inter-conflicts... Targets (1): virtualbox_bin-4.0.3-1 Total Download Size: 0,00 MB Total Installed Size: 129,80 MB Proceed with installation? [Y/n] checking package integrity... (1/1) checking for file conflicts [########################################################################################] 100% (1/1) upgrading virtualbox_bin [########################################################################################] 100% :: Unloading VirtualBox kernel modules [BUSY] [DONE] :: Recompiling VirtualBox kernel modules [BUSY] [DONE] :: Reloading VirtualBox kernel modules [BUSY] [DONE]

ok i will test

@seblu:>= does not work. Thats the line I changed to be able to update.