Arch Linux User Repository

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

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.

@ijann If this is a recurring thing, as the PKGBUILD suggests due to its hardcoded version number, then simply having to do this every single time that you need to upgrade is as annoying as uninstalling and reinstalling. This is a known issue since 2011. It really should just depend on Virtualbox.

@MartinX3 But why should I pin the 2011 comment, the line that @elvisman113 published solved it for me and I was able to install normally. You send me to look for a comment from 2011. Do you know how many comments are written each year? to search again, why don't you anchor that comment from 2011? But if you pin the comment to look for one from 2011, 😤

@ijann Please read the comments in 2011 before making such claims.

The reason was to prevent incompatibilities between MAJOR version like the jump from v7.x.x to v8.0.0.

But how it is made in this PKGBUILD it breaks whole system upgrades by also check the minor and patch version.

This has to be fixed.
Otherwise this package is a security issue with it's blocking system updates behaviour...

You should post the comment where the solution to the problem is, it's simple, but many are new and don't know how to solve it, @elvisman113 already mentioned it but go back to the comment from 2011, don't be bad, here are ways to post the comments to show how to solve the problem and not repeat in comments a problem that has already been solved over time.

The update problem due to the oracle extension virtualbox-ext-oracle

> sudo pacman -Sd virtualbox
o
> yay -Sd virtualbox

then update normally