20:01:41 <tarazed> #startmeeting
20:01:41 <Inigo_Montoya> Meeting started Thu Jan 25 20:01:41 2018 UTC.  The chair is tarazed. Information about MeetBot at http://wiki.debian.org/MeetBot.
20:01:41 <Inigo_Montoya> Useful Commands: #action #agreed #help #info #idea #link #topic.
20:02:19 <tarazed> #topic Anybody new here today?
20:02:30 <tarazed> Anybody here who has not attended any of these meetings before?
20:02:30 <tarazed> If so please introduce yourself and we shall respond in kind.
20:02:54 <tarazed> Hi Shlomi
20:03:06 <rindolf> tarazed: meow
20:03:39 <tarazed> There is no particular agenda today but Lewis suggested that people might want to talk about the KDE/Plasma update and, quoting him:
20:03:42 <tarazed> "The status for trying the MGA5 Applet -> M6 upgrade. And please
20:03:44 <tarazed> discuss the sense or otherwise of doing it from a *non* Plasma desktop
20:03:47 <tarazed> (or the command line)."
20:04:06 <tarazed> So the floor is open.
20:04:11 <brian__> sure - I can try that from a VM
20:04:22 <brian__> how do I get that upgrade applet to show?
20:04:48 <tarazed> That is something I wondered, never having seen it.
20:05:23 <tjandrews> I've never done it, either. Never so much as looked into it.
20:05:44 <tmb> Its described in test procedure: https://bugs.mageia.org/show_bug.cgi?id=21425#c24
20:05:46 <[mbot> [ 21425 – mgaonline changes to black background and invisible labels during upgrade to Mageia 6 ]
20:05:59 <tarazed> If it is for an upgrade maybe it only turns up when a new version is available.
20:06:18 <brian__> ok - look into 21425
20:06:31 <tarazed> Thanks tThomas.
20:07:02 <tmb> point 8 shows how to trigged the "new distro release available"
20:08:36 <brian__> looks like comment 24 has the objects
20:08:37 <tarazed> Just looked at 21425.  I guess any of us could try it.
20:08:59 <tjandrews> OK, reading the test procedure, it requires a more reliable ISP than mine.
20:09:27 <tjandrews> And faster, too.
20:09:51 <tmb> well, mga6 repo is mostly stable...
20:09:59 <brian__> should I focus on kde only or cover gnome as well?
20:10:16 <tarazed> That's what Lewis wondered?
20:10:46 <tarazed> My inclination is to try it with Mate.
20:11:10 <brian__> I'll have to see what mga5 VM's I have in play
20:11:13 <tjandrews> My end is the trouble. An online upgrade would take several hours.
20:11:45 <brian__> it probably will even if you had more bandwidth
20:12:05 <tarazed> Yeah,  Don't sweat it TJ.  We just have to do what we can.  My ISP is fairly reliable, and fast (216MB/s).
20:12:21 <brian__> <I'm envious>  ;-)
20:12:22 <tarazed> Sorry, 216Mb/s
20:12:52 <brian__> ok I have a 5-32bit_gnome
20:13:00 <brian__> and a 64-bit KDE
20:13:15 <brian__> that would hit both arch and UI's
20:13:50 <brian__> my time is getting limited now, so it'll take some time if there are issues
20:14:27 <tarazed> It will get tested so no need to worry too much.
20:14:27 <brian__> tmb:  VM upgrades should be sufficient?
20:14:53 <brian__> or should I pull an antique drive and build mga5-64-kde
20:16:34 <tmb> brian__, vm upgrades are simplest as you can create a snapshot before and roll back when/if you want...
20:16:47 <brian__> yes
20:17:35 <brian__> is there any benefit in doing a bare metal upgrade in this case?
20:17:41 <brian__> after the VM tests
20:17:43 <tmb> as for the kde update to test against cauldron I just posted on QA-discuss that I think it's a waste of QA time as there is way much more stuff going on in cauldron that will make the tests somewhat useless
20:18:23 <tarazed> Okay.
20:18:23 <brian__> ok - I'll focus on the list then
20:20:15 <tarazed> Are there hardware specific issues when upgrading?  If so then we would need real hardware as well.
20:22:18 <tmb> yeah, some hw tests would be good too
20:22:19 <brian__> I'm guessing - upgrade - yeah hardwar
20:22:58 <brian__> ok after initial tests, I'll spin up my old coalburning PC with a bearing drive
20:23:29 <tjandrews> ;-)
20:24:26 <tarazed> As said, we have a good collection of hardware in QA so you don't need to push yourself too much Brian.  If you have the time, great and thanks.
20:24:48 <tarazed> Time to move on?
20:24:54 <brian__> yes
20:25:23 <tarazed> #topic Updates - any problems?
20:25:55 <tarazed> What about this Plasma update thing?
20:27:30 <tarazed> Nothing posted so far.
20:28:27 <tarazed> tmb: the graphics stack.  Can we move this on now?
20:30:10 <tmb> yeah, I think its tested enough... and so is virtualbox update
20:30:36 <tjandrews> I was going to ask about vbox.
20:31:18 <tjandrews> Wilcal's problem has a workaround, if not a solution.
20:31:44 <tarazed> tmb: OK, with virtualbox gone you can finish the kernel list
20:32:44 <tarazed> tj: is that posted?
20:32:54 <tjandrews> I've been holding off on testing more kernels, waiting for vbox kmods.
20:33:52 <tjandrews> It's in the bug report. You need to use only one core to run a VM. There's a bug on it, from Cauldron.
20:33:59 <brian__> I just saw 4.14.15 - will look into it
20:34:27 <brian__> once built though you can push it up correct?
20:34:40 <tarazed> That's fair enough TJ.  We can move it on then.
20:34:46 <tmb> and th "one cpu" bug in vbox does not affect alll... for example I cant reproduce it on any of my systems
20:35:34 <tarazed> So this is a corner case of some kind.
20:36:00 <tjandrews> Sounds like an upstream bug to me.
20:37:56 <tarazed> We seem to have run dry, so#topic Anything else?
20:38:20 <tarazed> #topic Anything else?
20:38:47 <tarazed> Trying to get used to these shiny buttons.
20:39:08 <tmb> :)
20:39:19 <tjandrews> Don't let the power go to your head...
20:40:22 <tarazed> I got it wrong  anyway.  There should have been somebody else on the bench.  Too late now.
20:41:05 <tarazed> Looks like we are finished.  Thanks to everybody for coming.
20:41:15 <brian__> good night everyone
20:41:28 <tarazed> You want to do the countdown TJ?
20:41:43 <tjandrews> :)
20:41:51 <tjandrews> T-5
20:42:04 <tjandrews> T-4
20:42:14 <tjandrews> T-3
20:42:21 <tarazed> See y'all next week.
20:42:23 <tjandrews> T-2
20:42:30 <tjandrews> T-1
20:42:44 <tarazed> #endmeeting