16:05:49 #startmeeting F23-blocker-review 16:05:49 Meeting started Thu Aug 20 16:05:49 2015 UTC. The chair is adamw. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:05:49 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:05:49 #meetingname F23-blocker-review 16:05:49 #topic Roll Call 16:05:49 The meeting name has been set to 'f23-blocker-review' 16:05:57 sorry, can we state our names again for bot purposes? :P 16:06:09 #chair pwhalen sgallagh 16:06:09 Current chairs: adamw pwhalen sgallagh 16:06:23 our names again 16:06:30 * tflink dislikes having his IRC habits run by a bot, refuses to comply 16:07:44 * pschindl is here 16:08:09 tflink: you seem like a candidate for the skynet resistance 16:08:30 adamw: shush! the bot will hear you 16:08:38 #topic Introduction 16:08:38 Why are we here? 16:08:38 #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. 16:08:38 #info We'll be following the process outlined at: 16:08:40 #link https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting 16:08:40 #info The bugs up for review today are available at: 16:08:44 #link http://qa.fedoraproject.org/blockerbugs/current 16:08:44 #info The criteria for release blocking bugs can be found at: 16:08:46 #link https://fedoraproject.org/wiki/Fedora_23_Alpha_Release_Criteria 16:08:48 #link https://fedoraproject.org/wiki/Fedora_23_Beta_Release_Criteria 16:08:50 #link https://fedoraproject.org/wiki/Fedora_23_Final_Release_Criteria 16:08:52 tflink: no problem, i'll drown it in boilerplate 16:09:19 * tflink hears a clunk at his front door and a robotic voice demanding that I open it 16:09:29 adamw: see what you've done?! 16:09:46 tflink: that's just Columbia House. 16:10:01 is that even still a thing? 16:10:11 just shut down recently i think 16:10:14 For Beta, we have: 16:10:15 #info 6 Proposed Blockers 16:10:15 #info 6 Accepted Blockers 16:10:15 #info 4 Proposed Freeze Exceptions 16:10:17 #info 0 Accepted Freeze Exceptions 16:10:34 we also have 10 Proposed Blockers for Final, which we might get to later. 16:10:54 anyone willing to secretarialize? 16:12:09 bueller? 16:12:20 well, if no-one will i guess i'll do it after the meeting 16:12:37 here we go with Beta proposed blockers 16:12:38 #topic (1245423) TypeError: nothing connected to functools.partial(.TimedAction object 16:12:39 #link https://bugzilla.redhat.com/show_bug.cgi?id=1245423 16:12:39 #info Proposed Blocker, anaconda, MODIFIED 16:13:01 This looks like a pretty clear blocker. +1 16:13:13 this is the crasher where you try to delete a single partition in Reclaim Space, and yeah, looks fairly clear. 16:13:20 the fix does work. 16:14:01 +1 16:15:04 +1 16:16:37 +1 16:17:06 sorry, lemme find the agreed format we're using lately... 16:18:09 proposed #agreed 1245423 - AcceptedBlocker Beta - clear violation of "When using the guided partitioning flow, the installer must be able to: ... Remove existing storage volumes to free up space, at the user's direction" 16:18:29 ack 16:18:38 ack 16:18:46 ack 16:18:52 ack 16:19:42 #agreed 1245423 - AcceptedBlocker Beta - clear violation of "When using the guided partitioning flow, the installer must be able to: ... Remove existing storage volumes to free up space, at the user's direction" 16:19:50 #topic (1225957) Regression: GFileMonitor doesn't react to "mv some-file watched-file" 16:19:50 #link https://bugzilla.redhat.com/show_bug.cgi?id=1225957 16:19:50 #info Proposed Blocker, glib2, NEW 16:19:55 hum, this is a new one 16:20:55 I voted in the ticket, but it's a serious regression affecting a lot of Glib-based software, including Cockpit. 16:21:12 mclasen reported yesterday (or maybe this morning) that he has a fix ready upstream for it. 16:21:32 yeah, since it affects cockpit looks like a +1 blocker to me. 16:21:54 It probably affects a lot of other stuff, but we have a handy blocker criterion for Cockpit. 16:22:11 yea, +1 as well 16:22:19 +1 as in the ticket 16:22:31 +1 16:24:00 proposed #agreed 1225957 - AcceptedBlocker Beta - clear violation of "after system installation the Cockpit web management interface must be running and accessible on its default port (9090)" 16:24:18 ack 16:24:32 ack 16:24:32 ack 16:24:54 #agreed 1225957 - AcceptedBlocker Beta - clear violation of "after system installation the Cockpit web management interface must be running and accessible on its default port (9090)" 16:25:08 #topic (1249304) UnboundLocalError: local variable 'e' referenced before assignment 16:25:08 #link https://bugzilla.redhat.com/show_bug.cgi?id=1249304 16:25:08 #info Proposed Blocker, python-blivet, ON_QA 16:25:21 So, there's no explanation for why this is happening in the bZ 16:25:47 That said, it was reported fairly often from people installing Alpha from Live media. So it's probably hardware-specific. 16:25:57 i'm assuming it's some kind of exception handling corner case 16:25:57 (Since we didn't spot this during validation) 16:26:29 A fix is in updates-testing and people are already reporting that it worked 16:26:40 Without a clear idea of what triggers it, I'm not prepared to call it a blocker. 16:26:50 (And it may just sort itself out before Beta Freeze anyway) 16:27:52 Proposal: Defer a decision until someone identifies the specific reproduction steps or we enter Beta Freeze. 16:28:29 +1 defer 16:28:36 * adamw looks at the code a bit 16:29:44 meh, can't tell how serious it is easily 16:30:01 so, +1 defer, sure. fix should get in there. 16:30:13 pwhalen: pschindl ? 16:30:44 sure, +1 defer for now 16:30:47 +1 defer 16:32:25 proposed #agreed 1249304 - defer decision - it's unclear how serious or how commonly encountered this bug is, and a fix is already pending, so we'll hope to see it gone by next meeting 16:32:53 ack 16:33:21 ack 16:33:33 ack 16:34:14 #agreed 1249304 - defer decision - it's unclear how serious or how commonly encountered this bug is, and a fix is already pending, so we'll hope to see it gone by next meeting 16:34:21 #topic (1252052) blivet.errors.DeviceError: ('cannot replace active format', 'fedora_dhcp45-root') 16:34:21 #link https://bugzilla.redhat.com/show_bug.cgi?id=1252052 16:34:21 #info Proposed Blocker, python-blivet, MODIFIED 16:35:02 +1, seems to affect installs with pre-existing LVM layouts 16:35:12 (i hit this trying to reinstall my fedlet for e.g.) 16:35:19 +1 16:35:53 looks +1 to me 16:36:10 +1 16:36:11 +1 16:36:51 +1 16:37:58 proposed #agreed 1252052 - AcceptedBlocker Beta - clear violation of "When using the guided partitioning flow, the installer must be able to: ... Remove existing storage volumes to free up space, at the user's direction" 16:38:37 ack 16:38:43 ack 16:39:09 ack 16:39:22 #agreed 1252052 - AcceptedBlocker Beta - clear violation of "When using the guided partitioning flow, the installer must be able to: ... Remove existing storage volumes to free up space, at the user's direction" 16:39:31 #topic (1253787) AttributeError: 'int' object has no attribute 'convertTo' 16:39:31 #link https://bugzilla.redhat.com/show_bug.cgi?id=1253787 16:39:31 #info Proposed Blocker, python-blivet, MODIFIED 16:41:17 +1 from the criterion cited in the BZ 16:42:05 +1 16:42:16 +1 although it looks like it will be fixed probably in next compose 16:43:01 we hope! 16:43:09 garretraziel: The purpose of voting a blocker is so that if it turns out it's not fixed, we know that we can't ship until it is. 16:43:24 well, no, that's just for rawhide; we need to get updates pushed for anaconda 16:43:31 (there's a new anaconda/blivet update today, we should test it) 16:43:34 We didn't vote on the earlier one only because we had no idea what was causing it and how prevalent it was. 16:43:58 +1 16:43:59 proposed #agreed 1253787 - AcceptedBlocker Beta - clear violation of "When using the custom partitioning flow, the installer must be able to: ... Create mount points backed by ext4 partitions, LVM volumes or btrfs volumes, or software RAID arrays at RAID levels 0, 1 and 5 containing ext4 partitions." 16:44:16 ack 16:44:23 (iirc there's a footer in there or something which includes thinp)' 16:44:25 +1ack 16:44:43 * danofsatx thought he pushed enter after the +1 16:44:56 ack 16:44:57 #agreed 1253787 - AcceptedBlocker Beta - clear violation of "When using the custom partitioning flow, the installer must be able to: ... Create mount points backed by ext4 partitions, LVM volumes or btrfs volumes, or software RAID arrays at RAID levels 0, 1 and 5 containing ext4 partitions." 16:45:04 #topic (1250942) clicking on buttons on error pop-up doesn't work 16:45:05 #link https://bugzilla.redhat.com/show_bug.cgi?id=1250942 16:45:05 #info Proposed Blocker, python-meh, NEW 16:45:18 meh... 16:45:43 so, i've seen cases like this in previous releases, but it sounds like it may be worse here 16:45:47 it is a bit of a judgment call, though 16:45:55 /me smacks danofsatx 16:46:27 We should just fix all the bugs so we don't have to report them 16:46:42 or just not create any in the first place. 16:47:03 YAK FARM 16:47:26 * adamw sees if anaconda folks have an opinion 16:51:08 i guess i'm kinda on the fence on thios 16:51:22 it *is* pretty bad if people can't report crashes...but not sure it'd make it past a go/no-go meeting 16:51:37 bugs where the mechanism is completely broken are more clear cut 16:51:54 Yeah, this would be one of those "would we block on it if it was the only one left" sort of bugs 16:52:21 * roshi steps in late 16:52:29 -1 16:53:10 I'm a tentative -1/+1 on this 16:53:19 err -1 blocker/+1 FE 16:53:34 is anyone -1 beta / +1 final? 16:53:45 If it turns out to be happening very frequently during TC testing, I might revise it 16:53:53 * adamw provides swatches for the bikeshed 16:54:02 adamw: No, I don't think it makes sense at Final at all 16:54:21 Reporting bugs in anaconda is really only useful at Alpha or Beta, otherwise they won't be fixable for that release 16:54:40 (Yes, they'll be fixable in the next release, but that's not terribly helpful) 16:54:57 well, it helps *us*...and it does look bad if you can see a nice 'report a bug!' button but not click it. 16:55:11 true 16:55:23 (for values of 'help' that mean 'provide more work', i guess...) 16:55:29 you can still report it from console, can't you? 16:55:44 I'm -1 Beta Blocker, +1 FE and I could be convinced to discuss blocking Final after Beta 16:55:45 but you can still get logs. I'm more for FE. 16:56:08 I don't think it will touch lot of bugs 16:56:24 garretraziel: i never remember if report-cli is in the images or not. worst case you have to scp it out and run report-cli from somewhere else. 16:56:41 sounds like a -1/+1 consensus 16:56:42 (Where by "after beta" I mean "if we discover that it happens frequently") 16:57:10 That makes sense. 16:57:29 I'm for -1/+1 FE, because it will only affect bugs where modal dialog is shown and you can still get logs/report it from console 16:57:36 proposed #agreed 1250942 RejectedBlocker AcceptedFreezeException Beta - as things stand our call is that this is probably not quite common enough to block (it's a conditional criterion violation, so it's a judgment call). We may revise this later if it turns out to be more common than we thought 16:57:56 ack 16:58:09 ack 16:58:10 ack 16:59:08 ack 16:59:44 #agreed 1250942 RejectedBlocker AcceptedFreezeException Beta - as things stand our call is that this is probably not quite common enough to block (it's a conditional criterion violation, so it's a judgment call). We may revise this later if it turns out to be more common than we thought 16:59:59 OK, that's all the proposed beta blockers 17:00:08 making good time I see :) 17:00:19 beta freeze is 09-08 17:00:26 with that in mind, do we want to do final blockers or beta FE next? 17:00:33 or, you know, drink ourselves senseless? 17:00:39 ^^ that 17:01:06 we've got a bunch for Final, should probably look at them 17:01:10 -1 work/+1 senseless drinking 17:01:10 before the keep piling up 17:01:28 We're not in Freeze yet, so I'd focus on blockers 17:01:30 garretraziel: drink until senseless, then work 17:02:16 roshi: the breakfast of champions 17:02:28 drink until you don't feel the perl any more 17:02:44 alrighty, final blockers it is then 17:03:03 roshi: do you want to take over driving, or secretarializing? i've been doing both so far 17:03:18 which ever you prefer 17:03:58 * roshi can drive 17:04:03 alrighty, take the wheel 17:04:10 #chair roshi 17:04:10 Current chairs: adamw pwhalen roshi sgallagh 17:04:22 /me hangs on for dear life 17:04:24 looks like we've got 10 to go through 17:04:46 * roshi still wants to figure out why sgallagh can't "/me" properly 17:04:50 #topic (1252756) repository definition nor product branding works with nfsiso 17:04:53 #link https://bugzilla.redhat.com/show_bug.cgi?id=1252756 17:04:55 #info Proposed Blocker, anaconda, NEW 17:04:59 sgallagh: 'mind if I drive, Sam?' 'Not if you don't mind me clawing at the dash and screaming like a cheerleader, Max.' 17:05:31 adamw: One of my favorite games of all-time 17:05:37 yup 17:05:48 "there's nothing but strangers out there." 17:06:54 +1 on this, though it looks like one that's subject to go/no-go squeezing 17:07:03 "oh who uses nfsiso anyway" 17:07:08 +1 17:07:13 +1 17:07:25 I sense the squeezing coming for this as well 17:07:26 blocker_count++ 17:07:37 pschindl: it's BlockerCount 17:07:53 indented with 1 tab and 3 spaces 17:07:54 roshi: I'm sorry, I forgot :) 17:08:00 :p 17:08:27 after the 3 spaces is a unicode zero-width character 17:08:30 in case you were wondering 17:08:44 Yeah... I'd really be asking whether nfsiso is something people are really using 17:08:59 And whether it should be part of the criteria at all 17:09:15 proposed #agreed - 1252756 - AcceptedBlocker Final - This bug is a clear violation of the following Final criteria: "The installer must be able to use all supported local and remote package and installer sources." 17:09:23 sgallagh: of course I use it. Because test case makes me :( 17:09:24 (And I'd prefer to have that conversation ahead of time, rather than Go/No-Go) 17:09:29 roshi: I'm not convinced I'm +1... 17:09:38 sgallagh: i'm pretty sure it really is something real people use 17:09:39 #unchair sgallagh 17:09:39 Current chairs: adamw pwhalen roshi 17:09:43 :p 17:09:49 #chair sgallagh 17:09:49 Current chairs: adamw pwhalen roshi sgallagh 17:09:50 /me glares 17:09:51 ooooh, someone's playing hardball 17:10:06 ack 17:10:10 this is a bandwagon that you're on now whether you like it or not :p 17:10:21 votes are currently 4/1 17:10:40 sgallagh: want to send a missive to the list for discussion, and we can remove status if the criteria gets edited? 17:10:56 tbh, I wasn't sure if #unchair would do anything... 17:10:57 lol 17:11:18 Just a minute; I'm ruminating on this 17:11:45 * adamw wasn't aware you had that many stomachs 17:11:53 are we +1ing or acking? 17:11:58 +1 17:12:12 Alright, I think I'm with you on +1 17:12:12 * danofsatx is lost 17:12:27 chewing your cud in public is bad form 17:12:32 Even to the point of Go/No-Go discussion 17:13:05 to be fair adamw it could just be that his stomach has compartments - not distinct stomachs 17:13:16 #agreed - 1252756 - AcceptedBlocker Final - This bug is a clear violation of the following Final criteria: "The installer must be able to use all supported local and remote package and installer sources." 17:13:33 #topic (1252902) inst.repo=hd: is not working 17:13:34 #link https://bugzilla.redhat.com/show_bug.cgi?id=1252902 17:13:34 #info Proposed Blocker, anaconda, POST 17:14:02 roshi: My stomach at this point is growing *a*partements... I need to lose weight. 17:14:15 this is similar to the previous one, just hd instead of nfs 17:14:27 ok then, +1 17:14:54 same +1 17:15:06 +1 17:15:12 +1 17:15:15 +1 17:15:15 +1 17:15:28 proposed #agreed - 1252902 - AcceptedBlocker Final - This bug is a clear violation of the following Final criteria: "The installer must be able to use all supported local and remote package and installer sources." 17:15:41 ack 17:15:48 ack 17:15:54 ack 17:15:56 ack 17:15:58 proposed #agreed - 1252902 - AcceptedBlocker Final - This bug is a clear violation of the following Final criteria: "The installer must be able to use all supported local and remote package and installer sources." 17:16:03 #agreed - 1252902 - AcceptedBlocker Final - This bug is a clear violation of the following Final criteria: "The installer must be able to use all supported local and remote package and installer sources." 17:16:07 #topic (1254687) DNF does not display any translations 17:16:07 #info Proposed Blocker, dnf, POST 17:16:10 #link https://bugzilla.redhat.com/show_bug.cgi?id=1254687 17:16:32 so i did the l10n test day and found a bunch of bugs, who'd'athinkit 17:16:50 +1, seems obvious 17:16:54 +1 17:16:58 and it has a PR 17:16:58 (bonus: it's fixed) 17:17:01 which makes me happy 17:17:38 obviously +1 for me 17:18:23 proposed #agreed - 1254687 - AcceptedBlocker Final - This bug is a clear violation of the following Final criteria: "All critical path actions on release-blocking desktops must correctly display all sufficiently complete translations available for use." 17:18:35 ack 17:18:38 ack 17:19:11 ack 17:19:14 #agreed - 1254687 - AcceptedBlocker Final - This bug is a clear violation of the following Final criteria: "All critical path actions on release-blocking desktops must correctly display all sufficiently complete translations available for use." 17:19:18 #topic (1250414) media check fails on DVD/netinst - "configured resource limit was exceeded" 17:19:21 #link https://bugzilla.redhat.com/show_bug.cgi?id=1250414 17:19:23 #info Proposed Blocker, dracut, ON_QA 17:20:27 +1 and it's got a fix 17:20:40 +1 per cited criterion 17:21:22 +1 17:21:33 +1 17:21:34 +10 17:21:39 erm, -9 17:21:42 proposed #agreed - 1250414 - AcceptedBlocker Final - This is a clear violation of the following Final criterion: "Validation of install media must work correctly for all release-blocking images." 17:21:50 ack 17:21:58 ack 17:21:59 well, now we know someone uses their 10key 17:22:42 ack 17:22:53 well, it was better than +any 17:22:57 #agreed - 1250414 - AcceptedBlocker Final - This is a clear violation of the following Final criterion: "Validation of install media must work correctly for all release-blocking images." 17:23:10 #topic (1236034) many fonts missing in fontconfig cache after installation, forced refresh needed 17:23:13 #link https://bugzilla.redhat.com/show_bug.cgi?id=1236034 17:23:15 #info Proposed Blocker, fontconfig, VERIFIED 17:23:24 you can skip verified 17:24:04 that never happens so I didn't notice 17:24:06 #topic (1249336) [abrt] setroubleshoot-server: util.py:291::ImportError: No module named sepolicy 17:24:10 #link https://bugzilla.redhat.com/show_bug.cgi?id=1249336 17:24:12 #info Proposed Blocker, setroubleshoot, MODIFIED 17:24:27 well, it's not entirely safe because the update might not get karma. but this far out it should be OK 17:24:41 we usually skip VERIFIED during review of *existing* blockers, not *new proposed* ones. 17:24:51 adamw: you're right, as always. spoke too soon 17:25:02 maybe because I'm not officially here 17:25:10 * kparal is a ghost, wheeee 17:25:28 roshi: can we go back to the fontconfig one just in case? 17:25:33 /me gets out the proton pack 17:25:36 sure 17:25:40 * roshi does the same 17:25:46 sgallagh: on three! 17:25:59 #topic (1236034) many fonts missing in fontconfig cache after installation, forced refresh needed 17:26:02 #link https://bugzilla.redhat.com/show_bug.cgi?id=1236034 17:26:04 #info Proposed Blocker, fontconfig, VERIFIED 17:26:11 in that case +1 17:26:11 +1 17:26:21 +1 17:26:31 +1 17:26:32 +1 17:26:51 +1 17:28:02 proposed #agreed - 1236034 - AcceptedBlocker Final - This is a clear violation of the following Final criterion: "All applications that can be launched using the standard graphical mechanism of a release-blocking desktop after a default installation of that desktop must start successfully and withstand a basic functionality test." 17:28:14 ack 17:28:26 ack 17:28:58 ack 17:29:00 ack 17:29:01 ack 17:29:02 #agreed - 1236034 - AcceptedBlocker Final - This is a clear violation of the following Final criterion: "All applications that can be launched using the standard graphical mechanism of a release-blocking desktop after a default installation of that desktop must start successfully and withstand a basic functionality test." 17:29:09 #topic (1249336) [abrt] setroubleshoot-server: util.py:291::ImportError: No module named sepolicy 17:29:12 #link https://bugzilla.redhat.com/show_bug.cgi?id=1249336 17:29:15 #info Proposed Blocker, setroubleshoot, MODIFIED 17:29:15 +1 17:29:27 +1 too 17:30:11 in case it's not obvious, this is the 'selinux troubleshooting' gui for selinux alerts 17:30:20 on a clean default workstation live install it doesn't run 17:30:34 +1 17:30:36 fun 17:30:38 +1 17:31:05 This feels like it should have a dedicated criterion as well 17:31:05 proposed #agreed - 1249336 - AcceptedBlocker Final - This bug is a clear violation of the following Final criterion: "All applications that can be launched using the standard graphical mechanism of a release-blocking desktop after a default installation of that desktop must start successfully and withstand a basic functionality test." 17:31:19 Does the non-graphical reporter work? 17:31:44 dunno, but the criterion is more of a 'you shouldn't get any crashes launching apps through the menus' one 17:31:51 it's not primarily about whether reporting selinux avc's works 17:32:11 I know, but I feel like that should *also* be a criterion 17:32:20 it may be 17:32:24 i just didn't think of that angle 17:32:36 dunno if the cli reporter is present/working out of the box, sorry. 17:33:02 still, fixing this one is easy enough. 17:33:13 (the py3 port isn't, but if that doesn't shake out, we can just add the dep.) 17:33:13 ack/nack/patch? 17:33:18 ack 17:33:26 ack 17:33:41 ack 17:33:42 #agreed - 1249336 - AcceptedBlocker Final - This bug is a clear violation of the following Final criterion: "All applications that can be launched using the standard graphical mechanism of a release-blocking desktop after a default installation of that desktop must start successfully and withstand a basic functionality test." 17:33:52 #topic (1240802) Can't unlock an encrypted root partition using caps lock key 17:33:55 #link https://bugzilla.redhat.com/show_bug.cgi?id=1240802 17:33:57 #info Proposed Blocker, systemd, NEW 17:34:24 this one still 17:34:27 this one is fun 17:34:29 i keep meaning to look at it and never get to it 17:34:36 Can we file this under "Why would you do that??" 17:36:22 * adamw doesn't understand how the behaviour from #c7 is 'strange' 17:36:28 isn't that exactly how caps lock is supposed to work? 17:37:00 adamw: I think it's the brokenness of libvirt 17:37:07 #c8 sounds bad, but yeah, i'm inclined to file under 'weird shit, do it differently' 17:37:14 later he said that caps lock on produced a mix in tty3 17:37:40 adamw: It looks like this is all in libvirt. 17:37:42 so i'm basically -1 on this, if you have weirdness with caps lock, turn it off. 17:37:45 sgallagh: #c8 17:37:49 is bare metal. 17:37:50 I've seen this too, not just at password prompts 17:38:03 where libvirt will sometimes toggle the caps-lock at random 17:38:14 virt-manager / libvirt do have weirdness though, yeah. i often wind up with alt stuck down. 17:38:17 it's most painful at password 17:38:29 theory: it's not random, the ghost in the machine is trying to communicate and we're just not listening 17:38:41 it's typing out one character at a time with capslocks... 17:38:51 I suspect #c8 is a different bug from the rest of this 17:39:15 roshi: I highly doubt Kusanagi would be that obtuse 17:39:26 I lean more -1 on a practical level of what would happen if this is the last blocker at go/no-go 17:39:46 I'm with roshi here. -1 17:39:55 -1 17:40:01 sgallagh: the kernel is a harnessing mechanism - it controls the magic smoke inside the chips - it can only communicate at LUKS password prompts 17:40:23 That's just like... your opinion, man 17:40:58 proposed #agreed - 1240802 - RejectedBlocker Final - While this bug is very odd and annoying, the workaround is easy and doesn't seem to happen enough to warrant blocking the release for it. 17:41:02 sgallagh: heh 17:41:11 ack 17:41:16 ack 17:41:42 ack 17:41:45 #agreed - 1240802 - RejectedBlocker Final - While this bug is very odd and annoying, the workaround is easy and doesn't seem to happen enough to warrant blocking the release for it. 17:41:57 #topic (1250737) systemd-tmpfiles-setup.service fails on 23 Alpha RC1 Server 17:42:00 #link https://bugzilla.redhat.com/show_bug.cgi?id=1250737 17:42:03 #info Proposed Blocker, systemd, POST 17:42:41 +1, pretty clear 17:43:57 +1 to the blocker, but I'm not certain that the solution as presented is necessarily correct. 17:44:05 +1 17:44:24 "A bunch of stuff we want tmpfiles to do didn't happen. We'll call it a warning instead of a failure" 17:44:33 yeah 17:44:52 * pschindl has to leave. ack to whatever roshi writes to propose :) 17:45:41 i wasn't entirely clear on whether he meant 'we just let it fail and call it a warning' or 'by downgrading some error we allow the rest of the tmpfiles stuff to complete' 17:45:43 :) 17:45:49 i can ask him to clarify in the comment 17:45:55 that'd be good 17:46:06 still accept as a blocker though, or punt? 17:46:12 it's a blocker either way. 17:46:15 we all seem to agree on blockeriness 17:46:17 the only question is whether the fix is appropriate. 17:46:32 adamw: I'm reading through the systemd upstream bug 17:46:39 It's... ugly 17:47:01 * adamw tries to avoid systemd upstream bugs because he likes to cherish his illusions 17:47:20 they still haven't fixed the 'oh hey, we'll just kill -9 everything on shutdown, that's fine right?' 17:47:22 bug. 17:47:28 proposed #agreed - 1250737 - AcceptedBlocker Final - This is a clear violation of the following Final criterion: "All system services present after installation with one of the release-blocking package sets must start properly, unless they require hardware which is not present." We would prefer a actual fix to merely relabeling this error as a warning. 17:47:44 s/a/an/ in final sentence 17:48:27 ack 17:48:35 ack 17:48:51 ack 17:48:52 #agreed - 1250737 - AcceptedBlocker Final - This is a clear violation of the following Final criterion: "All system services present after installation with one of the release-blocking package sets must start properly, unless they require hardware which is not present." We would prefer an actual fix to merely relabeling this error as a warning. 17:49:05 #topic (1254658) systemctl seems not to be translated at all 17:49:05 #link https://bugzilla.redhat.com/show_bug.cgi?id=1254658 17:49:05 #info Proposed Blocker, systemd, NEW 17:49:18 The short version of the upstream bug is that Lennart considers XFS to be an "exotic" filesystem and should follow ext[234]'s lead in how to handle that ioctl 17:49:41 that's who I read it too sgallagh 17:49:42 How *the default FS in Fedora Server and RHEL* is considered "exotic" is outside my ability to process. 17:50:30 is this something we've released with in the past? 17:51:12 I can see an argument that it's already been shipped like this, sans translations - but I think it's a clear blocker 17:52:02 i *think* i ran the 'service' checks for 22 final. 17:52:16 -1 blocker 17:52:33 The blocker criterion requires us to ship translations if they exist, but none do 17:52:53 oh, good point 17:52:56 yeah, fair enough. 17:52:57 -1 17:53:02 * adamw should read his own criteria sometimes. 17:53:43 proposed #agred - 1254658 - RejectedBlocker Final - While it would be great to have translations for this, none currently exist upstream so this doesn't actually violate the criterion. 17:53:49 ack 17:54:12 patch: agreed, not agred. 17:54:59 I guess I'll accept your revision :p 17:55:05 * roshi can typ 17:56:00 I think somthing is wrong with a crtain ky, but I can't b sur. 17:56:03 i always remember the guy from my university irc channel who came in extremely drunk one day 17:56:12 proposed #agreed - 1254658 - RejectedBlocker Final - While it would be great to have translations for this, none currently exist upstream so this doesn't actually violate the criterion. 17:56:15 i think it went something like 'i aturrrrgling tp typr' 17:56:31 ack 17:56:33 ack 17:56:35 hh awsom 17:56:44 #agreed - 1254658 - RejectedBlocker Final - While it would be great to have translations for this, none currently exist upstream so this doesn't actually violate the criterion. 17:56:56 #topic (1199252) default html mime configuration 17:56:56 #link https://bugzilla.redhat.com/show_bug.cgi?id=1199252 17:56:56 #info Proposed Blocker, xfce4-session, ASSIGNED 17:59:09 I don't see any criterion this violates 17:59:23 basic usage 17:59:30 Not a blocking desktop 18:00:36 yeah, I was looking through to see about other DE's 18:00:39 but doesn't look like it 18:00:42 -1 18:02:13 -1 18:02:29 -1 then 18:03:00 +1 FE, but we're a long way from that. 18:03:05 proposed #agreed - 1199252 - RejectedBlocker Final - This bug doesn't seem to affect any release blocking desktops and so is not considered a blocker for Final. 18:03:32 ack 18:03:37 oh wait! 18:03:38 proposed #agreed - 1199252 - RejectedBlocker Final - This bug doesn't seem to affect any release blocking desktops and so is not considered a blocker for Final. Please propose as an FE if needed during freeze. 18:03:40 that's wrong, isn't it? 18:03:42 nack 18:03:44 Xfce is blocking now 18:03:46 * nirik doesn't know why he proposed it even but whatever. 18:03:53 which seemed like a great idea at Alpha 18:03:57 so, +1. 18:03:58 oof 18:04:00 blocker for arm, at least, that's right 18:04:02 for arm? right 18:04:04 You're right 18:04:12 /me shakes fist at his past self 18:04:14 not for workstation though? 18:04:22 roshi: ? 18:04:34 it's all kinda moot, I am going to push the fix out to f23 today. 18:04:37 roshi: we don't have per-arch blockers at present. it's a blocker or it ain't. 18:04:44 if it worked on arm and didn't work on workstation - we'd ship 18:04:46 right? 18:05:05 roshi: wait, how are you comparing arm and workstation? 18:05:18 one of them is an arch. one of them is a flavor. 18:05:20 * adamw raises a TypeError 18:05:21 Using the Chewbacca defense? 18:05:46 roshi: if this bug is present on the ARM Xfce image, which by all indications it would be, it's a blocker. 18:05:56 right 18:06:01 but if it wasn't on the arm image 18:06:04 would we block? 18:06:18 no. if you're asking would we block for an Xfce bug which didn't affect ARM, we would not. 18:06:30 if the arm images worked flawlessly, and everything else catches fire and kills puppies, do we still ship? 18:06:30 whats the criteria? advanced menus? 18:06:52 ok, so we really need to see if this is on arm before we can say if it's a blocker then 18:07:01 it's basically a noarch bug, isn't it? 18:07:11 i'm willing to go ahead and assume it affects arm, personally. 18:07:21 (especially since nirik says he's fixing it today so let's move on already.) 18:07:39 I am too, just wanted to suss out that eventuality in case we come across it in the future 18:07:49 +1 then 18:08:01 do we need to update criteria or test matrices with the new arm DE? 18:08:06 i already did it. 18:08:07 * roshi didn't see if we did that already 18:08:11 sweet 18:09:15 proposed #agreed - 1199252 - AcceptedBlocker Final - As Xfce is the desktop environment for arm this violates the following Final criterion: "Each application in the default system menu layout should launch without crashing and withstand basic usage. Bugs should be filed in any case where this does not happen" 18:09:23 ack 18:09:37 ack 18:09:38 ack 18:09:47 #agreed - 1199252 - AcceptedBlocker Final - As Xfce is the desktop environment for arm this violates the following Final criterion: "Each application in the default system menu layout should launch without crashing and withstand basic usage. Bugs should be filed in any case where this does not happen" 18:09:57 that's it for blockers 18:10:04 call it for now or go through FE's? 18:10:07 Assuming no more came in while we were processing. 18:10:19 We're not in Freeze yet; any good reason to bother? 18:10:21 since this is an out of band review, I'm for calling it now and doing them on monday 18:11:07 WFM 18:11:13 #topic Open Floor 18:11:14 me too 18:11:17 anybody have anything? 18:11:17 nice work folks, that was quick 18:11:21 * roshi sets the fuse 18:11:28 it'd be good if people could test+karma latest anaconda/blivet 18:11:33 thanks for handling the beginning and secretarializing adamw 18:11:39 the one we have in f23 stable atm is a bit crusty 18:11:49 i'm gonna try it with a live image and also spin up a boot.iso and throw it at colada 18:12:28 sounds good 18:13:34 thanks for coming! 18:13:38 3... 18:13:40 2... 18:13:42 1... 18:13:47 #endmeeting