19:04:39 <DavidWHodgins> #startmeeting
19:04:39 <Inigo_Montoya> Meeting started Thu Mar 29 19:04:39 2018 UTC.  The chair is DavidWHodgins. Information about MeetBot at http://wiki.debian.org/MeetBot.
19:04:39 <Inigo_Montoya> Useful Commands: #action #agreed #help #info #idea #link #topic.
19:04:45 <DavidWHodgins> #topic Who's new?
19:04:57 <rindolf> sophie  is back
19:05:03 <DavidWHodgins> Anyone here who hasn't been to a qa team irc meeting before?
19:05:38 <DavidWHodgins> #topic QA team election and my status
19:05:53 <wilcal> You doing ok
19:06:02 <DavidWHodgins> Basically, I'm just feeling very tired. Not sure why.
19:06:12 <DavidWHodgins> Just needed to take a break.
19:06:30 <DavidWHodgins> I'm not  quitting the team, just need to take a bit more time to rest up.
19:06:31 <wilcal> We were worried
19:06:51 <rindolf> DavidWHodgins: i see
19:06:55 <wilcal> Anytime anyone needs a break any time and for any amount of time just do it
19:07:08 <DavidWHodgins> Sometimes I let things get to me, and just have to get away for a while.
19:07:24 <tarazed_> Lewis sends his apologies - he is travelling.
19:07:26 <DavidWHodgins> Sorry for worrying everyone so much though.
19:07:38 <wilcal> I now live in an interesting place where getting away is an every day thing :-))
19:07:44 <DavidWHodgins> lol
19:07:46 <tjandrews> But, anyone, if you are leaving for more than just a "break" please tell us.
19:08:26 <DavidWHodgins> So I'm still around. The election results previously announced stand. Any questions or comments?
19:08:41 <wilcal> Not from me.
19:08:48 <tarazed_> Suits me
19:08:57 <tjandrews> None here, except for an expression of great relief.
19:09:03 <Benmc> good to hear, no other comment
19:09:03 <DavidWHodgins> #topic Kernel test status
19:09:05 <tarazed_> Indeed
19:09:20 <wilcal> I like the latest kernel
19:09:32 <wilcal> looks good here
19:09:38 <DavidWHodgins> Working ok for me, though I haven't spent much time using it.
19:10:02 <tarazed_> It has been pretty well hammered but what about non-SSE2 machines?
19:10:17 <tjandrews> I broke my own rules and put it on my production install. Working nicely.
19:10:28 <DavidWHodgins> I'm not sure if anyone here still has any non-SSE2 cpus
19:10:31 <Benmc> i have one, but but limited ram
19:10:56 <Benmc> doesnt like sddm
19:11:13 <DavidWHodgins> Even this 10 year old laptop has sse2
19:11:38 <tmb> Benmc, you are talking about the QT test ?
19:11:42 <wilcal> yours is older then mine but not by much
19:12:10 <DavidWHodgins> tmb Do you want to go ahead with this one or wait for the ext4 bug fixes annoucnced today?
19:12:26 <tarazed_> Benmc: Any chance you could try it?  It is about the only thing holding it back.
19:13:07 <tjandrews> I have a Dell that's 14 years old (I think) and it has a 64-bit P4.
19:13:33 <tmb> DavidWHodgins, they are still discussing the fixes for the ext4 stuff, so no need to wait...
19:14:14 <DavidWHodgins> Ok. I'm inclined to say go ahead and push these kernel updates then. Anyone object?
19:14:24 <wilcal> not from me
19:14:29 <tjandrews> I'm good.
19:14:57 <tarazed_> Yeah, OK
19:15:28 <DavidWHodgins> #topic Plasma/kf4/qt updates, and qarepo.pl
19:15:55 <DavidWHodgins> No problems that I've seen in my limited testing. Haven't looked at the qarepo.pl script
19:15:56 <wilcal> I am becoming quite comfortable with qarepo.pl
19:16:13 <tarazed_> Me too - a neat application.
19:16:13 <wilcal> it will have a lot of uses other then this one
19:16:30 <wilcal> I am very uncomfortable with this update
19:16:33 <tjandrews> Martin has to do an update. It isn't enabling the local repo for updates.
19:17:02 <tarazed_> You sure?  It worked here.
19:17:05 <wilcal> And may never agree to release it. So others must push it
19:17:10 <DavidWHodgins> Saw that. Will try out the script myself later.
19:17:15 <wilcal> It is very high risk to me
19:17:32 <wilcal> An important item is missing let me explain
19:17:49 <Benmc> (- a few x2 )sorry (nappy run) will try to test today
19:17:57 <wilcal> So the three bugs all have an initial listing of the rpms that are being updated
19:18:08 <wilcal> QT just got a new listing of rpms
19:18:09 <tarazed_> Benmc: Thanks
19:18:44 <wilcal> Plasma and kf4 are still awaiting a new listing and there have been changes
19:19:28 <bria_n> Hi All
19:19:42 <wilcal> so until i see a new listing if the rpms on all three bugs and can work with qarepo.pl I'm not supporting the release
19:19:43 <tarazed_> Hi brian & herman
19:19:45 <hviaene> Hi all
19:19:54 <wilcal> Hi bria_n
19:19:56 <tjandrews> Four bugs, wilcal. Don't forget the kde applications bug.
19:20:28 <wilcal> ok
19:20:37 <DavidWHodgins> Clearly the list has to be sorted out before the updates can be pushed. That has to be done anyway before the advisory can be added to svn. It's the advisory in svn that controls which srpm packages get pushed as part of the updates
19:20:42 <wilcal> 100's of packages and they change
19:21:16 <tjandrews> Not so many changes lately.
19:21:42 <wilcal> as I go (slowly) along and get more familiar with qarepo.pl others may override me and push it on. And I'm ok with that
19:21:47 <DavidWHodgins> It's expected that the list of packages will change during testing, as bugs found during the testing get fixed. That's normal.
19:22:35 <wilcal> So you are head guy here David you've got to make the call when this is settled down, tested and ready for release
19:22:35 <DavidWHodgins> While qarepo.pl is a nice to have tool to help in future largee updates, it's not part of the updates itself. It's a seperate tool
19:22:45 <wilcal> just like we just did with the latest kernel
19:22:52 <bria_n> understood
19:23:09 <wilcal> And that's what make it so valuable
19:24:02 <DavidWHodgins> Also, just like to remind everyone that some regressions are expected and acceptable in a massive update like this. It fixes a lot more problems then it creates so that overrides the few (if any) regressions.
19:24:02 <wilcal> Are people just using "urpmi --auto-update" to test this thing
19:24:15 <bria_n> So for qt5, plasma 5 - we are waiting on four fixes then?
19:24:21 <tjandrews> This actually isn't as bad as the changes that come as we prepare for a new release.
19:24:41 <DavidWHodgins> On my primary system I have been. On my test installs I've been limiting it to what's listed in the various bug reports.
19:25:42 <bria_n> I followed the same theme as DavidWHodgins.  Just on the qt5, plasma update the update failed then the DE crashed
19:25:43 <wilcal> one thing i tried was to disable all the repos and only use the one created by qarepo.pl
19:25:57 <wilcal> does that sound sensible?
19:26:03 <bria_n> then I fell back to command prompt and did the --auto-update
19:26:27 <bria_n> kind of what I suggested
19:26:38 <tmb> wilcal, no, you always need core release and core updates enabled
19:26:49 <wilcal> ok thks
19:26:54 <DavidWHodgins> wilcal: No, as it's possible for one of the new packages to require something from existing release or updates repos
19:27:12 <wilcal> so just get down to core release and core updates and the qarepo.pl
19:27:21 <tjandrews> But disable all the testing repos.
19:27:36 <wilcal> got it
19:28:13 <DavidWHodgins> bria_n: The latest test I did was using a vb snapshot with no updates from testing, and then using auto-select with testing enabled. That went ok, so it's probably a matter of there being rpm packages available that are not listed in the bug report
19:28:22 <wilcal> so we await a new list of the rpms in the four bugs with Qt probably complete now
19:29:13 <bria_n> :DavidWHodgins - that makes sense
19:29:35 <wilcal> is all this an unending task for the packagers
19:29:55 <DavidWHodgins> Yeah. When I go to prepare the advisory, I'll compare the srpms available to what's listed in the bug reports to see if I can spot what's missing.
19:29:59 <wilcal> this things changes all the time and so much that its never going to be stable
19:30:42 <DavidWHodgins> wilcal: It does stabalize as we find fewer and fewer bugs that can be fixed by our packagers (vs upstream).
19:31:01 <bria_n> let's see, I'm thinking it'll be 99% with some risk, but not bad
19:31:05 <wilcal> light at the end of the tunnel
19:31:23 <DavidWHodgins> Unlike standard updates, we are primarily looking for packaging bugs, not the same level of testing we do for normal updates.
19:31:27 <wilcal> Kudos to Martin for qarepo.pl
19:31:42 <bria_n> yep - I'll have to jump on board of that
19:32:17 <tjandrews> I've been using it on my production install for two weeks, installed the old-fashioned way, deselecting what I didn't want in Mageia Update. It's been rock-solid.
19:32:35 <bria_n> that was my experience once it was installed fully
19:32:54 <bria_n> though I did purposefully blow away my laptop image
19:32:56 <DavidWHodgins> I'll try and sit down and prepare the advisories in the next day or so. Will update the bugs to confirm any packages I find that appear they should be included
19:33:14 <wilcal> sounds like a plan
19:33:50 <DavidWHodgins> So tenatively this weekend we should be ready for this mass push of the new updates
19:34:04 <DavidWHodgins> Can't spell today. :-)
19:34:17 <bria_n> <brian> bites his nails.
19:34:34 <DavidWHodgins> #topic Testing updates
19:34:55 <DavidWHodgins> I haven't looked at the list this week, so can't help much there.
19:35:14 <wilcal> So we'll have a final stable listing of the rpms
19:35:15 <bria_n> I think Kernel 4.14.30 is solid
19:35:19 <wilcal> it is
19:35:58 <tjandrews> The list looks bad, but take away the Plasma stuff and it looks better.
19:36:08 <tarazed_> puppet still needs a response.  Should be simple - according to tmb something about a service pack.
19:36:14 <bria_n> let's release 22026.  It tested out, just a pain in updates
19:37:01 <bria_n> 22734 - those in the know seemed to get it to work.
19:37:15 <bria_n> ...that excluded me....
19:37:33 <wilcal> squarrelmail I don't know how to test
19:37:42 <tarazed_> Spent days on that one
19:37:42 <DavidWHodgins> bria_n: I'm really not sure about bug 22026. If a user has a nextcloud server running, installs the update and doesn't do anything, doesn't it break the running server?
19:37:44 <[mbot> Bug: ['Upgrade the nextcloud server in updates to prevent the mess we had in MGA5 with backports.', 'ASSIGNED', 'QA Team'] https://bugs.mageia.org/show_bug.cgi?id=22026
19:37:58 <bria_n> it does, but that's normal for nextcloud
19:38:06 <bria_n> <<my opinion>>
19:38:23 <bria_n> OwnCloud for a major release was equally bad
19:39:25 <bria_n> I'll leave it up to the leaders.  It seems we have documentation left if we do anything at all with it
19:40:02 <wilcal> It's one of those career apps. Get to know it well and you can write your own job ticket
19:40:23 <DavidWHodgins> Ok. Let's do it this way. This update we'll go ahead and release as an update. If we get many complaints then in future, it will go back to being in backports only.
19:40:41 <bria_n> I can accept that
19:40:47 <wilcal> ok from me
19:41:11 <DavidWHodgins> I don't like having it this way, but it's a rarely used enough package I think we can risk it, at least this once.
19:41:16 <tjandrews> I don't know enough to comment one way or the other.
19:41:19 <DavidWHodgins> phone. brb
19:41:44 <bria_n> <<theme to rocky in background --- everyone hear it?>>  ;-)
19:41:55 <wilcal> puppet is another app that's a career builder
19:42:27 <tjandrews> Dave: If it were my phone, it would probably be an opportunity to lower my credit card interest rate.
19:42:31 <bria_n> I'm very limited on bandwidth now, someone else has to take it
19:43:11 <bria_n> if it were mine it would be a fundraiser for clergy/children/women/men/police with cancer fund
19:43:47 <wilcal> I got 100's of calls to from moving services. Sometimes many many a day
19:44:05 <tjandrews> I've rejected hundreds of Carribean cruises.
19:44:11 <bria_n> ditto
19:44:20 <wilcal> soon as I contacted one it seems everyone in the moving business knew i was moving
19:44:31 <bria_n> ah --- the database
19:45:15 <bria_n> 389-ds-base looks easy enough, anybody new want to try?  Did John join and introduce?
19:45:44 <hviaene> I've done that one at least twice in the past
19:46:31 <bria_n> also we should see a new firefox hitting us soon I suspect
19:46:35 <bria_n> Security fix
19:46:59 <tjandrews> Must be overdue for a new Flash.
19:48:39 <wilcal> Latest Firefox 59.x really makes you work if you want to use flash
19:49:17 <hviaene> I need that one for eid-applications
19:50:23 <hviaene> But I don't have any issues with it.
19:50:33 <bria_n> I think they have a fix for 52 lts we are on
19:51:47 <DavidWHodgins> Back
19:51:53 <wilcal> Is there a problem with the latest Flash?
19:52:12 <wilcal> except that it's Flash
19:52:52 <tjandrews> Not that I know of.
19:53:32 <tjandrews> Firefox 52's days are numbered. Firefox 60 ESR due out in May.
19:53:36 <wilcal> Adobe has pushed Flash EOL to late 2020
19:54:33 <DavidWHodgins> Any other questions or comments on remaining updates?
19:54:52 <bria_n> none here
19:54:53 <wilcal> not from me
19:54:58 <hviaene> No
19:54:58 <wilcal> I'm done
19:55:02 <DavidWHodgins> #topic Anything else
19:55:09 <wilcal> Thanks for being here David. Super job
19:55:13 <wilcal> your the best
19:55:18 <DavidWHodgins> :-)
19:55:19 <DavidWHodgins> Thanks
19:55:52 <DavidWHodgins> Looks like countdown time then
19:55:56 <DavidWHodgins> T - 5
19:55:57 <wilcal> bye all
19:56:00 <DavidWHodgins> 4
19:56:06 <DavidWHodgins> 3
19:56:07 <hviaene> G'night all
19:56:10 <DavidWHodgins> 2
19:56:13 <DavidWHodgins> 1
19:56:20 <DavidWHodgins> Thanks for coming everyone
19:56:25 <DavidWHodgins> #endmeeting