Virtualbox-ext-oracle in Unstable

[jrichard326]

This morning pamac offered virtualbox-ext-oracle 6.1.36-1, so I built the package. Afterwards, Virtualbox launched, but I could not open any VM’s. Downgrade back to virtualbox-ext-oracle 6.134-1 worked as now all versions, Virtualbox, Virtualbox-guest-iso were back to version 6.134. I upgrade all to version 6.1.36 and all was working.
Please push updates Virtualbox and virtualbox-guest-iso and any others to version 6.136 in Unstable branch?

Thanks

[anon89812132]

@jrichard326

Virtualbox

The 6.1.36 was literally pushed to Arch Linux 3 hours ago. No more patience, or everything has to be instant?

@jrichard326

virtualbox-ext-oracle 6.1.36

Is an AUR package, why is dictating the update routine?

[straycat]

I installed that update earlier and figured I’d wait until 6.1.36 made it’s way to unstable before starting virtualbox.

[linux-aarhus]

@jrichard326

This morning pamac offered virtualbox-ext-oracle 6.1.36-1, so I built the package. Afterwards, Virtualbox launched, but I could not open any VM’s.

This is exactly why you should not automate rebuilding of custom packages.

[maycne.sonahoz]

@jrichard326

Please push updates Virtualbox and virtualbox-guest-iso and any others to version 6.136 in Unstable branch?

@maycne.sonahoz

Since AUR is maintained by Arch users for Arch users, updates in AUR and in Manjaro’s repositories are usually not synchronized:

• You may need to delay an AUR package update in order to comply with its dependencies from Manjaro’s repositories.
• You may need to manually start a rebuild of an AUR package after a dependency update from Manjaro’s repositories.

[Yochanan]

Always wait to update virtualbox-ext-oracle until the matching virtualbox version is available.

[anon89812132]

Virtualbox 6.1.36 is in unstable now