19:03:05 <wilcal> #startmeeting 19:03:05 <Inigo_Montoya`> Meeting started Thu Oct 21 19:03:05 2021 UTC. The chair is wilcal. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:03:05 <Inigo_Montoya`> Useful Commands: #action #agreed #help #info #idea #link #topic. 19:03:16 <wilcal> Hello all and welcome to our weekly meeting 19:03:33 <wilcal> #topic Who's new? 19:03:41 <wilcal> Anyone new? 19:04:20 <wilcal> Nope 19:04:42 <wilcal> Lets move to 19:04:43 <wilcal> #topic Mageia 8 using and testing 19:04:56 <wilcal> List got short then list got long 19:05:09 <wilcal> Todays updates here did fine 19:05:27 <wilcal> Kodi is getting better and bettere with every release 19:05:57 <wilcal> I have a major issue so is there anything on the list that needs to be discussed first 19:07:13 <wilcal> Anything here with problems: http://madb.mageia.org/tools/updates 19:07:15 <[mbot> Mageia App Db - Current Update candidates 19:07:53 <br_ian> seems like couchdb change may have an issue 19:07:58 <br_ian> anyone else looked into it? 19:08:15 <br_ian> https://bugs.mageia.org/show_bug.cgi?id=29548 19:08:17 <[mbot> 29548 – couchdb new security issue CVE-2021-38295 19:09:16 <wilcal> Never used it 19:09:46 <br_ian> per Herman's note - probably needs a packager to look at it 19:10:10 <wilcal> Anything else on there needs discussion 19:10:50 <wilcal> So lets discuss my issue 19:10:57 <br_ian> np 19:11:05 <Guygoye> I opened a bug report and completed another one on the Raspberry 19:11:12 <wilcal> https://bugs.mageia.org/show_bug.cgi?id=29571 19:11:14 <[mbot> 29571 – Update request: kernel-5.10.75-1.mga8 19:11:41 <wilcal> https://bugs.mageia.org/show_bug.cgi?id=29566 19:11:43 <[mbot> 29566 – Update request: virtualbox-6.1.28-1.mga8 19:11:43 <br_ian> oh - I couldn't download that this morning 19:12:08 <wilcal> Working these two at the same time historically can be a nightmare 19:12:14 <Guygoye> I'll test it as soon as possible 19:12:18 <wilcal> It can brick your system 19:13:05 <wilcal> In the past if you updated the kernel first then vbox update may brick the system 19:13:31 <wilcal> I thouth there was a informal agreement that the two wouldn be in the to do list at the same time 19:13:49 <wilcal> so which to do first? Vbox or the kernel 19:13:56 <wilcal> careful 19:14:10 <Bequimao> I don't use virtualbox. So I will test the kernel. 19:14:34 <Guygoye> I use both 19:14:44 <wilcal> IMO you should do the Vbox update first make sure that works then on the same test platform update the kernel 19:15:19 <wilcal> If you reverse that some years ago you get the kernel panic warning 19:15:36 <wilcal> And your system is bricked 19:15:43 <wilcal> just say'n 19:16:13 <wilcal> And always test on a system that you expect can be bricked 19:16:59 <wilcal> Anyone any thoughts on this 19:17:02 <br_ian> very true wilcal. Don't test that on your prod box if you can help it 19:17:32 <wilcal> I do a mirror of the drive and use the mirrored drive to test 19:18:30 <wilcal> So I will install update_testing Vbox on a system with the present released kernel. Then when that is good on the same system update the kernel 19:19:16 <wilcal> It's been awhile since I've seen both updates in the updates_teting repo at the same time 19:20:07 <wilcal> Vox may have evolved beyond the days when it really diddled around with the kernel 19:20:23 <wilcal> there used to be special drivers and stuff 19:20:44 <br_ian> not sure, seems pretty integrated still 19:21:09 <MageiaTJ> I believe vbox is to be tested and pushed for the existing kernels befoe the kmods for the newe kernel updates can be produced. 19:21:28 <wilcal> Vbox has gotten really really good in the last years. Especially creating a real vertual environment 19:21:45 <wilcal> You got it TJ 19:21:56 <wilcal> Thank you for that. It's important 19:22:45 <MageiaTJ> I'm going to test the vbox update with the 5.14.10 backport kernel later today. 19:23:16 <wilcal> After those Golden Words from TJ anything else on the list for discussion 19:23:44 <benmc> just installed new kernel and rebootn, see how it goes 19:24:26 <wilcal> BTW I test new kernels first in a Vbox client. And in the last years that's been really accurate 19:25:05 <benmc> sound and internet (wifi) 19:25:39 <wilcal> Vbos used to have lots of sound and network wrinkles those have all seem to have faded away 19:26:08 <Guygoye> benmc: sound and internet works well? 19:26:25 <benmc> youtube sound and pix ok, yep 19:26:26 <wilcal> I tested Kodi in a Vbox client. That never used to work. The latest version of Kodi works great in a Vbox client 19:26:37 <MageiaTJ> We had one session a couple of years ago wher the i586 kernel-desktop wouldn't work with my aged laptop's ole Radeon video, but TMB fixed it. 19:27:00 <MageiaTJ> That sort of thing is why we need real hardware tests, too. 19:27:05 <Bequimao> A question on virtualbox. 19:27:14 <wilcal> Go 19:27:59 <Bequimao> I don't use virtualbox as I already said. I use Qemu/KVM instead. Guest-additions are removed. 19:28:00 <benmc> eMMC device partitions still indicate as removable though 19:28:48 <Bequimao> When I test a new kernel with qarepo, the guest-additions are installed. Any sense? 19:28:57 <wilcal> I try to keep my Vbox clients in a simple a state as I can. No special partitions or dubl boot stuff 19:29:42 <wilcal> Let it figure out the guest-aditions on it's won 19:29:45 <wilcal> own 19:30:18 <br_ian> i usually have to go to vbox site and reinstall them through vbox 19:30:30 <wilcal> Ya that can happen 19:31:21 <wilcal> For the record if you didn't know Virtualbox is an Oracle propety. 19:31:30 <treegazer> yep 19:32:37 <wilcal> If you export a .vdi file that will plug and play on another Vbox sysetem. Works beautifully 19:32:58 <wilcal> Perfect for backups 19:33:27 <wilcal> I maintain a primary M8 64-bit client and clone that for testing 19:34:00 <wilcal> I am very careful with that primary client and backup it's .vdi file in multiple places 19:34:22 <Bequimao> There a similar tool in Qemu. I spent much work on it. So I won't change back to VBox. 19:34:23 <MageiaTJ> What little stuff I need to do with Windows is done in Vbox. 19:34:23 * treegazer trying to get VMware workstation working with mga8. It looks like something has changed in the build a kernel module on mga8 which is needed for vmware kernerl modules. I will try to get help with this. 19:35:06 <wilcal> There are many pirated Windows .vdi's all over the Internet 19:35:25 <wilcal> They can be big like 10GB big 19:35:38 <treegazer> how can those possibly be trusted? 19:36:19 <wilcal> I've never had a .vdi client infect my system. Vbox pretty much keeps everyting "in the box" 19:36:31 <wilcal> good place to keep infected test systems 19:36:33 <benmc> treegazer: exactly 19:37:32 <wilcal> Also if you syspect or know something is infected disconnect it's network connection 19:37:45 <treegazer> unless it is something I have installed from the original install media...I am very paranoid about randon stuff floating around the interwebs. Especially windows. 19:37:52 <wilcal> that way you can tinker with it safely 19:38:56 <treegazer> looks like windoze11 forces users to switch to new hardware. It wont run without UEFI and TPM hardware 19:38:56 <wilcal> I bet in the last 10-years I don't think I've tinkered with more then 2 or 3 Windows Vbox clients 19:39:15 <wilcal> Win11 is an embarrisment for MicroSoft 19:39:25 <wilcal> lets move to 19:39:26 <wilcal> #topic Anything else? 19:39:48 <treegazer> it's going to exacerbate the chip shortages 19:39:53 <wilcal> You but a Dell Laptop in 2019 and you can update it to Win11 19:39:59 <wilcal> You buy 19:40:27 <treegazer> have you seen the M$ "health check" to verify your h/w supports win11? 19:41:00 <wilcal> I should try that on my Dell laption that's a little over a year old 19:41:11 <wilcal> laptop 19:41:16 <benmc> have we moved on to "anything else" yyet 19:41:21 <wilcal> yes 19:41:28 <wilcal> Anything else 19:42:00 <benmc> # anything else? 19:42:32 <wilcal> I don't have anything 19:42:41 <br_ian> nothing really - again I assume setting feedback is critical if we need packagers to look at something 19:42:58 <MageiaTJ> nothing here. 19:43:07 <wilcal> OK thanks all for being here 19:43:18 <wilcal> great discussion on the Kernel/Vbox updates 19:43:51 <br_ian> wilcal - feedback? 19:43:56 <MageiaTJ> Sometimes it takes them a long time, even with the feedback flag set. 19:44:04 <br_ian> true 19:44:08 <wilcal> Count down time 19:44:12 <wilcal> T-5 19:44:19 <wilcal> thanks all for being here 19:44:25 <wilcal> T-4 19:44:30 <wilcal> T-3 19:44:45 <wilcal> next week same time same place 19:44:50 <wilcal> T-2 19:44:54 <Luigi12> if they don't respond to "feedback" assign it back to the packager 19:45:07 <wilcal> T-1Thanks Luigi 19:45:16 <wilcal> #endmeeting