19:01:32 <lewyssmith> #startmeeting
19:01:32 <Inigo_Montoya`> Meeting started Thu Oct 13 19:01:32 2016 UTC.  The chair is lewyssmith. Information about MeetBot at http://wiki.debian.org/MeetBot.
19:01:32 <Inigo_Montoya`> Useful Commands: #action #agreed #help #info #idea #link #topic.
19:01:58 <lewyssmith> #topic Who's new? - If you are then come and say hello
19:02:37 <lewyssmith> Does anyone notice any new name?
19:03:23 <tjandrews> I don't know how to make Chatzilla show the names.
19:03:54 <brian_> not sure who ca-on-ad... is
19:04:07 <lewyssmith> tjandrews: I use old Opera, but Hexchat shows the list. Both are good.
19:04:41 <lewyssmith> brian_: But he/she has been around before.
19:04:50 <brian_> ah ok
19:04:54 <tjandrews> I have a list in a side pane, but it's everybody, not just those here.
19:05:29 <lewyssmith> The list is those who are logged in, even if they are not saying anything.
19:05:52 <lewyssmith> Anyway...
19:05:55 <lewyssmith> #topic Mageia 5.1 - Still saiting for new isos
19:06:53 <lewyssmith> Anne has been awaiting the latest kernel & nonfree firmware updates. I have just let those loose.
19:07:40 <tmb> vbox needs to go out too then...
19:08:17 <tmb> (as vbox kmods needs to stay in sync)
19:08:53 <lewyssmith> But the equivalent VBox update awaits. It is a *long* bug. I would prefer to see new 5.1 Classic ISOs without the VBox update, to give us something to work on. We could re-do the ISO once VBox is agreed. What say you?
19:09:03 <tjandrews> vbox 32-bit is completely unusable for me.
19:09:13 <lewyssmith> tmb: BTW Welcome, Thomas. Hope you are OK.
19:09:30 <tjandrews> Sure. Why?
19:09:51 <lewyssmith> Why what?
19:09:53 <tmb> lewyssmith, well, then old vbox 5.1.2 kmods needs to be restored on updates_testing
19:09:58 <tarazed> tj: Commiserations.  You did the right thing.
19:10:25 <tjandrews> Ah.
19:11:11 <lewyssmith> tmb: I am not competent to jusge. If we need to wait for VBox, so be it. Presumably that means the Kernel & nonfree firmware updates should *not* be pushed yet.
19:11:17 <tmb> lewyssmith, but that should be possible with some sysadm foo if theya re still in old tree
19:11:39 <tjandrews> In 32-bit, vbox 5.1.6 acts just like 5.1.4 did. But I don't know if it's unique to my system or not.
19:12:22 <tmb> well, if 5.1.6 is broken then 5.1.2 it is..
19:12:35 <lewyssmith> Is VBox 5.1.6 compatible with the latest kernel (made for 5.1.4)?
19:12:51 * tmb goes checking schedbot
19:15:30 <tmb> ok,, no 5.1.2 kmods available anymore
19:16:23 <tjandrews> Is there any chance that vbox downloaded from the vendor would be different than ours?
19:17:46 <tmb> lewyssmith, if you read https://bugs.mageia.org/show_bug.cgi?id=19397#c7 you see I prepped 5.1.2 modules to go with 4.4.22
19:17:48 <[mbot> Bug 19397: normal, Normal, qa-bugs, NEW , Update Request: kernel-4.4.22-1.mga5, kernel
19:18:10 <tjandrews> I'm wondering if something is somehow missing. Some new dependency, perhaps.
19:18:21 <tmb> it was others pushing for vbox 5.1.6 that "broke" that
19:19:30 <lewyssmith> So it looks as if in order to advance, we really need VB 5.1.2 back.
19:21:14 <lewyssmith> Well?
19:21:35 <tmb> yep, I'll nuke the 5.1.6 kmods and resubmit 5.1.2 ones
19:21:49 <lewyssmith> That would be very kind.
19:22:28 <lewyssmith> Are there any other issues holding back new 5.1 ISOs?
19:23:50 <tmb> nope. I thought tv wanted to backport some grub2 related patches, but since nothing have happened I'll roll new drakx-installer-* packages to pick up kernel 4.4 and nvme support and we go with that
19:23:50 <lewyssmith> So if there is no more to say for now on 5.1, following Bill's schedule...
19:25:20 <lewyssmith> Again, very kind of you. We do need to try 5.1 - some of us have not been able to yet.
19:25:40 <lewyssmith> #topic Mageia 6 - How's it looking?
19:26:20 <lewyssmith> This can only apply to people who install from Cauldron. Any comments?
19:27:49 <brian_> I thought 6 wa completely on hold
19:28:23 <brian_> I have once instance of 6 running with XFCE.  Seems to take the updates and work fine
19:28:46 <lewyssmith> -2: It is; but some people keep up-to-date in advance.
19:29:49 <lewyssmith> The main issue according to the mailList sems to be orphans after updating existing M5.
19:30:46 <lewyssmith> Once more, "All quiet on the western front" here, so...
19:31:02 <lewyssmith> #topic Testing updates - Any difficulties, problems, issues?
19:31:03 <stratocaster7> Good luck was still there on fresh installs as of a few days ago and plasma is still not saving settings. Some parts seem pretty broken still.
19:31:54 <tjandrews> So then, what are we to do with vbox 5.1.6?
19:32:22 <tmb> put feedback on 5.1.6 for now and go back to 5.1.2
19:33:48 <lewyssmith> Shall I mark the bug now?
19:33:56 <tjandrews> It's too bad that I seem to be the only one testing it on a 32-bit Mageia 5.
19:34:24 <tmb> yeah, I've dropped the 5.1.6 kmods
19:34:26 <tjandrews> Makes me wonder if it's just me.
19:35:25 <stratocaster7> tjandrews: Not just you. Luigi12 has commented about audio problems too.
19:35:42 <tmb> tjandrews, maybe only one in QA but scaling out error percentage on all mga5 users it will not be good
19:35:54 <tjandrews> In practice, I can't imagine somebody with a 64-bit-capable machine using vbox on a 32-bit install as I have been testing.
19:36:29 <tjandrews> But I suppose it's possible.
19:37:20 <jkerr82508> fwiw I've just installed 32 bit mga5 live gnome dvd in a vm on  vbox5.1.6 on mga5-32. Everything is working perfectly
19:37:43 <lewyssmith> The bug feedbacked with a note about 5.1.2.
19:38:47 <tjandrews> I can't get it to boot an iso.
19:39:37 <lewyssmith> Would anyone normally mix 32/64 bit hosts & guests?
19:40:15 <lewyssmith> Would it help to confine testing to the same architecture for both?
19:40:54 <brian_> I can't think 32 host running 64 VM, but then to try a distro I suppose yes
19:41:28 <brian_> I certainly do host 64 to VM 32 and 64
19:41:28 <lewyssmith> That would be pushing your luck, I think.
19:42:10 <tjandrews> No. it's a 32-bit host. The processor is 64-bit, but the kernel is 32.
19:42:38 <brian_> yes - same here all my machines are 64 bit now, even my anxient sempron
19:42:42 <brian_> ancient
19:43:02 <lewyssmith> The update list is long, & grows faster than we are attacking it. Please take a look. We have had some stiff ones lately.
19:43:08 <brian_> but to save memory I run 32 on the sempron (I use it to play music)
19:43:18 <tjandrews> I have no problems mixing a 32-bit Mageia guest on a 64-bit host.
19:43:36 <brian_> :lewysmith - I'll see what I can attack
19:45:35 <lewyssmith> Does anyone know how to invoke aria2 to test the c-ares bug?
19:46:17 <lewyssmith> I wonder whether it is used by our normal update processes.
19:48:02 <tarazed> I may step in and help you on this one.  Don't know anything about it just now.
19:48:46 <lewyssmith> You have been working hard on all fronts here, Len. Including near-impossible ones!
19:49:35 <lewyssmith> A successor to Claire, even.
19:51:43 <lewyssmith> Let us see if Luigi is onlooking...
19:51:59 <lewyssmith> #topic Luigi's roundup - Security news & expected updates
19:52:53 <lewyssmith> ping Luigi12
19:53:13 <Luigi12> boo
19:53:37 <lewyssmith> Welcome David.
19:54:03 <Luigi12> tjandrews: until recently I was using i586 Mageia on all of my machines, so my vbox host at home was included in that
19:54:25 <Luigi12> I finally gave up on i586 because the Mageia server kernel has memory issues and becomes unusable within a week
19:54:54 <Luigi12> lewyssmith: it's common to have VMs a different arch than the host
19:55:26 <Luigi12> ok I'm caught up now
19:55:26 <tmb> Luigi12, is the memory problem still an issue ? I thought it got fixed...
19:55:39 <Luigi12> tmb: yeah it still doesn't work right
19:55:58 <tmb> hm, that sucks
19:56:09 <Luigi12> tmb: I know you changed a config setting (SLUB allocator or something) but it didn't help, I had to give up on it and reinstall as x86_64
19:56:11 <tjandrews> Other than vbox, I've had no issues with the server kernel.
19:56:35 <Luigi12> ok, roundup, new security bugs
19:56:55 <Luigi12> someone filed a bug for the kernel ironically, so we may have another kernel update right after the current one
19:57:02 <tjandrews> But then, I've moved on to the point where I don't use it all the time.
19:57:17 <Luigi12> there's a new flash available of course, there's a new chromium-browser-stable available of course, lather rinse repeat
19:57:41 <lewyssmith> Good thing Bill is absent today!
19:57:44 <Luigi12> bugs filed in the past week for freeimage, nodejs, libgit2, tomcat, guile, tracker
19:57:57 <Luigi12> also one for dbus, but it sounds like it's almost (if not completely) a non-issue in practice
19:58:32 <Luigi12> we have a growing list of older security bugs that are not getting addressed
19:58:40 <Luigi12> I don't have the time to package all security fixes myself anymore
19:58:57 <lewyssmith> Who should do it?
19:58:59 <Luigi12> stormi made a nice madb tool for our security bugs
19:59:03 <Luigi12> lewyssmith: the packaging team
19:59:20 <Luigi12> same as the QA madb tool, just change "updates" to "security" if you want to see it
19:59:42 <Luigi12> at some point I'll have to fill out the status field for some of them to give a better overview
20:00:06 <Luigi12> been working 12 hour days :o)
20:00:29 <brian_> ouch
20:00:44 <brian_> can relate
20:01:00 <lewyssmith> The security lists = 80+ bugs!
20:01:03 <tjandrews> So can I.
20:01:12 <tmb> nice tool :)... not so nice list ... :(
20:01:21 <lewyssmith> !
20:02:57 <lewyssmith> Luigi12: Have you announced all for this week?
20:03:35 <Luigi12> yeah
20:03:49 <Luigi12> php update might come soon too
20:05:14 <lewyssmith> We already have 2 PHP related updates. We have seen worse forecasts. Thanks for your contribution.
20:05:48 <tarazed> What should we do about stuck bugs, openjpeg2 in particular?
20:06:19 <lewyssmith> Can I discuss that with you directly?
20:06:28 <tarazed> Surely.
20:06:54 <lewyssmith> Will do. The others are slowly unsticking.
20:07:36 <lewyssmith> Any reason not to move on (topic)?
20:08:36 <lewyssmith> #topic Anything else?
20:08:41 <tjandrews> Just wanted to say that my brother's Mageia has been using the server kernel for about a year without issues, but his motherboard maxes out at 2GB.
20:09:22 <tmb> virtualbox 5.1.2 kmods for kernel 4.4.22 now restored in updates_testing
20:09:30 <tjandrews> The server kernel is the one the installer always puts there.
20:10:08 <lewyssmith> tmb: Fast work, Thomas! Let VB fans attack it.
20:10:31 <lewyssmith> Remember that next 5.1 ISOs depend on it.
20:11:31 <tmb> tjandrews, file a bug about that, and attach outputs from  dmesg, lspcidrake -v and dmidecode so we can find out why it selects server kernel on that hw
20:12:52 <tjandrews> It has since Mandriva days.
20:13:22 <tjandrews> I was told it was something about it being PAE-capable.
20:14:22 <lewyssmith> No further burning issues, so countdown?
20:14:50 <lewyssmith> -5
20:15:04 <lewyssmith> Thanks to those who turned up.
20:15:07 <lewyssmith> -4
20:15:12 <lewyssmith> -3
20:15:30 <lewyssmith> And to Bill for preparing the meeting.
20:15:32 <lewyssmith> -2
20:15:41 <tarazed> Bonsoir
20:15:43 <lewyssmith> Goodbye eveybody.
20:15:47 <lewyssmith> -1
20:15:55 <lewyssmith> #endmeeting