IRC conversation with upstream

file_683726.txt (text/plain), 5.32 KB, created by Jakub Hrbek on 2019-04-18 06:49:20 UTC

kreyren> is virtualbox compatible with linux-5.0.3 ? seems to be looking for old modules on gentoo http://dpaste.com/003BN5A assuming https://i.imgur.com/1bEpRTO.png
<01> kreyren: When did 5.0.3 came out?
<kreyren> like +- 2 weeks ago?
<kreyren> 5.1-rc4 is latest afaik
<01> And when did VirtualBox 6.0.4 came out? 2019-01-28. Do you expect something from Jan/2019 to have support for something from Apr//2019?
<01> No.
<01> So, either you go for the test builds, or you wait for a newer release.
<kreyren> im asking if test build is compatible
<01> BTW, it seems that you're getting VirtualBox from the repository. That's a fork of VirtualBox!
<kreyren> so that i woudn't compile it manually for nothing
<01> I believe there were some patches submitted, not sure if they've made their way to the testbuilds...
<kreyren> `I="https://download.virtualbox.org/virtualbox/${MY_PV}/${MY_P}.tar.bz2` -> seems like virtualbox ?
<01> What's that???
<kreyren> thats where ebuild takes source
<kreyren> + patches 
<01> That seems like "something of" a source code release. That's the only file that ends in .tar.bz2...
<kreyren> https://download.virtualbox.org/virtualbox/ ?
<01> But the latest you have is the 6.0.4 one, from Jan. Not the latest test builds.
<01> What I'd do...
<01> If you installed VBox from the repository, remove it.
<01> Install the latest test build from https://www.virtualbox.org/wiki/Testbuilds
<01> You're on Gentoo you said, right? So, nor RHEL6 or RHEL7, you need the "generic" package for Linux...
<kreyren> it woudn't make it in gentoo repo if it wasn't official.. the release is very restricted.. 
<kreyren> + it;s. virtualbox.org
<01> Are you saying that Gentoo has the test builds?
<kreyren> they are using patches https://dev.gentoo.org/~polynomial-c/${PN}/patchsets/${PN}-6.0.0_beta2-patches-01.tar.xz"
<kreyren> checking
<kreyren> it's https://download.virtualbox.org/virtualbox/6.0.4/ with gentoo patches 
<kreyren> probably something grabbed from upstream since source doesn't have release candidates
<01> Frankly, I honestly don't want to "support" a fork, no matter how strict they are. If it's "VBoxManage -version" comes up with "6.0.97_Gentoo r129919", then that's a fork. Forget the actual numbers, it's the "_Gentoo" part that counts.
<kreyren> doubt it's fork https://dev.gentoo.org/~polynomial-c/virtualbox/patchsets/ seems to be using upstream patches
<kreyren> 001_virtualbox-5.0.16-mesa-check.patch               006_virtualbox-4.2.18-vboxwebsrv_fix.patch
<kreyren> 002_virtualbox-5.2.16-remove-configure-checks.patch  009-virtualbox-5.1.0-add_missing_gl_header.patch
<kreyren> 003_virtualbox-4.0.2-restore_old_machines_dir.patch  010_virtualbox-5.2.12-qt511.patch
<kreyren> 004_virtualbox-4.1.2-vboxpci-build.patch             011_virtualbox-6.0.0_beta2-xpcom_const.patch
<kreyren> 005_virtualbox-4.2.26-asneeded.patch
<kreyren> ah sry spam
<01> kreyren: What in the seven kingdoms is that?
<01> We're still talking about VirtualBox latest test builds supporting Linux 5.0.3, right
<01> ?
<kreyren> y
<01> Then why am I seeing VBox 4.0.2 to 5.2.16
<01> ?
<kreyren> assuming that debian-sid has same issue i doubt that vbox supports linux 5.0 yet 
<01> kreyren: Did you try the test builds? Y/N?
<kreyren> 01, asuming that they have one patch repo and applying them on demand to said version so 6.0.0 is applied which seems to be grabbed from git commit and placed in patch
<kreyren> 01, i tried debian-sid on this kernel with virtualbox which afaik is latest build -> same issue -> assuming not supported
<01> kreyren: I don't think I'm making myself clear... If you don't try the test builds from VirtualBox.org, then I'm not going to keep checking how the repos are doing their job...
<01> And not the release, the latest available test-build.
<01> https://www.virtualbox.org/wiki/Testbuilds
<kreyren> that should be in debian assuming that debian dir is in latest git
<01> Maybe you should be talking to #debian
<kreyren> trying the test-build from provided url as `kreyren@dreamon ~/Downloads $ ./VirtualBox-6.0.5-129923-Linux_amd64.run`
<kreyren> wont do anything
<kreyren> assuming .run file
<01> Won't do anything? How are you running it?
<kreyren> as presented ./pathname.run
<01> Something's wrong with the download or your setup. All I have to do is "sudo sh ./VirtualBox.run"
<01> (assuming that you've made it executable, right?)
<kreyren> yep i made it executable
<kreyren> wont open with sudo nor sudo sh
<01> Then make sure it's not corrupted. Let me run a checksum on it...
<01> 44caa4576dd3b1ecd04abe4585417266c4f396ec3164d1907242dad0319b3f32  /Users/Shared/VirtualBox/_Downloads/VirtualBox-6.0.97-129919-Linux_amd64.run
<01> Sorry, the command was: "shasum -a 256 /Users/Shared/VirtualBox/_Downloads/VirtualBox-6.0.97-129919-Linux_amd64.run"
<kreyren> sec
<kreyren> downloading it using wget just to make sure that firefox won't touch it, is taking longer
<kreyren> 20% atm on 500mb/s download
<kreyren> seems to work now, trying
<01> Rogue download then? You didn't even run the checksum?
<kreyren> works nwo! thanks
<01> With Linux 5.0.3?
<kreyren> nope checksum wasn't needed
<kreyren> yep, trying to load image now
* 01 going for smoke, not loading anything...
<kreyren> sanity: https://i.imgur.com/6McpRYZ.png
<01> kreyren: Did VirtualBox install and run properly?
<kreyren> yep installing MXLinux on it now