19:04:54 <MrsB> #startmeeting
19:04:54 <Inigo_Montoya`> Meeting started Thu Apr 16 19:04:54 2015 UTC.  The chair is MrsB. Information about MeetBot at http://wiki.debian.org/MeetBot.
19:04:54 <Inigo_Montoya`> Useful Commands: #action #agreed #help #info #idea #link #topic.
19:05:04 <MrsB> Welcome everybody to another one
19:05:20 <MrsB> #chair DavidWHodgins wilcal
19:05:20 <Inigo_Montoya`> Current chairs: DavidWHodgins MrsB wilcal
19:05:21 <DavidWHodgins> #topic Who's new? If you are just joining, come and introduce yourself
19:05:41 <MrsB> Is anybody new with us tonight ?
19:06:02 * rindolf is not new.
19:06:05 <MrsB> I had an email earlier from ashvin who is joining the team
19:06:14 <marja> \o/
19:06:53 <MrsB> let's move on then
19:07:00 <DavidWHodgins> #topic Mentoring update - Still ISO testing :\
19:07:05 <marja> MrsB: is that saptech?
19:07:19 <MrsB> no saptech too, you're right marja.
19:07:52 <MrsB> not here atm either though
19:08:08 <MrsB> So hows mentoring guys? Still difficult to tell
19:08:23 <DavidWHodgins> No change in mentoring here. Waiting till rc is out, before working on helping vlad set up updates testing environments
19:08:35 <wilcal> So much iso testing but i still stay in touch
19:08:49 <lewyssmith> No active candidate with me.
19:08:50 <MrsB> yeah it's not a mentoring climate atm is it
19:09:01 <MrsB> really lewis, how did that happen?
19:09:21 <lewyssmith> Not surte what you mean.
19:09:35 <MrsB> you've been a mentoring star
19:09:54 <lewyssmith> They all grew up quickly.
19:10:06 <MrsB> let's move on then and do this again next week :D
19:10:18 <MrsB> morning tmb and Tonyb_
19:10:28 <Tonyb_> morning
19:10:29 <DavidWHodgins> #topic Mageia 5 RC - Where are we now?
19:10:30 <tmb> mornin'
19:10:34 <MrsB> thanks dude
19:10:57 <MrsB> Sooo how's it looking?
19:11:23 <marja> I'm more testing bits and pieces than full isos :-/
19:11:25 <MrsB> I've compiled a bit of an errata at the top of the pad
19:11:32 <DavidWHodgins> We still have 13 release blocker bugs. While they should be final blockers, I think we should go ahead and release the RC. Though maybe we should plan it for Monday, to give a bit more time for testing the latest iso images.
19:11:57 <tjandrews> The i586 RC is looking good on older hardware.
19:12:01 <Tonyb_> I'll test more over weekend
19:12:18 <MrsB> tmb: what are your thoughts?
19:13:00 <wilcal> brb
19:13:05 <lewyssmith> I am keen to try the mising consoles affair, but have been too busy in other directions. BTAIM For the seconf time I have a problem with the KDE Live DVD not booting; it was always very reliable.
19:13:24 <marja> tv suggested to have one more set https://bugs.mageia.org/show_bug.cgi?id=15493#c15
19:13:26 <[mbot> Bug 15493: critical, release_blocker, bugsquad, NEW , Graphics goes crazy when changing color depth on Broadwell-U, kernel, x11-driver-video-intel, ldetect-lst, drakx-kbd-mouse-x11
19:13:57 <MrsB> seem to have plymouth problems, some nvidia & fglrx problems
19:14:34 <lewyssmith> I should be able to try the latest Gnome &Classic DVDs tomorrow.
19:14:37 <MrsB> so intel, nvidia and amd, otherwise we're fine \o/
19:15:36 <wilcal> lol i've got two mice on my table. was using the wrong one
19:15:47 <DavidWHodgins> :-)
19:15:52 <tjandrews> Having no problems at all with the nvidia 304 driver. My card:GeForce 6200OC.
19:16:07 <MrsB> sign of old age that Bill!
19:16:32 <wilcal> Good success here with the lastest Live media except for the "Oh No" thingy
19:16:48 <MrsB> tjandrews: does the 64bit dvd or dualdvd in 64bit work for you?
19:16:54 <ennael> hi there (around using 3G connection)
19:16:58 <wilcal> Was using my Raspberry Pi II mouse :-))
19:17:16 <MrsB> morning ennael
19:17:19 <tjandrews> Haven't tried them.
19:17:41 <MrsB> try the dualdvd please and check for bug 15253
19:17:42 <[mbot> Bug https://bugs.mageia.org/show_bug.cgi?id=15253 major, release_blocker, ennael1, NEW , 5b3: Display corruption once the cursor moves (64bit is KO, 32bit is OK) with 16bpp & 24bpp (OK with 15bpp), kernel
19:18:05 <MrsB> i think it affects all non current nvidia cards
19:18:15 <Tonyb_> EFI issues: agree should probably only have one EFI partition, use grub2-efi to boot others.  Any reason to go beyond this?
19:18:30 <tjandrews> No significant experience in working with 64-bit. Might find every single pitfall there is.
19:18:38 <DavidWHodgins> Tonyb_: Nope
19:18:42 <lewyssmith> Tonyb_: Seconded.
19:19:12 <tmb> sorry... I was reading pad...
19:19:16 <MrsB> it's exactly the same really tjandrews, just different
19:19:22 <Tonyb_> my EFI formatting issues not found by others.  I'll re-do it all later today
19:19:48 <tjandrews> MrsB: I've heard THAT one before...
19:19:52 <wilcal> Testing UEFI in Vbox seems quite successful
19:20:25 <lewyssmith> Encouraging.
19:20:33 <MrsB> most of the uefi problems seem fixed now
19:20:48 <tmb> I think we are mostly in good shape... the Gnome "oh no" part is annoying
19:20:48 <wilcal> or reduced to just errate comments
19:20:58 <Tonyb_> I take it that RIAD is all dmraid for M5?
19:21:08 <wilcal> Good enough for M5, make it better in M6
19:21:27 <Tonyb_> s/RIAD/RAID
19:21:35 <lewyssmith> We guessed!
19:22:10 <DavidWHodgins> Tonyb_: I believe real hardware raid is supported too, though it should be invisible to the os.
19:22:16 <wilcal> tmb I've noticed the number of cauldron updates has been very subdued lately
19:22:25 <wilcal> seems pretty stable
19:22:46 <tmb> Tonyb_, yeah, we rely on dmraid for everything right now... we have some wip code for detecting mdadm managed Intel raids, but it needs more changes to drakx than I'm willing to accept at this point
19:23:00 <Tonyb_> Noted
19:23:07 <tmb> and of course hw raid we always support
19:23:12 <MrsB> yes no more extras now please, let's fix what we have :)
19:23:29 <wilcal> need to get this thing out the door
19:24:12 <DavidWHodgins> Let's plan on releasing the RC Monday, unless RC blockers are found between now and then.
19:24:26 <MrsB> well let's see it properly tested first please
19:24:36 <MrsB> very few have looked at current isos
19:24:36 <tjandrews> I've seen a grumble or two on Usenet on how long it's taking. But that's to be expected.
19:24:38 <tmb> there is one "fix" that seem to cure the gnome "oh np", and that is to simply drop fglrx drivers from the isos
19:24:51 <wilcal> CI's when?
19:25:11 <MrsB> it Oh No's in vbox again now too
19:25:50 <MrsB> last build fixed that iirc
19:25:51 <tmb> (and stick them in "Live Nonfree" repo so they are available after install if wanted)
19:26:22 <MrsB> will that affect support for new hw?
19:27:21 <MrsB> #info Please all test the current ISOs
19:27:38 <MrsB> #info upgrades with online medias added are now fixed
19:28:04 <tmb> yeah, I can reproduce the vbox "oh no" and it too went away after dropping fglrx, so it seems the fglrx is messing up mesa / GL support even if the hw is not there
19:28:22 <marja> bizarre
19:28:28 <MrsB> that's strange
19:28:35 <tmb> (and despite me trying to force ldconfig -X everywhere...
19:28:48 <MrsB> would blacklisting it help?
19:29:10 <wilcal> didn't we have a release where we released just KDE or was that Mandriva?
19:29:25 <wilcal> Gnome to follow
19:29:34 <tmb> well, on live media that means the same as stickng it in nonfree
19:29:44 <MrsB> we've done similar for live or classic before but at this stage there's little point
19:30:00 <lewyssmith> Why does my Radeon Gnome Live not show the problem?
19:30:14 <DavidWHodgins> wilcal: I don't remember a kde only release under Mageia or Mandriva/Mandrake.
19:30:39 <DavidWHodgins> lewyssmith: My understanding is that it's only some radeon cards.
19:30:40 <wilcal> Maybe it was in Beta or something
19:30:46 <tmb> lewyssmith, yeah, that's the problem. it seems both hardware and timing dependant :(
19:31:49 <tmb> So yes, we could keep it on isos and tell people that hit it to either do the "install mode" directly or use classical isos...
19:32:45 <MrsB> in live mode is not so important as long as when installed it is used
19:34:30 <tmb> I also plan to test the new fglrx 15.3 beta that was released to ubuntu to see if it would be more stable, but I didn't want to put that on RCs
19:35:47 <MrsB> could maybe make a separate one with it for Alan to test?
19:35:58 <tmb> I hope to be able to debug the crashing still before final, but I dont think it should hold up RC
19:36:31 <MrsB> I think we're all pretty weary of the RC now
19:37:01 <wilcal> time to get this out the door
19:37:03 <MrsB> As long as we make it clear we've identified these issues and should have them fixed before final
19:37:16 <DavidWHodgins> s /should/hope/
19:37:17 <tmb> "hopefully"
19:37:35 <MrsB> Could we re-establish the network config on lives in final please
19:37:48 <MrsB> in finish-install
19:38:22 <marja> MrsB: it was there
19:38:36 <MrsB> I'm sure we forced that at one point, in mga3 or early mga4 maybe
19:38:49 <marja> MrsB: with the last KDEliveDVD (or have I dreamt that?)
19:39:18 <MrsB> maybe if you have wifi only?
19:39:38 <tmb> it's always been disabled on live medias if working network is detected... but due to a bug in earlier mga release we failed to reliably detect working connection so we showed the question :)
19:40:07 <tmb> but yes, I can force the network window to be shown if wanted
19:40:07 <MrsB> I'll search for the bug, I'm 90% certain we forced it
19:40:23 <marja> MrsB: ah, maybe I had forgotten to set it up in live mode, the second time I started it before really installing
19:40:41 <DavidWHodgins> We do need a way then, to set the hostname, but that's an enhancement for Mageia 6, I think.
19:41:08 <MrsB> I think it would be useful to force it, setting the hostname isn't straightforward after installation.
19:41:14 <marja> DavidWHodgins: manahost did it easily
19:41:22 <marja> DavidWHodgins: but that's not on the iso
19:42:14 <MrsB> Plymouth is the next most visible issue
19:43:07 <MrsB> and nvidia corruption in installer
19:43:09 <tjandrews> Uh-oh. Something's come up, and I have to go. MrsB, downloading the DualDVD now. Will try it later tonight.
19:43:10 <tmb> Is that only happening on gnome or does it show up on kde too ?
19:43:37 <marja> tjandrews: have a nice evening
19:43:42 <MrsB> seems both from classic isos, gnome only from lives - in my tests anyway
19:43:53 <MrsB> Nite TJ
19:44:08 <wilcal> later tj
19:44:14 <tmb> so classic iso with kde shows it ?
19:44:32 <MrsB> reported by TJ earlier yes
19:44:43 <MrsB> I've only done a gnome install from classic so far
19:45:03 <MrsB> i'll do kde first thing tomorrow and work through the others too
19:45:53 <MrsB> https://bugs.mageia.org/show_bug.cgi?id=15666
19:45:54 <[mbot> Bug 15666: normal, release_blocker, bugsquad, NEW , After install from Classical media, boot process from Grub to Log in is in scrolling text
19:46:02 <tmb> ok, that rules out gdm session management fixes... The other change that happend was some drm race fixes in kernel... I wonder if plymouth somehow relied on that "broken code"
19:46:40 <MrsB> well, gnome is the bad guy on live isos
19:46:55 <MrsB> kde seems ok installed from those
19:47:13 <lewyssmith> Not for me lately: it doesn't.
19:47:19 <marja> te scrolling text is with Live KDE in live mode, too
19:47:20 <MrsB> oh?
19:47:36 <wilcal> kde's been pretty solid for weeks
19:47:45 <MrsB> oh well, there we go then. It's both.
19:47:58 <marja> ah, and true, my last installs had it, too (scrolling text)
19:48:10 <tmb> yeah, I cant reproduce the missing plymouth here on my installed systens :(
19:48:45 <MrsB> I added a journal to the bug from a classic gnome install
19:48:53 <marja> but some older installs do not have it, after updating
19:49:12 <MrsB> i'll add more journals from kde etc tomorrow too then
19:49:24 <MrsB> and xorg logs
19:51:33 <MrsB> I think the focus of the RC release should be the implementation of uefi support and ... these are the other bugs we've identified but we need wider testing now we can concentrate on the rest
19:52:03 <lewyssmith> Seems reasonable.
19:52:17 <wilcal> i support that
19:52:20 <tmb> yeah, I think we are good enough to go for wide testing
19:52:53 <MrsB> Let's all please have a push to test what we have now and as long as there are no new showstopper we'll plan to release them
19:53:06 <MrsB> # info Let's all please have a push to test what we have now and as long as there are no new showstopper we'll plan to release them
19:53:10 <MrsB> oops
19:53:15 <MrsB> #info Let's all please have a push to test what we have now and as long as there are no new showstopper we'll plan to release them
19:54:19 <MrsB> #info and I'd like to say a big well done and thankyou to everybody who has worked on them, building/fixing them and endlessly testing them
19:54:45 <tmb> so a go/no-go on monday council ?
19:54:56 <MrsB> sounds ok, yes
19:55:05 <DavidWHodgins> I think that's appropriate.
19:55:25 <MrsB> #info we'll decide go/no-go on Monday at the council meeting so please make any major issues know ASAP
19:55:35 <tmb> and all prepared for "go" so we csn push it then
19:55:53 <MrsB> we'll need to let atelier know
19:56:15 <tmb> yep
19:56:23 <MrsB> ennael ok?
19:57:38 <MrsB> i guess shes been 3G'd
19:57:50 <MrsB> let's move on then :)
19:57:53 <MrsB> thanks guys
19:57:55 <DavidWHodgins> #topic Testing updates - We're doing pretty well, considering
19:58:10 <MrsB> So yeah, we're doing pretty well considering
19:58:19 <MrsB> kernels will wait until after release
19:58:31 <wilcal> A little more testing on the kernels and they're outta there
19:58:32 <MrsB> we always seem to get kernels and isos at the same time
19:58:41 <wilcal> some please look at them
19:58:45 <wilcal> someone
19:58:56 <MrsB> everybody is busy elsewhere atm
19:59:04 <wilcal> kernels look ok
19:59:17 <DavidWHodgins> That's why we'll wait for more kernel testing, after the RC is out.
19:59:26 <MrsB> yep
19:59:31 <wilcal> next week
19:59:34 <tmb> I have them running on all live systems and servers I have control over, including Mageia servers :)
19:59:45 <MrsB> show off :P
19:59:54 <lewyssmith> I have not been able to do any update testing for some time, so please excuse my departure on this topic. Goodbye all.
19:59:56 <Akien> I'll push atelier to get the RC blog post prepred
19:59:58 <tmb> that's all x86_64 systems btw
19:59:59 <Akien> *prepared
20:00:02 <wilcal> Vbox is good to go with them
20:00:07 <DavidWHodgins> lewyssmith: Have a good night.
20:00:15 <Akien> (sorry my comment is a bit late, I was reading the backlog :p)
20:00:28 <MrsB> thanks Akien, I'll let stormi know too
20:00:33 <Tonyb_> Bye Lewis
20:00:38 <MrsB> Nite lewis
20:00:52 <wilcal> later lewys
20:01:12 <MrsB> So after ISOs are release, all please drop onto updates and check over the new kernels
20:01:54 <MrsB> Is there anything scary there?
20:02:39 <DavidWHodgins> The two perl updates, we may need to only test that they install cleanly.
20:03:03 <MrsB> i'll validate perl-Module-Signature after the meeting, rindolf tested it already
20:03:14 <DavidWHodgins> The rest just need to actually have some time spent on them.
20:03:25 <MrsB> yeah
20:03:28 <DavidWHodgins> MrsB: setup too
20:03:33 <MrsB> yep
20:03:54 <MrsB> tmb: I'll replace the existing advisory with the new one for that, is that Ok?
20:04:19 <Tonyb_> Excuse me. work calls
20:04:28 <MrsB> Nite Tonyb_
20:04:33 <DavidWHodgins> Thanks Tonyb_
20:05:30 <MrsB> he's gone again :\
20:05:32 <tmb> I'd rather add the info to same advisory than replacing it ... so people that has seen first round understand why it pops up again
20:06:07 <MrsB> yeah so reuse the same file, just update the info
20:06:26 <DavidWHodgins> tmb: Including keeping the ID?
20:06:27 <tmb> something like "Update Apr 16th, ... we needed to fix this part too..."
20:06:52 <MrsB> is it generally better to use a new bug or is this ok for you?
20:07:41 <DavidWHodgins> My preference would be for separate bug reports.
20:07:52 <MrsB> me too, just for our own QA process
20:08:09 <tmb> well current infra will make the old advisory disappear if we switch id on it, so that's not nice...
20:08:13 <MrsB> others say differently but we need to decide really to avoid this in future
20:08:49 <DavidWHodgins> Like a cve, I think an update that fixes a prior update should get at new id.
20:08:58 <tmb> technically we should fix infra to cope with revisions of advisories, but that wont happend for now
20:09:26 <tmb> and yes, we have used new bug and id before when "re-fixing" an issue
20:09:38 <DavidWHodgins> So for this update, just change the srpm, and add info to the description?
20:09:54 <MrsB> atm we can still go either way but it sounds like it's best with a new bug, until somethign changes
20:10:41 <tmb> well, pushing a new advisory makes it possible to reference old one and explain additional fixes needed that way...
20:10:58 <MrsB> Well let's decide then..
20:11:04 <MrsB> Votes for new bug..
20:11:12 <MrsB> o/
20:11:22 * DavidWHodgins votes yes
20:11:34 <wilcal> o/
20:11:47 <tmb> yeah, I think we can go for new one...
20:12:13 <DavidWHodgins> But as this affects developers, and sysadmins too, I think it should be proposed to, and decided by the council.
20:12:54 <MrsB> it doesn't though to my mind. Once it's assigned to QA it's a QA bug
20:13:17 <MrsB> we follow our procedures and workflow
20:13:24 <MrsB> same as devs follow theirs
20:13:31 <tmb> to cover the fact that the old rpms were removed, just add a note on old advisory that we removed it and reference the new advisory when its pushed
20:13:42 <DavidWHodgins> It's still up to the developers to create the new bug, before assigning to qa, and sysadmin push procedures (if the decision is made not to use a new bug).
20:13:47 <tmb> (and why we removed it)
20:14:01 <MrsB> we've previously split bugs where necessary ourselves Dave
20:14:10 <DavidWHodgins> True
20:14:54 <tmb> yeah, for example just re-open the once cloned & closed bug, track it there and push it that way
20:15:08 <MrsB> #info Until infra can be changed to handle it, for situations such as the setup package in future we'll use a new bug and separate advisory which can reference the original
20:15:32 <DavidWHodgins> We should let developers and bug-squad know that we've decided to use new bug reports, once an update has been pushed.
20:16:29 <MrsB> I can send an email but it's somethign we can handle ourselves when needed. Hopefully it shouldn't be needed often.
20:16:37 <DavidWHodgins> Ok
20:17:22 <DavidWHodgins> First time I can remember this happening, since we started creating the svn advisories.
20:17:40 <MrsB> yeah, certainly first time we've atcually removed an update
20:18:19 <MrsB> anyway, let's move on. It's MrsB's roundup
20:18:29 <DavidWHodgins> #topic Luigi's roundup
20:18:43 <wilcal> It's Luigi time
20:18:58 <MrsB> #info Luigi12 is not available today so sent a list of 'coming soon' to qa-discuss ML
20:19:27 <DavidWHodgins> #topic Anything else?
20:19:39 <wilcal> Not from me
20:19:40 <DavidWHodgins> Nothing else here
20:19:53 <tmb> nor from me, I will go to sleep in time for once :)
20:20:01 <wilcal> zzzzzzzzzzzz
20:20:01 <DavidWHodgins> ☺
20:20:03 <MrsB> #info There is concern at the moment that ruby needs attention, there is an update pending for ruby itself and 3 others for ruby packages
20:20:10 <MrsB> you jumped the gun :P
20:20:15 <DavidWHodgins> Oops
20:20:29 <tmb> good night all
20:20:35 <wilcal> nite tmb
20:20:39 <MrsB> #info also dpkg please Bruno :)
20:20:39 <DavidWHodgins> Have a good night tmb
20:20:49 <MrsB> Nite tmb
20:20:50 <marja> good night tmb
20:20:58 <MrsB> So is there anything else?
20:21:39 <DavidWHodgins> Time for countdown. :-)
20:21:49 <MrsB> can do!
20:21:51 <MrsB> T - 5
20:21:55 <wilcal> bye all
20:21:59 <MrsB> thanks for coming everybody
20:22:03 <marja> wilcal: bye
20:22:03 <MrsB> 4
20:22:05 <MrsB> 3
20:22:06 <MrsB> 2
20:22:07 <DavidWHodgins> Have a good night everyone
20:22:08 <MrsB> 1
20:22:10 <MrsB> #endmeeting