20:11:15 #startmeeting F23-blocker-review 20:11:15 Meeting started Thu Oct 15 20:11:15 2015 UTC. The chair is roshi. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:11:15 Useful Commands: #action #agreed #halp #info #idea #link #topic. 20:11:15 #meetingname F23-blocker-review 20:11:15 The meeting name has been set to 'f23-blocker-review' 20:11:15 #topic Roll Call 20:12:00 heh, adamw beat me to the fedora-devel channel 20:12:08 * satellit listening 20:12:11 who's around for some aync blocker goodness? 20:12:13 * nirik is lurking around 20:12:23 #chair nirik satellit jpigface adamw 20:12:23 Current chairs: adamw jpigface nirik roshi satellit 20:12:39 #topic Introduction 20:12:39 Why are we here? 20:12:40 #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. 20:12:41 this is sync 20:12:43 it's so sync it hurts 20:12:43 #info We'll be following the process outlined at: 20:12:46 #link https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting 20:12:46 * jpigface is still performing tests, but is listening 20:12:48 #info The bugs up for review today are available at: 20:12:51 #link http://qa.fedoraproject.org/blockerbugs/current 20:12:53 #info The criteria for release blocking bugs can be found at: 20:12:56 #link https://fedoraproject.org/wiki/Fedora_23_Alpha_Release_Criteria 20:12:59 #link https://fedoraproject.org/wiki/Fedora_23_Beta_Release_Criteria 20:13:02 #link https://fedoraproject.org/wiki/Fedora_23_Final_Release_Criteria 20:13:05 lol 20:13:07 4 proposed 20:13:13 first up: 20:13:14 #topic (1261569) old kernel boots by default after upgrade 20:13:14 #link https://bugzilla.redhat.com/show_bug.cgi?id=1261569 20:13:14 #info Proposed Blocker, anaconda, POST 20:13:37 so i've got a fix for this, i'm pretty sure it works, though it'd be good if others would confirm. 20:13:58 as cmurf said, istr we accepted a bug like this in the past 20:14:00 uh... anaconda ? upgrades? 20:14:05 * nirik reads the bug 20:14:18 nirik: anaconda writes a wrong value to /etc/sysconfig/kernel , which causes problems when kernel updates happen 20:15:20 ok, makes sense. 20:15:28 yeah, I recall a bug like this being blocker 20:15:45 the new kernel entry isn't saved to grubenv , which sometimes stops it being the default boot choice. sometimes, somehow, it still does become the default boot option, but it's definitely wrong and causes problems at least sometimes. for me it seems like UEFI installs wind up booting the old kernel, BIOS installs wind up booting the new kernel, we're theorizing that sometimes grubenv isn't read properly for some reason, and when grubenv isn't re 20:15:46 ad properly the top entry in the list will be default so the bug is hidden... 20:15:48 +1 whatever, we should pull it in. Blocker I guess. 20:15:57 iirc the criterion we used before was the update criterion 20:16:06 the argument being that updates aren't applied 'properly' if new kernels don't become the default 20:16:18 a classic piece of criterion ninjutsu indeed 20:16:35 it makes sense to me 20:16:36 +1, makes sense to fix this 20:16:37 +1 20:16:42 #chair kalev 20:16:42 Current chairs: adamw jpigface kalev nirik roshi satellit 20:16:43 note that we have an anaconda build today with all *other* blockers fixed, so this would be the sole (current known) reason to do another anaconda build' 20:16:55 but i think it's bad enough to be worth that, especially since we still have *other* outstanding blockers 20:17:03 * roshi is fine with that 20:18:42 proposed #agreed - 1261569 - AcceptedBlocker Final - This bug is a violation of the following Beta criterion: "The installed system must be able to download and install updates with the default graphical package manager in all release-blocking desktops." While the latest kernel is *installed*, it's not set up to be the default as it should be - which potentially leaves users without the latest 20:18:48 security patches in the kernel. 20:18:55 proposed #agreed - 1261569 - AcceptedBlocker Final - This bug is a violation of the following Beta criterion: "The installed system must be able to download and install updates with the default graphical package manager in all release-blocking desktops." While the latest kernel is *installed*, it's not set up to be the default as it should be - which potentially leaves users exposed. 20:19:01 there, and it's small enough 20:19:16 -ETOOLONGFORIRC 20:19:16 ack 20:19:20 ack 20:19:22 ack 20:19:25 ack 20:19:26 ack 20:19:27 #agreed - 1261569 - AcceptedBlocker Final - This bug is a violation of the following Beta criterion: "The installed system must be able to download and install updates with the default graphical package manager in all release-blocking desktops." While the latest kernel is *installed*, it's not set up to be the default as it should be - which potentially leaves users exposed. 20:19:40 adamw: are you going to secretarialize? 20:20:29 sure 20:21:01 thanks :) 20:21:02 #topic (1269581) GNOME autologin makes boot and shutdown last 90 seconds more 20:21:05 #link https://bugzilla.redhat.com/show_bug.cgi?id=1269581 20:21:08 #info Proposed Blocker, gnome-keyring, ASSIGNED 20:21:26 halfline has a proposed fix for this hot off the press: http://koji.fedoraproject.org/koji/taskinfo?taskID=11464853 20:21:51 i'm kinda on the fence about blocker status - on the one hand it's not really that terrible in effect, forcibly shutting down a live boot is fine, on the other hand it'd affect everyone who ever booted an f23 live forever 20:21:56 which is a bad look 20:22:44 true 20:22:50 I'm +1 FE for sure 20:22:58 not 100% sold on blocker 20:23:01 I think it's already marked as FE 20:23:04 about +.75 20:23:11 but a forced shutdown is not fine (even in live), IMHO :) 20:23:17 yeah, it is 20:23:34 marked an FE, I mean 20:24:11 yeah, if i'm forced to pick i guess i'd go +1 20:24:25 +1 blocker? or fe? 20:24:25 lot of non-technical reviews base their vote on things like boot times etc. 20:24:32 blocker 20:24:40 that's a fair point jpigface 20:24:42 yeah, reviewers would likely kill us for it 20:24:49 'they couldn't even fix THIS?' 20:24:50 yeah, I can be +1 blocker I guess. 20:24:50 * satellit not as important since persistence lo longerer works in USB's? 20:24:53 * roshi looks for the criteria 20:26:09 so, looks like we've got 2.75+ blocker? 20:26:11 I think I'd lean towards marking it as a blocker as well 20:26:22 halfline: what's your take? 20:26:30 a fix would be nice 20:26:32 roshi: unfortunately the existing criteria are specifically tied to post-install 20:26:41 * roshi would personally just tell people to not use autologin 20:26:46 "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." 20:26:53 roshi: autologin is used on the live images, you can't change it 20:27:07 oh yeah 20:27:18 so the blocker part of this bug is really 'shutting down the live image takes forever' 20:27:25 (aiui) 20:27:27 but kparal was talking about the popularity of the feature outside of that 20:27:33 yeah, that's what I grokd as well 20:27:37 true, i guess, but post-release can fix with an update 20:27:48 to do this right i'd say we should approve in principle that we extend the shutdown requirement to installer images 20:27:56 adamw: don't have a strong opinion 20:28:14 we've had issues with installer images not shutting down/rebooting after install that apparently causes pain for remote deployment too iirc 20:28:27 adamw: (but hope the fix works so the discussion is moot!) 20:28:36 * satellit seen that 20:28:41 halfline: heh, yeah 20:29:12 I'm still +1 blocker, because new users (and reviewers, as noted above) often base their decisions to lives' performances. 20:29:27 proposed #agreed - 1269581 - The practical impact of this bug is a violation of the following Beta criterion when using a live image: "Shutting down, logging out and rebooting must work using standard console commands and the mechanisms offered (if any) by all release-blocking desktops" 20:29:47 er 20:29:58 proposed #agreed - 1269581 - AcceptedBlocker Final - The practical impact of this bug is a violation of the following Beta criterion when using a live image: "Shutting down, logging out and rebooting must work using standard console commands and the mechanisms offered (if any) by all release-blocking desktops" 20:30:31 ack, I think it makes sense to extend this criteria to live media 20:31:21 as do I 20:31:39 kalev: +1. We're not talking about an exotic package which is crashing, we're talking about basic functionalities (IMHO) 20:31:40 sur 20:31:41 sure 20:31:58 +1 20:32:01 #agreed - 1269581 - AcceptedBlocker Final - The practical impact of this bug is a violation of the following Beta criterion when using a live image: "Shutting down, logging out and rebooting must work using standard console commands and the mechanisms offered (if any) by all release-blocking desktops" 20:32:08 #topic (1264012) liveusb-creator doesn't create bootable Live i686 image in default cp mode 20:32:11 #link https://bugzilla.redhat.com/show_bug.cgi?id=1264012 20:32:13 #info Proposed Blocker, liveusb-creator, NEW 20:32:28 see my comment at end 20:33:00 i was trying this just now to confirm it's the same syslinux problem as litd, but i'm not sure yet 20:33:14 my first try seemed to fail with 'Missing operating system' which usually means the partition isn't marked bootable... 20:33:21 results are te same from f23 20:33:37 the* 20:34:07 so, syslinux is still busted, news at 11? 20:34:33 (btw, I remember this one too: https://bugzilla.redhat.com/show_bug.cgi?id=1250712) 20:34:34 also with nuei liveusb-creater (copr) 20:34:47 seems so nirik 20:35:33 well, is there any chance we can get it fixed at this point? it's been broken for a long while now... ;( 20:36:01 disks-restore works fine as fallback 20:36:26 has anyone who understands syslinux even looked at it? 20:36:28 assuming this *is* the same syslinux bug, we're kinda at the mercy of upstream and possibly pjones 20:36:40 last i checked with pjones he said he was aware of it, hadn't looked at it 20:36:44 still 0 commits this year on upstream. ;) 20:36:50 i did email h. peter anvin to see if he can help but did not receive a reply yet 20:37:06 how did it regress, due to a gcc update or something I bet? 20:37:07 nirik: eh? http://repo.or.cz/w/syslinux.git/ 20:37:11 kalev: GCC, yeah 20:37:16 it's almost certainly GCC 5 20:37:28 oh, thats not the repo listed on the main site... 20:37:29 but ok 20:37:41 if that's the case, we could probably do a ugly ugly hacky workaround by building it in a f22 chroot and submitting it as a f23 update 20:38:00 heh 20:38:14 ooh, that sounds horrible. 20:38:16 * nirik shudders 20:38:16 let's do it! 20:38:19 :P 20:38:41 I suppose we could try git head... seems a lot of commits on that repo 20:38:51 already done it 20:38:53 doesn't help 20:39:16 nirik: see my comments on the other bug - https://bugzilla.redhat.com/show_bug.cgi?id=1263988#c11 20:39:47 ok. I wasn't aware that you had done another git head test. 20:40:20 ooo 20:40:23 * adamw checks upstream mailing list 20:40:23 http://www.syslinux.org/archives/2015-October/024358.html 20:40:45 http://www.syslinux.org/archives/2015-September/024318.html 20:40:48 ohhhh, that looks like our issue 20:40:52 http://www.syslinux.org/archives/2015-September/024319.html 20:41:01 * adamw will test a syslinux with those patches 20:41:10 seems possible 20:41:20 proposal: punt for more testing? or ? 20:41:37 it's getting a bit late to be punting, but otoh, these *would* be 'special blockers' - they don't need to hold up compose 20:41:45 they'd be 'must be in 0-day updates' cases, i guess 20:42:08 yeah 20:42:11 votes? 20:42:21 guess i'm ok with punting to monday 20:42:33 wfm 20:43:09 +1. that's reasonable. 20:43:14 yeah, I don't think it needs to be in todays TC, so fine to punt :) 20:43:27 or any TC or RC 20:43:27 proposed #agreed - 1264012 - Punt Final - There are some patches we'd like to take a look at before voting on this. Punting until the Blocker Review meeting on Monday (2015-10-19) 20:43:32 +1 20:43:37 ack 20:43:41 ack 20:43:43 ack 20:43:43 ack 20:43:51 #agreed - 1264012 - Punt Final - There are some patches we'd like to take a look at before voting on this. Punting until the Blocker Review meeting on Monday (2015-10-19) 20:43:55 #topic (1263988) livecd-iso-to-disk doesn't create bootable usb drive 20:43:58 #link https://bugzilla.redhat.com/show_bug.cgi?id=1263988 20:44:01 #info Proposed Blocker, syslinux, NEW 20:44:03 last one 20:44:35 proposed, I mean 20:44:54 same as the last one 20:44:56 same thing as in previous, I think? 20:44:57 yup 20:45:08 * satellit same problem? 20:45:15 we're assuming it is 20:45:25 * nirik nods. 20:45:31 i'll build the new syslinux and see if it fixes litd, if it does, i can post it in this bug and folks can see if it solves this one too 20:45:39 (since i never seem to have much luck with luc at all) 20:45:39 sounds good 20:45:51 yeah 20:45:57 punt again? 20:46:03 * kalev nods. 20:46:06 +1 20:46:15 proposed #agreed - 1263988 - Punt Final - There are some patches we'd like to take a look at before voting on this. Punting until the Blocker Review meeting on Monday (2015-10-19) 20:47:06 ack 20:47:27 ack 20:47:30 ack 20:47:32 ack 20:47:34 ack 20:48:04 #agreed - 1263988 - Punt Final - There are some patches we'd like to take a look at before voting on this. Punting until the Blocker Review meeting on Monday (2015-10-19) 20:48:53 before we go on to FE's, can I bring up the gnome 3.18.1 update? 20:49:01 go through FE's or accepted blockers? 20:49:04 sure kalev 20:49:17 * nirik has a silly bug to mention at the end as well (or whenever) 20:49:31 right, so it's the case again, as somehow always happens, that gnome releases a bug fix update two days after fedora goes into the freeze ... 20:50:08 and we're in a bad situation where we should either do a massive 0 day update or do a freeze exception for this 20:50:31 IMHO if we are going to do a freeze exception we should do it sooner rather than later. 20:50:34 so two bad choices, and I guess we get to choose the less bad 20:50:36 yup 20:51:05 I would personally lean towards a freeze exception, but if we do that, I'd love to see a TC with it this week to make sure it gets proper testing 20:51:15 I'd definitely not want to pull this in late next week or something crazy like that 20:51:23 yeah 20:51:28 sooner rather than later for sure 20:51:28 right 20:51:36 the status with builds is that the last upstream release I was waiting for, gnome-shell-extensions, was just released 5 minutes ago 20:51:37 kalev: is there an update for it? 20:51:39 and is building for fedora 20:51:40 ah, ic 20:51:48 i'm pencilling in a TC for today 20:51:50 so there should be an update in bodhi in 30 minutes or so 20:52:19 i'm more or less OK with an FE, though it *is* a bit later than we've previously done it, and we do have fairly complete validation for GNOME in current TCs which would be a shame to lose 20:52:20 * nirik was planning to sign and push to updates-testing after it's submitted. 20:52:51 so far we've had a good track record with these GNOME FEs but sod's law says one of 'em is going to bite us in the ass sooner or later 20:53:18 proposal: do a tc today without, do another tc tomorrow with... 20:53:21 I'll be alert these days and ready to jump on any regressions that shows up 20:53:38 nirik: sounds like a plan 20:53:46 sure, sounds good to me 20:53:52 * adamw throws another jpigface into the test furnace 20:54:07 then we can check the one tomorrow and if it looks ok pull into stable/rc 20:54:14 ok ok, i promise i'll do the tests for at least *one* of the TCs. :P 20:54:26 nirik: sounds like a good plan to me 20:54:38 and we wouldn't want releng to have a day without a tc. ;) 20:54:57 I'll go file a FE for this 20:54:57 you'd get bored 20:55:09 rgr 20:55:28 adamw: you know, I'm always around for release validation testing 20:55:41 jpigface: see, we're making sure you have lots of it, aren't we kind :) 20:55:55 :D 20:56:30 jpigface doesn't know that asking for more is likely to get more than was originally thought 20:56:36 :P 20:57:42 ahah :D 20:57:44 so, on to FE's ? or do people want to see the amusing bug I was going to mention? 20:57:56 * adamw is always up for amusement 20:58:05 I'm all for an amusing bug before FEs 20:58:07 https://bugzilla.redhat.com/show_bug.cgi?id=1271445 20:58:08 amusement first, of course! 20:58:24 I have no way to test this. I actually don't have any machines with cdrom drives here that are on. ;) 20:59:10 but if this happens in f23... it could be a problem... removing the media while you are using it. 20:59:30 yeah... 20:59:37 not sure we have a criteria for this though... 20:59:51 or even what is responsible here? 21:00:10 -1 blocker, since if you yank the USB out while using it you run into the same issue 21:00:13 :p 21:00:44 true indeed. 21:00:51 heh, fun. 21:01:18 tbh, I didn't know the drive got locked before 21:01:26 tested in f23? 21:01:39 I just thought, "Hey, I'm using that - probably shouldn't press that button." 21:01:52 I am pretty sure it was in the past, but like I said, I haven't used cd/dvd's in ages... 21:02:12 when I still had spare DVDs, I would burn them for testing 21:02:19 ran out of them last release though...\ 21:02:36 I think long ago there used to be a --memory option to livecd boots to load everything into memory so you could eject the media. 21:02:54 ie, boot a bunch of machines with the same cd... but I think that got dropped 21:03:50 I'm not sure about this one... it's like cutting the ethernet cable while downloading... 21:04:18 or throwing your main on your fuse box 21:04:19 well, just thought I would mention it. If folks want to test it on f23 and add comment, feel free. 21:04:40 not to mention, if drive firmware doesn't support it anymore - we might not even be *able* to fix it 21:04:41 * satellit I have a 8.1 MacbookPro here with disk eject button should test... 21:04:51 I'd take an FE for it though I guess 21:05:23 * adamw would need more details 21:05:31 don't even know what's supposed to be implementing locking at what level 21:05:35 yeah, I'd still want it tested 21:05:40 k 21:06:03 votes? 21:06:06 right, its all a bit unknown at this point. 21:06:21 the orig reporter was on 22 it seems like 21:06:42 so I am 0 for anything now, but if people could test we could propose later or not. 21:06:59 I certainly am -1 for blocking. FE could be reasonable, but I'm not sure. 21:07:26 it's not what we call a normal usage... 21:07:57 well, we'll wait for more info and move onto FEs 21:08:04 that work? 21:08:16 roshi: +1 21:08:18 sure 21:08:25 got 7 proposed FEs 21:08:32 #topic (1091300) Anaconda Support for Server Roles 21:08:32 #link https://bugzilla.redhat.com/show_bug.cgi?id=1091300 21:08:32 #info Proposed Freeze Exceptions, Changes Tracking, ON_QA 21:08:33 +1 21:09:06 given the actual scope of the FE request, +1 21:09:47 * roshi voted in bug 21:09:48 +1 21:09:50 +1 21:10:10 +1 here too 21:10:26 proposed #agreed - 1091300 - AcceptedFreezeException Final - It would be good to get a tested fix into Final for the release. 21:11:38 ack 21:12:12 ack 21:12:16 #agreed - 1091300 - AcceptedFreezeException Final - It would be good to get a tested fix into Final for the release. 21:12:19 #topic (1192030) Workstation LiveISO refuses to boot on Hyper-V Generation 2 VM 21:12:22 #link https://bugzilla.redhat.com/show_bug.cgi?id=1192030 21:12:25 #info Proposed Freeze Exceptions, livecd-tools, POST 21:13:42 change seems fairly safe, though, god, dracut. 21:14:45 well, the change is in livecd-tools right? 21:15:06 +1 FE I have no idea how popular this is, but would be good to fix. 21:15:45 wfm, though not familiar enough to know if the patch'll work or not 21:16:04 nirik: yes, but it's to its iteraction with dracut 21:16:09 roshi: count yourself lucky! 21:16:31 proposed #agreed - 1192030 - AcceptedFreezeException - It would be good to get a tested fix included during freeze. 21:16:56 ack 21:17:01 ack 21:17:23 #agreed - 1192030 - AcceptedFreezeException - It would be good to get a tested fix included during freeze. 21:17:32 #topic (1271231) mate-compiz f23 livecd can't use new updated f23 default wallpaper 21:17:35 #link https://bugzilla.redhat.com/show_bug.cgi?id=1271231 21:17:38 #info Proposed Freeze Exceptions, mate-desktop, NEW 21:18:01 +1 21:18:04 simple and clean enough 21:18:09 * roshi loves these kinds of FEs 21:18:23 +1 21:18:29 :O 21:18:52 proposed #agreed - 1271231 - AcceptedFreezeException Final - It would be good for the MATE live to have the default F23 wallpaper. 21:18:56 +1 non-blocking required to use default ? 21:19:08 I don't think so 21:19:13 ack 21:19:16 but if they want to, no reason to stop them 21:19:18 ack 21:19:19 (3.18.1 builds are done, FE bug filed, putting the update together now) 21:19:25 ack 21:19:27 #agreed - 1271231 - AcceptedFreezeException Final - It would be good for the MATE live to have the default F23 wallpaper. 21:19:37 #topic (1212148) Review Request: python-pyeclib - Python interface to erasure codes 21:19:40 #link https://bugzilla.redhat.com/show_bug.cgi?id=1212148 21:19:42 #info Proposed Freeze Exceptions, Package Review, MODIFIED 21:21:00 * nirik voted +1 in bug 21:21:15 ok, so this is to keep openstack-swift in F23 21:21:20 +1, sure 21:21:31 since it fixes a problem related to dependencies, I'm +1. 21:21:51 yeah, ok 21:22:06 +1 21:22:17 proposed #agreed - 1212148 - AcceptedFreezeException Final - It would be good to get dep issues fixed for F23 packages and keep openstack-swift in F23. 21:22:41 ack 21:23:01 ack 21:23:33 #agreed - 1212148 - AcceptedFreezeException Final - It would be good to get dep issues fixed for F23 packages and keep openstack-swift in F23. 21:23:40 #topic (1271949) python-fiat has broken dependencies in F23 tree 21:23:40 #link https://bugzilla.redhat.com/show_bug.cgi?id=1271949 21:23:41 #info Proposed Freeze Exceptions, python-fiat, MODIFIED 21:24:03 +1 21:24:16 same as above, +1 21:24:18 +1 21:24:19 +1 here too 21:24:21 proposed #agreed - 1212148 - AcceptedFreezeException Final - It would be good to get dep issues fixed for F23 packages. 21:24:30 ack 21:24:40 ack 21:24:42 ack 21:24:46 er, proposed #agreed - 1271949 - AcceptedFreezeException Final - It would be good to get dep issues fixed for F23 packages. 21:24:52 wrong bug # 21:24:59 #agreed - 1271949 - AcceptedFreezeException Final - It would be good to get dep issues fixed for F23 packages. 21:25:03 ack 21:25:09 #topic (1270663) Failure to install: systemd-219-13.fc22.x86_64 was supposed to be installed but is not! 21:25:12 #link https://bugzilla.redhat.com/show_bug.cgi?id=1270663 21:25:15 #info Proposed Freeze Exceptions, rpm, NEW 21:26:04 +1 21:27:27 why does this need to be in the frozen package set? 21:27:31 and it looks like it's already fixed 21:28:31 aiui, getting this fixed removes a blocker for cockpit, which is in the set 21:29:31 it says for cockpit *development* 21:30:10 ah 21:30:12 right 21:30:13 also it sounds like it might already be fixed. ;) I'd punt for more testing... 21:30:13 * adamw pings stefw 21:31:15 that update isn't in stable 21:31:21 and obviously won't get there unless the bug gets an FE 21:32:35 yeah. 21:34:03 * adamw still can't quite see a justification for it as an FE though 21:34:08 proposal - punt and ask proposer for a justification? 21:34:17 yeah, I thought it was blocking something in cockpit for F23 21:34:21 +1 21:34:26 +1 21:35:11 proposed #agreed - 1270663 - Punt Final - We need some form of justification for why this needs an FE to move forward. 21:35:35 ack 21:35:37 ack 21:35:57 #agreed - 1270663 - Punt Final - We need some form of justification for why this needs an FE to move forward. 21:36:00 ack 21:36:04 #topic (1270568) smb fails to start 21:36:05 #link https://bugzilla.redhat.com/show_bug.cgi?id=1270568 21:36:05 #info Proposed Freeze Exceptions, samba, ON_QA 21:36:45 is smb on any media? 21:36:51 * nirik wishes for a pdc 21:37:03 I suspect it's on Workstation 21:37:05 * kalev checks. 21:37:09 nirik: I was about to ask the same question... 21:37:24 can be fixed with a 0day though, right? 21:37:47 * roshi hasn't seen any services (aside from rngd) fail to start on fresh installs 21:37:52 I don't fully understand the bug, is it that smb is totally busted or is it only busted for upgrades? 21:38:01 if it's only for upgrades then 0day is just fine 21:38:02 and if they're updating from f22, a 0day fixes this 21:38:03 it's not in the workstation installer tree - https://dl.fedoraproject.org/pub/alt/stage/23_TC9/Workstation/x86_64/os/Packages/s/ 21:38:31 -1 21:38:35 then, there is no point in having it as FE. -1 21:38:38 side note: we should probibly kill rngd sometime. ;) 21:39:32 proposed #agreed - 1270568 - RejectedFreezeException Final - This does affect any of the release media and can be fixed with a 0-day update for upgrades from F22. No need for an FE. 21:39:34 i think the rngd bug got mostly fixed at some point... 21:40:03 hold on, gimme a minute to check comps and kickstarts 21:40:16 it's definitely not in Workstation, I just checked livecd logs 21:40:25 but it maybe be in Server, since it's in https://dl.fedoraproject.org/pub/alt/stage/23_TC9/Server/x86_64/os/Packages/s/ 21:40:43 it's in the server DVD, yeah 21:40:53 fedora-installer-server.ks has @smb-server , it's in that group 21:40:59 adamw: rngd got kinda pulled into the kernel. the pkg doesn't do anything anymore and should die (as far as I last looked) 21:41:01 so if it fails OOTB it's worth an FE 21:41:02 * adamw testing 21:42:47 * adamw should really get used to using virt-install or something one of these days 21:43:20 * roshi just ripped the virt-install guts out of testcloud 21:45:06 just installing samba 21:45:18 roshi: well, i mean, anything other than manually reinstalling in virt-manager :P 21:45:54 so, being able to start from a fresh install without having to reinstall? 21:46:03 looks like it starts up fine. 21:46:05 backing stores! 21:46:21 so, seems like an update-only issue, -1 21:46:25 -1 21:46:32 you don't have the updates-testing one do you? 21:46:38 but sure if it's just updates -1 21:46:42 proposed #agreed - 1270568 - RejectedFreezeException Final - This does affect any of the release media and can be fixed with a 0-day update for upgrades from F22. No need for an FE. 21:46:51 patch 21:47:01 proposed #agreed - 1270568 - RejectedFreezeException Final - This doesn't affect any of the release media and can be fixed with a 0-day update for upgrades from F22. No need for an FE. 21:47:06 s/does/doesn't/ 21:47:21 ack 21:47:23 ack 21:47:27 nirik: no, i turend u-t off. 21:47:29 ack 21:47:31 #agreed - 1270568 - RejectedFreezeException Final - This doesn't affect any of the release media and can be fixed with a 0-day update for upgrades from F22. No need for an FE. 21:47:34 k. just checking. ;) 21:47:35 that's all the FEs 21:47:48 I filed one new, but not sure if you guys want to vote on it today :) 21:47:52 #topic Open Floor 21:48:16 https://bugzilla.redhat.com/show_bug.cgi?id=1272249 21:48:16 wait nope 21:48:18 #topic (1272249) Include GNOME 3.18.1 in Fedora 23 21:48:18 #link https://bugzilla.redhat.com/show_bug.cgi?id=1272249 21:48:18 #info Proposed Freeze Exceptions, distribution, MODIFIED 21:48:55 +1 21:49:05 I'd rather get this tested no instead of after release... 21:49:12 +1 for sure 21:49:15 +1 subject to the plan we agreed earlier 21:49:23 +1 21:49:24 +1 yeah that ^ 21:49:27 +1 21:49:30 we'll do a TC10 without it and a TC11 with and if it looks like there are any issues with TC11 we'll back it right back out again 21:49:32 TC w/o it first, then another the following day with it? 21:49:39 roshi: i can request 'em both today 21:49:44 we'll see how fast dgilmore can spit them out :) 21:50:45 proposed #agreed - 1272249 - AcceptedFreezeException Final - It would be good to get this tested before release. We'll cut one regular TC without this change, and another with it included. If this update causes issues we'll revert to the first TC created. 21:51:04 is that clear enough? 21:52:45 works for me 21:52:53 sure.ack 21:52:56 ack 21:53:01 #agreed - 1272249 - AcceptedFreezeException Final - It would be good to get this tested before release. We'll cut one regular TC without this change, and another with it included. If this update causes issues we'll revert to the first TC created. 21:53:07 alright, that's it 21:53:11 #topic Open Floor 21:53:14 anything else? 21:53:20 we could do accepted blockers, but i think i'm basically on top of 'em 21:53:29 * roshi has to depart 21:53:33 * nirik too 21:53:34 if you want to, go for it 21:53:39 * kalev three 21:53:43 well, i dunno what the story is with https://bugzilla.redhat.com/show_bug.cgi?id=1263677 21:53:54 but everyone's leaving, so i guess i'll figure it out on my own 21:53:58 *weeps, grabs whisky bottle* 21:54:23 it's just gonna be me and jpigface and satellit and they've probably got some like, actual testing to do or something 21:54:37 oh hey! 21:54:51 oh no, never miond. 21:54:52 adamw: sorry, I'm going to bed hehe 21:54:54 guess I'll set the fuse then :p 21:54:59 3... 21:55:07 night guys 21:55:21 night 21:55:23 2... 21:55:27 thanks for coming! 21:55:31 see you all monday :p 21:55:49 1... 21:55:53 #endmeeting