17:00:52 #startmeeting F27-blocker-review 17:00:52 Meeting started Mon Nov 6 17:00:52 2017 UTC. The chair is adamw. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:52 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:00:52 The meeting name has been set to 'f27-blocker-review' 17:00:52 #meetingname F27-blocker-review 17:00:52 #topic Roll Call 17:00:52 The meeting name has been set to 'f27-blocker-review' 17:01:01 morning folks, who's around for some blocker review funtimes? 17:01:45 * siddharthvipul1[ is here 17:01:46 Morning...? 17:01:51 * lbrabec is here 17:01:55 * Kohane is here 17:01:59 * pwhalen is here 17:02:15 * kparal is here 17:02:15 adamw: is evening almost night for me.... 17:02:22 * coremodule is here! 17:02:41 .hello2 17:02:43 sgallagh: sgallagh 'Stephen Gallagher' 17:02:52 * nirik is lurking around 17:03:03 Kohane: PST is the one true timezone 17:03:32 adamw: PST? Is that a new chemical product? 17:03:42 .fire kohane 17:03:42 adamw fires kohane 17:03:51 LOL 17:04:07 #chair sgallagh lbrabec 17:04:07 Current chairs: adamw lbrabec sgallagh 17:04:22 impending boilerplate alert! 17:04:23 #topic Introduction 17:04:23 Why are we here? 17:04:23 #info Our purpose in this meeting is to review proposed blocker and nice-to-have bugs and decide whether to accept them, and to monitor the progress of fixing existing accepted blocker and nice-to-have bugs. 17:04:24 #info We'll be following the process outlined at: 17:04:24 #link https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting 17:04:26 #info The bugs up for review today are available at: 17:04:28 #link http://qa.fedoraproject.org/blockerbugs/current 17:04:30 #info The criteria for release blocking bugs can be found at: 17:04:32 #link https://fedoraproject.org/wiki/Basic_Release_Criteria 17:04:34 #link https://fedoraproject.org/wiki/Fedora_27_Beta_Release_Criteria 17:04:36 #link https://fedoraproject.org/wiki/Fedora_27_Final_Release_Criteria 17:04:38 who wants to secretarialize? 17:04:45 I'll do it! 17:04:57 .hello2 17:04:57 frantisekz: frantisekz 'František Zatloukal' 17:05:19 * sumantro is here 17:06:18 #info coremodule will secretarialize 17:06:24 hi sumantro and frantisekz 17:06:52 hey adamw 17:07:02 hi adamw 17:08:01 #info starting with the one proposed Final blocker 17:08:03 #topic (1494586) [abrt] gnome-shell: g_type_check_instance_is_fundamentally_a(): gnome-shell killed by SIGSEGV 17:08:04 #link https://bugzilla.redhat.com/show_bug.cgi?id=1494586 17:08:04 #info Proposed Blocker, gnome-shell, NEW 17:09:11 * Kohane is reading the bug 17:09:24 oh goody, more shell crashing 17:09:58 * adamw goes looking for a Shell folk 17:10:14 Petrol! 17:10:26 whoops,wrong Shell 17:10:41 LOL 17:10:45 coremodule: Time for a new password 17:12:22 upstream report: https://bugzilla.gnome.org/show_bug.cgi?id=789484 17:14:46 adamw: Same bug? 17:15:49 i think so, yes. 17:17:11 * mattdm is here 17:17:22 (and in another meeting, but there's life) 17:18:19 GNOME Shell bugs are unfortunate, but I'm not sure we want to set a precedent on blocking for every random crash. 17:18:36 Though the fact that it takes the whole session with it is particularly ugly. 17:19:21 TBH... I don't like it crashing but.... I'm not sure is a blocker. 17:20:16 I mean, it happens. And Gnome Wayland doesn't restart the session as Gnome with Xorg does, but... it's something that from to time happens. 17:20:48 sgallagh: *all* shell crashes on wayland take out the whole session, which is a big issue since we switched to wayland by default 17:20:50 Sure; at the same time, for the people to whom it's happening it is frequent 17:20:54 ... so, let's switch to Xserver by default and those crashes won't matter that much... :) 17:21:04 that makes me want to block on sufficiently-common shell crashes. 17:21:17 Yeah, that's why I'm fence-riding here 17:21:19 but that can open a can of worms. 17:21:20 * Kohane likes frantisekz idea... 17:21:47 the bug also references https://bugzilla.redhat.com/show_bug.cgi?id=1469129 , which looks similar but not quite the same 17:21:56 that one has 26 CCs 17:22:09 this one has 27 CCs 17:23:32 So... what do we do with this? 17:23:43 and FAF numbers seem to be broken 17:23:58 4 come from assigness etc. , so that looks like ~22 and 23 affected folks 17:24:10 which seems quite a lot for a beta 17:24:55 Yes, it is. 17:25:12 Well, I suppose it happens too often to ignore. 17:25:15 i'm going to see if the alleged reproducer in https://bugzilla.redhat.com/show_bug.cgi?id=1494586#c26 works for me 17:25:22 ok 17:25:45 yeah, it'd help if faf was more reliable here 17:25:49 or if we just knew how the heck to use it 17:25:55 (if that's the problem) 17:26:01 there *is* a gnome 3.26.2 update in the wings.... 17:26:21 mattdm: the upstream bug hasn't been closed or given any attention, though, so not sure if i'd expect that to fix anything 17:26:29 mattdm: Are you legitimately suggesting pulling in a megaupdate during Freeze? 17:26:34 but no mention about fixing this issue in 3.26.2 17:26:38 I just want to make sure I don't need to go to the optometrist. 17:26:50 sgallagh: no. I am not suggesting that 17:28:40 * sgallagh tries to round up cschalle 17:28:57 i'm already talking to mclasen in #fedora-desktop 17:29:05 we discussed it earlier 17:29:05 seems another instance of 'unclear bug' 17:29:12 I've pointed fmuellner at it 17:29:31 ah 17:29:41 also from earlier: 17:29:42 07:46:37> the backtrace isn't very enlightening I'm afraid 17:29:42 07:46:55> other than that it's something entirely different than the one about maximized windows 17:29:52 07:47:27> (it looks like something is trying to set an invalid gobject property on a StLabel, but it's too generic to tell anything more) 17:29:52 07:48:38> maybe we should consider turning on https://bugzilla.gnome.org/show_bug.cgi?id=789237 though 17:29:52 07:49:00> (that bug adds an env variable to dump the JS backtrace on segfaults) 17:31:37 So in short, this is serious but we have no idea what's causing it or how long it might take to fix it? 17:32:08 sgallagh: I don't think we can fix it from the abrt stack traces 17:32:10 that sounds...approximately correct, yeah. 17:32:24 This is fine. 17:32:44 otaylor: that commit to get a gjs trace when shell crashes would presumably help? 17:33:28 sgallagh: really needs a reproducer, or someone who sees it frequently getting some detailed debugging help 17:33:41 yes, getting a gjs stack trace would go a long ways 17:33:58 I'm going to see if I can repro it; one sec. 17:34:44 man, this hot shiny ball in the sky is really annoying. 17:34:58 Ah, wait. I'm on X11 on this sytem. 17:35:01 crud 17:35:21 adamw: what shiny ball? are you alright? 17:35:36 sgallagh: is the crash wayland specific, or just the crash taking down the session? 17:35:47 otaylor: Good question 17:35:51 * sgallagh checks his ABRT history 17:35:51 Kohane: i hear it's some star we're orbiting or something like that. 17:36:05 But I'm not expecting it to be as simple as "notification crashes gnome-shell" 17:36:10 adamw: Oh. I heard that too. 17:36:22 otaylor: there's a claimed reproducer in https://bugzilla.redhat.com/show_bug.cgi?id=1494586#c26 17:36:30 OK, I haven't seen it on this system. 17:36:43 otaylor: I think it happens in X too, but while Xorg restarts the session Wayland just crashes. 17:36:47 Does it happen on Live sessions? 17:36:48 https://bugzilla.redhat.com/show_bug.cgi?id=1494586#c13 claims it happens on X too. 17:37:06 If so, I'll throw it on this spare laptop I just found under a rock 17:37:13 i'm doing that atm 17:37:14 Yeah, the first link has a comment saying it happens with Xorg as well 17:37:19 (trying from a live session on a laptop) 17:37:34 I tried it in VM, but it seems suspend doesn't place nice with libvirt. can't be resumed 17:38:00 If it's not actually reproducible for others, probably just need to get fmuellner talking to Berend who seems to (for whatever reason) be seeing it frequently and able to reproduce it. 17:39:05 not crashing it here. 17:39:31 i wish we had a better framework for evaluating this kinda bug. :/ 17:39:55 adamw: I'm slightly leaning towards "Not a blocker because Fedora QA can't reproduce it" :) 17:40:14 heh 17:41:03 i guess i'm reluctantly leaning towards -1 on the basis that it's clearly not affecting everybody and we don't have any kinda confidence at this point that it's fixable in a reasonable time frame (per that wording we introduced last cycle) 17:41:22 it's really hard to say just how many people need to be seeing something like this to block, though 17:41:32 20+ seems like...a lot of people? but is it too many? i dunno. 17:41:43 otaylor: oh, btw, do you think https://bugzilla.redhat.com/show_bug.cgi?id=1469129 is related? 17:41:54 I think over 20 people is a lot. 17:42:22 adamw: I see no reason to think it is related 17:42:40 okay 17:42:49 so that's just another crash with a bunch of people hitting it...whee. 17:43:12 I wish we had a hardware inventory. 17:43:30 So we could at least see if it was common to Nvidia or something. 17:43:31 i wish i had a solid gold toilet. 17:43:35 yeah, that'd help. 17:44:33 so, i guess we talked this through about as hard as we can...votes? 17:45:02 -1 atm 17:45:02 I'm a weak -1 unless we get more information that it's going to hit a big percentage of users 17:45:36 -1 17:45:40 yea, -1 for now 17:45:44 -1 17:46:41 agreed, -1 17:46:47 I'll continue trying to get it to fail on my laptop as well 17:47:13 proposed #agreed 1494586 - RejectedBlocker (Final) - this is concerning as it's hitting quite a few people for a Beta. However, clearly not everyone is affected, and neither a reliable reproducer nor a clear cause analysis have been found yet. As this is being raised very late in the cycle, we feel we can only block the release on it with definition information indicating it will affect a broad range of users 17:47:46 ack 17:47:49 ack 17:47:50 ack 17:47:56 ack 17:48:05 wait, patch 17:48:11 s/definition/definite/ 17:48:16 ack 17:48:42 #agreed 1494586 - RejectedBlocker (Final) - this is concerning as it's hitting quite a few people for a Beta. However, clearly not everyone is affected, and neither a reliable reproducer nor a clear cause analysis have been found yet. As this is being raised very late in the cycle, we feel we can only block the release on it with definite information indicating it will affect a broad range of users 17:48:46 thanks sgallagh 17:48:48 sgallagh++ 17:48:49 adamw: Karma for sgallagh changed to 20 (for the f26 release cycle): https://badges.fedoraproject.org/tags/cookie/any 17:48:54 cookie for paying attention :P 17:48:58 heh 17:49:11 we have a couple of proposed FEs 17:49:13 #topic (1509996) Install color emoji fonts by default 17:49:13 #link https://bugzilla.redhat.com/show_bug.cgi?id=1509996 17:49:13 #info Proposed Freeze Exceptions, gnome-themes-standard, NEW 17:49:56 seems pretty late... 17:50:03 but emoji! 17:50:10 With no more blockers on the list, it seems unlikely another respin will happen 17:50:34 Freeze Exception for an emoji? 17:50:44 💩 17:50:48 lots of emoji, i think. 17:50:49 lovely! 17:50:58 I know but... 17:51:06 Also, -1 for this. 17:51:10 someone argued in the update thread that it's a bad idea to use a hard requirement here, which seems a reasonable argument too. 17:51:13 There's no reason it needs to be on the media 17:51:21 sgallagh: workstation live? 17:51:22 kparal: how did you send that? I didn't know IRC has emojis.... 17:51:29 Kohane: they're unicode. 17:51:32 Ah 17:51:43 you can send any unicode character over IRC. well, with a unicode-enabled client and server. which most are these days. 17:51:48 adamw: thanks, I didn't know 17:52:07 i think i'm -1 here too, bit late for mucking around with this. 17:52:12 anyway, I'm -1 on this 17:52:15 -1 17:52:20 -1 17:52:23 -1 17:52:28 adamw: Fine, I don't like the idea of making any non-blocker changes at this time (excepting maybe "FEs that would be blockers except it's a non-blocking arch") 17:52:34 -1 17:52:36 0 17:53:45 proposed #agreed 1509996 - RejectedBlocker (Final) - this seems like a relatively minor improvement (that only affects Workstation live sessions really) and we felt it's a bit late to be fiddling with comps and core package requirements for something like this 17:53:48 -1 17:53:51 grr 17:54:01 proposed #agreed 1509996 - RejectedFreezeException (Final) - this seems like a relatively minor improvement (that only affects Workstation live sessions really) and we felt it's a bit late to be fiddling with comps and core package requirements for something like this 17:54:13 ack 17:54:15 ack 17:54:17 ack 17:54:26 ack 17:54:29 ack 17:54:40 ack 17:55:09 ack 17:55:26 #agreed 1509996 - RejectedFreezeException (Final) - this seems like a relatively minor improvement (that only affects Workstation live sessions really) and we felt it's a bit late to be fiddling with comps and core package requirements for something like this 17:55:35 #topic (1507676) AArch64 disk images include '/etc/sysconfig/network-scripts/ifcfg-enp1s0' 17:55:36 #link https://bugzilla.redhat.com/show_bug.cgi?id=1507676 17:55:36 #info Proposed Freeze Exceptions, spin-kickstarts, MODIFIED 17:55:41 i almost feel like we already did this one? 17:55:51 oh, i did it in-bug. 17:56:58 * adamw really not sure what to say to this one. 17:58:12 why is that file problematic? 17:58:57 adamw: give me a moment to read... 17:58:58 kparal: it confuses people 18:00:02 This might be a silly question but... what is AArch64 ? 18:00:19 Kohane, 64bit arm 18:00:20 Kohane: ARM 64 18:00:35 Oh, okay, thanks 18:00:37 it's a non-blocking arch at present. 18:00:43 Yeah. 18:01:03 it's also a completely self contained change 18:01:05 I guess I'm okay with an FE on the off-chance that another respin happens 18:01:25 pbrobinson: i'm still not convinced by that. 18:01:37 pbrobinson: don't the same kickstarts get used for 32-bit arm and cloud disk images? 18:01:44 some of which are release-blocking. 18:01:48 adamw: nope, no they don't 18:01:55 hmmmm. /me fry eyes 18:02:39 as I explained in the bug report the fedora-disk* are currently just aarch64, the plan is eventually to move ARMv7 to consume them too, and maybe a x86 disk image but it doesn't happen yet 18:03:04 you can verify that by checking the includes and the pungi config if you don't believe me 18:03:38 okay. 18:03:46 then i guess fine 18:03:53 seems kinda trivial, but if it doesn't affect any blocking image, me 18:03:54 h 18:03:55 +1 18:05:49 so that's +2 18:05:51 +1 as well 18:05:51 any other votes? 18:06:02 +1 18:06:15 Dang, sorry guys, not trying to spam you with disconnect/reconnect messages... 18:06:28 +1 18:06:30 coremodule: No worries. 18:06:48 +1 18:07:40 proposed #agreed 1507676 - AcceptedFreezeException (Final) - this seems pretty minor, but it can't be fixed with an update and pbrobinson swears on his mother's life that it can't affect any images other than aarch64, so we'll grant an FE 18:07:54 pbrobinson: hope your mom has her affairs in order...:P 18:08:27 These meetings are fun... 18:08:31 adamw: LOL.... just you leave my mother out of this ;-) 18:08:34 okey dokey, moving onto beta 18:08:36 er, server beta 18:08:39 ack 18:08:47 heh, ack 18:08:49 ack 18:08:50 ack 18:08:56 #agreed 1507676 - AcceptedFreezeException (Final) - this seems pretty minor, but it can't be fixed with an update and pbrobinson swears on his mother's life that it can't affect any images other than aarch64, so we'll grant an FE 18:09:10 #info moving onto Modular Server Beta proposed blockers 18:09:18 there's a glitch in the matrix adamw 18:09:26 * adamw hears some sort of faint buzzing 18:09:39 a sort of whiny, australian buzzing 18:09:40 how strange 18:10:08 #chair pwhalen 18:10:08 Current chairs: adamw lbrabec pwhalen sgallagh 18:10:09 * pbrobinson goes to dig out some real blockers for adamw to lose sleep over ;-) 18:10:12 #topic (1509659) Modular Server is missing PackageKit 18:10:13 #link https://bugzilla.redhat.com/show_bug.cgi?id=1509659 18:10:13 #info Proposed Blocker, fedora-modular-release, ON_QA 18:10:51 +1 blocker (though allegedly fixed already) 18:11:16 +1 blocker 18:11:18 +1 18:11:35 beta blocker, right? 18:11:43 proposed #agreed 1509659 - AcceptedBlocker (Server Beta) - clear violation of "It must be possible to log in to the default Cockpit instance and use it to [...] Enrol the system to a FreeIPA or Active Directory domain" 18:11:44 yeah 18:11:45 kparal: Yes 18:11:46 criterion is beta 18:11:50 +1 blocker 18:11:52 +1 18:11:59 +1 blocker 18:12:27 Well, it's not 100% clear. But I won't argue the minutiae 18:12:45 (technically, cockpit can still enroll if you manually install all the packages ahead of time) 18:12:56 But realistically it violates the spirit of the criterion 18:13:24 oh great, now i'm hearing a faint whiny american buzzing 18:13:25 :P 18:13:33 ack/nack/patch? 18:13:34 LOL 18:13:40 ack 18:13:49 ack 18:13:50 ack 18:13:54 ack 18:13:56 ack 18:13:56 #agreed 1509659 - AcceptedBlocker (Server Beta) - clear violation of "It must be possible to log in to the default Cockpit instance and use it to [...] Enrol the system to a FreeIPA or Active Directory domain" 18:14:05 #topic (1509671) Modular Server is missing python-psycopg2 18:14:05 #link https://bugzilla.redhat.com/show_bug.cgi?id=1509671 18:14:05 #info Proposed Blocker, fedora-modular-release, ON_QA 18:15:32 +1, obv. 18:15:38 +1 18:15:41 +1 18:15:42 +1 18:15:51 +1 18:16:12 This is plain and simple to decide. I wish all bugs were like this. 18:16:15 +1 18:16:36 adamw: Well, I just don't file any of the complicated ones. 18:16:37 * sgallagh runs 18:16:47 +1 18:16:57 hehe 18:17:27 proposed #agreed 1509671 - AcceptedBlocker (Server Beta) - clear violation of "The core functional requirements for all Featured Server Roles must be met, without any workarounds being necessary" for the database server role 18:18:06 ack 18:18:22 ack 18:18:24 ack 18:18:30 ack 18:18:39 ack 18:18:59 #agreed 1509671 - AcceptedBlocker (Server Beta) - clear violation of "The core functional requirements for all Featured Server Roles must be met, without any workarounds being necessary" for the database server role 18:19:21 #info moving onto proposed Server Beta freeze exceptions 18:19:22 #topic (1508545) AArch64 requires shim-signed-13-0.6 18:19:22 #link https://bugzilla.redhat.com/show_bug.cgi?id=1508545 18:19:22 #info Proposed Freeze Exceptions, fedora-modular-release, ASSIGNED 18:19:38 This is one of those that would be a blocker if it was x86_64 18:19:43 +1, yeah. 18:19:50 So in my mind, that's pretty much an automatic +1 FE 18:20:34 +1 18:20:35 +1. this was a beta FE 18:20:35 can a new build be submitted as an update just for one arch? 18:20:48 +1 18:20:52 or this will also change shim on blocking arches? 18:21:43 just saying we could break it on blocking arches 18:21:47 kparal: That... is a good question. 18:22:01 We actually CAN restrict it to just one arch, where we couldn't in traditional Fedora 18:22:09 Though in this case I'm not sure that's a good idea 18:22:30 oh, i was misunderstanding this a bit 18:22:40 i thought a newer shim just hadn't been pulled into modular server for some reason 18:22:59 sgallagh: it's messy. which version do you put in the SRPMs? 18:23:03 adamw, right 18:23:08 .bug 1497854 18:23:08 sgallagh: Bug 1497854 – upgrade F26 - F27 fails on reboot due to missing shim.efi - https://bugzilla.redhat.com/1497854 18:23:14 This is what it originally fixed. 18:23:15 this is the same FE we had for classic beta 18:23:42 adamw: no, you're right. We basically just forgot to pull this in. 18:23:43 so we already sent 13-0.7 to stable for vanilla fedora? 18:23:52 Because when I went through the list of Beta blockers, I didn't check the FEs 18:23:57 okay. i'm less worried about this breaking other arches for Server, then. 18:23:58 yes 18:23:59 I'm lost... 18:24:01 since we know it works fine in vanilla. 18:24:04 so, still +1. 18:24:09 right, thanks adamw 18:24:41 sgallagh: it'd make sense to pull in 0.7 then, right? not 0.6? 18:24:54 Yes, I'll do that. 18:24:56 if that's what's in stable 18:24:57 okay 18:25:39 proposed #agreed 1508545 - AcceptedFreezeException (Server Beta) - this prevents installs on an entire (non-blocking) arch from working, so clearly worth an FE. the relevant shim-signed build is in 'regular' 27 Final and stable already, so we know it works 18:25:51 ack 18:26:13 ack 18:26:14 ack 18:26:21 ack 18:27:00 #agreed 1508545 - AcceptedFreezeException (Server Beta) - this prevents installs on an entire (non-blocking) arch from working, so clearly worth an FE. the relevant shim-signed build is in 'regular' 27 Final and stable already, so we know it works 18:27:11 #topic (1509934) mongodb fails installation because of libboost_chrono 18:27:11 #link https://bugzilla.redhat.com/show_bug.cgi?id=1509934 18:27:11 #info Proposed Freeze Exceptions, fedora-modular-release, NEW 18:28:11 Not a blocking role, but an important module. 18:28:17 That just turned up overnight 18:28:31 can this be installed from netinst as addon? 18:28:40 kparal: Not without fixing this. 18:28:54 The problem is that one of its deps is missing from the module, which means it's missing from the repository. 18:28:55 I mean if this module can actually be selected as part of some addon 18:29:14 otherwise 0day update is fine, no? 18:29:31 kparal: "It's complicated" (There's another bug we'll discuss a bit later on that) 18:29:36 ok :) 18:30:13 I guess +1 then 18:31:24 I'm 0 on this. Sorry. 18:31:35 * adamw gives it the sgallagh +1 18:32:15 kparal: I just mentioned that other bug in #fedora-qa, if you want to sneak an early peek at it 18:33:17 +1 from me 18:33:45 I think the fix is unlikely to destabilize anything else (since it's adding a missing package, not changing an existing one) 18:34:00 +1 18:34:09 +1 18:34:54 proposed #agreed 1509934 - AcceptedFreezeException (Server Beta) - sgallagh says there's a reason this can't be done as a post-release update, and it fixes installation of something that could pretty plausibly be needed in a Server product 18:35:06 ack 18:35:22 nice justification 18:35:23 Well, the reason is "it's selectable in Anaconda" 18:35:45 Which would result in it not working properly after installation, since anaconda can't install its deps 18:36:12 That said, we might opt to make it unselectable when we fix the other bug that's causing all of comps.xml to show up instead of just the available stuff 18:36:22 sgallagh: That's a good point 18:36:41 ack 18:36:49 ack 18:36:50 But I'm fine with this resolution 18:36:50 ack 18:37:26 #agreed 1509934 - AcceptedFreezeException (Server Beta) - sgallagh says there's a reason this can't be done as a post-release update, and it fixes installation of something that could pretty plausibly be needed in a Server product 18:37:26 ack 18:37:36 #topic (1509971) Modular Server is missing sscg 18:37:36 #link https://bugzilla.redhat.com/show_bug.cgi?id=1509971 18:37:36 #info Proposed Freeze Exceptions, fedora-modular-release, NEW 18:38:31 Mostly this just happened because mod_ssl grew a new dep on sscg after the module was created and no one updated the module. Trivial to fix, useful for the same reason as the previous BZ 18:38:38 +1 FE from me 18:38:50 +1 18:38:51 sure, fine. 18:39:07 +1 18:39:09 +1 FE 18:39:36 btw, i have a question here 18:39:46 Shoot me 18:39:51 what does the FE actually achieve here? 18:39:52 err, shoot 18:40:05 i mean, a regular FE means i send a push request that lets a bodhi update go through the freeze 18:40:10 adamw: We implemented a Freeze procedure this morning. 18:40:14 haha. okay. 18:40:24 We won't let updated module builds through to pungi-fedora without a Blocker or FE at this point. 18:40:29 do we have to do anything to actually get the changes 'pushed'? or are you taking care of it? 18:40:37 I'm gatekeeping it 18:41:04 I'll only send PRs to pungi-fedora with associated blocker/FE BZs 18:41:15 proposed #agreed 1509971 - AcceptedFreezeException (Server Beta) - this again fixes install of useful software on Beta and per sgallagh cannot be fully fixed with a post-release update 18:41:15 pungi-fedora decides which module builds make it to a compose 18:41:16 okay. 18:41:29 specifically, the variants-modular.xml file 18:42:01 For the record: https://pagure.io/pungi-fedora/pull-request/437 is how we switched into "Freeze" 18:42:32 So now it's got exact versions specified instead of "latest on the branch" 18:42:33 ack/nack/patch? 18:42:41 ack 18:42:49 ack 18:42:51 ack 18:43:18 ack 18:43:31 #agreed 1509971 - AcceptedFreezeException (Server Beta) - this again fixes install of useful software on Beta and per sgallagh cannot be fully fixed with a post-release update 18:43:42 #topic (1509973) fonts/everything profile installation fails because of missing dependencies 18:43:42 #link https://bugzilla.redhat.com/show_bug.cgi?id=1509973 18:43:42 #info Proposed Freeze Exceptions, fedora-modular-release, NEW 18:44:35 Short version is that the module was created with an "everything" profile that was self-conflicting. 18:44:40 So we need to back that out. 18:45:01 That said; I suppose this doesn't strictly have to be on the media, since I don't think this profile is going to be visible. 18:45:28 what is the everything profile? 18:45:28 or, what is a profile? 18:45:30 So I can back this change out if preferred (it was the last to go in before we formally Froze, though I had mostly just expected it to get the nod) 18:45:45 kparal: Thanks, I was thinking the same question. 18:46:05 OK, so when you enable a module, you specify a "stream", which is basically like a major version. e.g. Node.js 8 vs 6 18:46:16 After that, you have profiles, which are a set of packages out of that module to install. 18:46:34 There's a special-case one named "default" which will get picked if you don't specify another one. 18:46:56 so something like hard and soft dependencies for rpms 18:46:59 Profiles are used for modules like Samba so you can pick the server, the client, etc. 18:47:20 or perhaps like subpackages 18:47:25 Mmmh.... now I understand a bit better... 18:47:27 ok, just wanted to get the idea 18:47:31 In this particular case, karsten got ambitious and included an "everything" (non-default) profile that installs all available fonts 18:47:43 However it turns out that for whatever reason, they can't actually ALL be installed properly. 18:48:03 (I think some of them conflict with each other, but I didn't double-check that this is the case) 18:48:27 So the fix is to drop the ones that conflict from the "everything" profile; we've already checked that none of those are needed by Anaconda. 18:48:51 kparal: i think of it more as like the 'mandatory / default /optional' thing in comps. 18:49:07 Well, it's closer to metapackages than anything else 18:49:39 when you say "So I can back this change out if preferred" what do you mean? 18:49:48 what 'change'? back it out how? prefer to what? 18:50:23 adamw: The fix for this had already made it into the builds before I snapshotted for the Freeze on pungi-fedora 18:50:36 But I can manually revert it to the version that had this bug if we don't want to give it an FE 18:50:50 sgallagh: what is your preferred approach? 18:50:52 Mostly because karsten starts work a few hours before I do :) 18:50:52 oh. no. that seems silly. 18:51:00 sgallagh: just tell us what to vote 18:51:11 :) 18:51:15 adamw: +1 18:51:17 It's minimal risk, so I'm in favor of it 18:51:20 alrighty 18:51:20 +1 18:51:20 +1 18:51:21 :P 18:51:24 +1 18:51:25 +1 18:51:27 +1 18:51:28 this is excellent bureaucracy btw 18:51:36 I noticed lol 18:51:39 The only risk I can see is that it's possible karsten was wrong and one of the anaconda fonts is missing. But I doubt that. 18:51:53 sgallagh: next time, you can save the explanation and just say the "magic line" 18:51:54 sgallagh invents a freeze process, then proposes all the freeze exceptions and we all vote how he tells us to 18:51:56 And it's easy to revert if that's what happens. 18:52:02 hahahaha 18:52:08 +10 bureaucracy! 18:52:12 Well, we *do* need a freeze process. 18:52:26 So I work with what I have, since no one else implemented a better one 18:52:29 sgallagh: how is that a 'risk', if this is only about a non-default profile? 18:52:41 i thought the fix here was just to take the affected fonts out of the 'everything' profile 18:52:46 is the everything profile used to construct the installer images? 18:53:09 adamw: Actually, right. This will have no impact on anaconda. 18:53:15 okay, then we're good. 18:53:17 Sorry, confused myself slightly 18:53:35 proposed #agreed 1509973 - AcceptedFreezeException (Server Beta) - sgallagh sez so 18:53:37 :P 18:53:41 okay fine 18:53:52 I'm working on almost no sleep and no days off for like two and a half weeks here. Cut me some slack, please :-/ 18:53:56 adamw: patch, grammar 18:54:16 proposed #agreed 1509973 - AcceptedFreezeException (Server Beta) - this will ensure an available profile for the fonts module can actually be installed without errors 18:54:32 ack 18:54:36 ack 18:54:39 ack 18:54:41 ack 18:54:45 #agreed 1509973 - AcceptedFreezeException (Server Beta) - this will ensure an available profile for the fonts module can actually be installed without errors 18:54:57 okay, that looks like everything 18:55:02 #topic Open floor 18:55:07 adamw: One more, possibly 18:55:09 any other business related to Final or Server releases? 18:55:17 We should discuss the one I was just mentioning in #fedora-qa 18:55:23 1510140 ? 18:55:24 See if it fits somewhere 18:55:33 yes 18:56:05 i can't really find a way to judo it into the criteria. i think probably FE is fine 18:56:11 i'd certainly be +1 FE for beta 18:56:29 As long as it's NOT a Beta Blocker, I can work with that. 18:56:35 I'm just certain I can't fix that this week 18:56:51 yeah, don't think it needs to block beta. 18:57:07 if you don't intend to fix it for beta, granting it a beta fe doesn't make much sense... 18:57:20 and it presumably doesn't need a final FE yet 18:57:51 Right, I just wanted to make sure the blocker crew agreed that it's not a Beta blocker 18:58:23 I do agree is not a Beta blocker 18:58:42 I'll do whatever I can to make sure it doesn't get to the point we need to decide on Final Blocker status :) 18:58:58 yeah, i'm okay with it not being a beta blocker. 18:59:10 so in that case, sounds like we don't need to topic it formally as there's nothing to vote on. 18:59:52 #info for the record, we informally considered #1510140 and agreed it'd definitely be best to fix it before final, but it doesn't obviously hit any criteria and no-one seemed worried that it should block beta 18:59:56 ack 19:00:19 ack 19:01:04 ack 19:01:07 nothing to ack, there 19:01:09 it wasn't proposed 19:01:10 :P 19:01:17 okay, so anything else, or can i go get some breakfast? 19:01:20 I was acking your statement of "nothing to vote on" 19:01:23 aha 19:01:24 heh 19:01:26 Sorry for confusion 19:01:50 I think I'm good. 19:02:04 I'm good too 19:02:08 Anyone who wants to put the Modular Server through its paces, please download and do so :) 19:02:23 * sgallagh is really trying to hit Go for Thursday 19:02:27 sgallagh, which is the best to look at? 19:02:50 2017_11_05.n.3 is the one I Froze 19:02:54 ok, thanks 19:03:39 i'll try to adjust openqa for differences in modular as best as i can 19:03:44 i'll need to talk to you about the repo setup 19:04:00 Sure 19:04:09 If I'm not around, tdawson also has that information 19:04:58 roger 19:05:01 thanks for coming, folks 19:05:03 * adamw sets fuse 19:05:32 thanks for chairing adamw 19:05:56 bye everyone, see you later 19:05:56 thanks 19:06:05 adamw, thanks for chairing :) 19:08:18 #endmeeting