16:00:11 #startmeeting f18-alpha-blocker-review-6 16:00:11 Meeting started Wed Sep 5 16:00:11 2012 UTC. The chair is tflink. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:11 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:00:11 #meetingname f18-alpha-blocker-review-6 16:00:11 The meeting name has been set to 'f18-alpha-blocker-review-6' 16:00:16 #topic Roll Call 16:00:30 * kparal sneaks in 16:00:31 Who's ready for the weekly blocker review fun time? 16:00:49 kparal: sneaks in? I saw you join :-D 16:00:50 here 16:00:58 * satellit listening 16:01:05 #chair kparal adamw 16:01:05 Current chairs: adamw kparal tflink 16:01:07 * akshayvyas is here 16:01:54 dang, the blocker tracking page looks old already 16:02:11 * jreznik is here 16:02:11 old in the sense that I've been working on the re-skin and that already looks better 16:02:25 morning 16:02:38 adamw: morning! 16:02:45 this meeting should just move back into QA channel 16:02:48 forgot to screen 16:02:49 brb 16:03:30 it makes absolutely no sense hosting meetings here 16:03:38 or to...the meeting channel. 16:03:48 yeah, i think it's just mindless inertia at this point 16:04:07 I disagree - how do you schedule meetings that could last up to 4 hours 16:04:11 ? 16:04:16 well, -qa then, or -meeting-1 16:04:18 adamw: meeting channel is not a bad idea as there are people you can ping for more info but conflicts could arrise (and I know, we have -1, -2, -3) 16:04:25 it's not like we have a shortage of meeting rooms 16:04:30 its nice and quiet in here 16:04:47 QA is better and that's where usually all involved reside 16:04:48 personally, I don't care as long as there aren't people pestering us about when we'll be done 16:05:06 qa is probably better 16:05:08 i think QA is better personally 16:05:11 sadly 16:05:20 this is the first blocker meeting ive attended 16:05:27 * tflink makes note to change the channel next time 16:05:53 okey dokey 16:05:55 #action tflink to change announcement to use #fedora-qa instead of #fedora-bugzappers for the next blocker review meeting 16:06:14 anyhow, it sounds like we have enough people to get this party started 16:06:24 lets do it 16:06:28 * kparal cheers 16:06:34 and done everything is broken still ;() 16:06:36 :) 16:06:39 wrong 16:06:57 i have a working f18 kde install 16:07:03 we have a couple of bugs to review today but first ... the always exciting and invigorating boilerplate! 16:07:10 pretc6 dvd 16:07:10 #topic Introduction 16:07:20 #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:07:28 #info We'll be following the process outlined at: 16:07:28 #link https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting 16:07:44 #info The bugs up for review today can be found at: 16:07:44 #link http://qa.fedoraproject.org/blockerbugs/current 16:07:53 #info The criteria for release blocking bugs can be found at: 16:07:54 #link https://fedoraproject.org/wiki/Fedora_18_Alpha_Release_Criteria 16:07:54 #link https://fedoraproject.org/wiki/Fedora_18_Beta_Release_Criteria 16:07:54 #link https://fedoraproject.org/wiki/Fedora_18_Final_Release_Criteria 16:08:10 #info Up for review today are: 16:08:13 #info 18 Proposed Blockers 16:08:13 #info 15 Accepted Blockers 16:08:13 #info 3 Proposed NTH 16:08:14 #info 4 Accepted NTH 16:08:29 so much fun today 16:08:29 any objections to starting with the proposed blockers? 16:08:38 i think there may be some undocumented blockers :x 16:08:39 so much fun, I can hardly contain myself :) 16:08:53 dan408-: perhaps 16:09:01 ill hold it for open floor 16:09:07 let's get the ball rolling ... 16:09:13 or you could have proposed them, either way 16:09:17 proposed ones... 16:09:19 #topic (851212) error: cannot invoke setopt() - perform() is currently running 16:09:22 #link https://bugzilla.redhat.com/show_bug.cgi?id=851212 16:09:24 Bug 851212: unspecified, unspecified, ---, dlehman, VERIFIED , error: cannot invoke setopt() - perform() is currently running 16:09:25 #info Proposed Blocker, VERIFIED 16:09:44 * kparal loves verified status 16:09:59 kparal: +1! 16:10:02 did we ever figure out what was going on here? 16:10:05 no 16:10:12 but i don't think anyone else has hit this 16:10:18 oh actually 16:10:23 it was in POST status before 16:10:25 no-one spoke up in the report, i can't recall anyone mentioning it on-list or on irc or in the forums 16:10:27 -1 blocker 16:10:30 so anaconda devs probably fixed something 16:10:33 so i'm -1 blocker but +1 nth 16:10:44 -1 blocker, +1 nth 16:10:45 I'm for closing as fixed and not voting at all 16:10:56 kparal: are you sure? 16:11:09 why not? can't reproduce now 16:11:18 possibly https://lists.fedorahosted.org/pipermail/anaconda-patches/2012-August/000815.html . 16:11:28 ive never seen this issue 16:11:29 kparal: it's marked as fixed in 18.6.4-1 16:11:32 which isn't pushed stable yet 16:11:34 proposed #agreed 851212 - RejectedBlocker, AcceptedNTH - Doesn't seem to be wide-spread enough to justify blocker status but is nasty enough to justify NTH status. 16:11:34 so we can't really close it 16:11:39 ack/nak/patch? 16:11:39 ack 16:11:42 ack 16:11:43 ack 16:11:44 ack 16:11:45 ack 16:11:48 its also a different kernel 16:11:50 #agreed 851212 - RejectedBlocker, AcceptedNTH - Doesn't seem to be wide-spread enough to justify blocker status but is nasty enough to justify NTH status. 16:11:58 #topic (853985) KDM autologin does not work on Live 16:11:58 #link https://bugzilla.redhat.com/show_bug.cgi?id=853985 16:11:58 #info Proposed Blocker, ON_QA 16:12:00 Bug 853985: unspecified, unspecified, ---, rdieter, ON_QA , KDM autologin does not work on Live 16:12:12 I don't think this is an alpha blocker 16:12:20 neither do I 16:12:23 no 16:12:35 tflink: you can't login on kde spin 16:12:35 beta blocker maybe 16:12:39 there is a problem that KDM does not present a user list 16:12:45 it's a bit awkward in that you have to know the username is liveuser 16:12:47 so you have to KNOW the user is liveuser 16:12:47 can't login? can't you login as liveuser? 16:12:51 if you don't know what to write as login 16:13:01 with GDM it is easier, you just click on a name 16:13:07 tflink: you can but you have to know to write "liveuser" as username 16:13:14 jreznik: getting xorg working was a problem, i know its not related to live but that was an issue i encountered last night 16:13:15 certainly at least nth for me 16:13:22 yeah, I'd be OK with nth 16:13:27 -1 blocker, +1 nth 16:13:30 ack 16:13:44 * jreznik would say it's blocker... and definitely nth 16:13:56 beta? 16:14:08 jreznik: +1 16:14:10 dan408-: alpha - you can't login to kde live 16:14:12 I would also say it's a blocker 16:14:13 i'm probably +1 blocker given that it's pretty hard to guess the username if you don't know it 16:14:20 without manual intevention 16:14:20 release notes 16:14:23 proposed #agreed 853985 - RejectedBlocker AcceptedNTH - This doesn't prevent use of the KDE livecd but users do have to know to login as 'liveuser' which is not optimal. 16:14:30 ack/nak/patch? 16:14:32 ack 16:14:34 jreznik ok youve convince me +1 16:14:37 ack 16:15:00 nack... 16:15:01 * jreznik would be ok with nth but still thinks it's blocker... 16:15:01 do we have enough +1 blocker votes to accept it? 16:15:03 nack 16:15:06 nack 16:15:20 i see five at least. 16:15:23 it's now based on prefdm f17 service 16:15:29 nak without patch or reason gets you a slap in the face 16:15:32 so should be ok now 16:15:43 tflink: for me it's blocker 16:15:45 * kparal proposed to vote on +1 blocker 16:15:49 *proposes 16:15:51 tflink: reason is 'we want it to be blocker' :) 16:16:05 tflink: must boot to a working graphical environment without unintended user intervention 16:16:08 yes 16:16:11 where is the criteria that says the DM's need to display user names 16:16:20 Viking-Ice: see my post 16:16:23 proposed #agreed 853985 - AcceptedBlocker - adamw wants it to be a blocker, no other reason needed :) 16:16:28 patch? :) 16:16:29 ack 16:16:32 nack 16:16:32 it's unintended user intervention 16:16:44 tflink: I told you reason :) 16:16:54 adamw wants +1 16:16:54 it's alpha and we have not blocked it in the past when GDM showed this behavior 16:17:13 viking-ice +1 16:17:25 Viking-Ice: it's different for KDM 16:17:34 Viking-Ice: GDM gives you a user list, so all you have to do is click the only entry on the list 16:17:36 pretty obvious 16:17:39 proposed #agreed 853985 - AcceptedBlocker - Violates the following F18 alpha release criteria for KDE live spin - "When booting a system installed without a graphical environment, or when using a correct configuration setting to cause an installed system to boot in non-graphical mode, the system should boot to a state where it is possible to log in through at least one of the default virtual consoles" 16:17:40 KDM just gives you a 'username' dialog 16:17:44 ack 16:17:46 ack 16:17:52 nack 16:17:53 ack 16:17:58 Viking-Ice: patch? 16:18:05 Viking-Ice: so if you don't know the user for the live environment is called 'liveuser', you can't get in 16:18:10 ok, ack 16:18:21 with gdm, you can click on 'liveuser' 16:18:26 all reporters now the liveuser and we can mention this in the release notes for alpha 16:18:34 I'm not sure about the cited criterion, but I'm ack on the status 16:18:50 kparal: I'm open to other criterion suggestions 16:18:57 it's a bit tricky for the criteria 16:18:59 i think this is an important alpha blocker which may be due to others 16:19:00 oh, I grabbed the wrong one 16:19:00 I don't think we have any that matches directly 16:19:01 which i was ignoring for the sake of speed 16:19:05 and if reporters dont read the release notes thats their problem 16:19:08 can we move on 16:19:22 we have 4 acks, one nack, let's just take it and move on? 16:19:35 that's leave 'adamw wants it' criterion 16:19:39 we #6 says its fixed in update 16:19:41 yes 16:19:43 then be sure to make yet another criteria change 16:19:55 adamw wants it is good enough for me 16:19:57 s/leave/keep 16:20:05 #agreed 853985 - AcceptedBlocker - Violates the following F18 alpha release criteria for KDE live spin - "When booting a system installed without a graphical environment, or when using a correct configuration setting to cause an installed system to boot in non-graphical mode, the system should boot to a state where it is possible to log in through at least one of the default virtual consoles" 16:20:09 dan408: that's never a good enough reason for anything. 16:20:09 * kparal slaps kparal for bad english 16:20:21 definitely not the right criterion, though 16:20:24 adamw: :) 16:20:30 Viking-Ice: we should do that anyway, as there's really no criterion that says 'you have to be able to get to a live desktop' clearly 16:20:41 Viking-Ice: #5 kinda means it, but in a silly way 16:20:45 adamw, we should leave the live stuff out for alpha 16:21:02 It's alpha! 16:21:04 Viking-Ice: why? 16:21:07 so? 16:21:24 Viking-Ice: but live is main distribution channel for us... default media... 16:21:34 yeah it is 16:21:44 it's a lot easier to test a livecd because you don't need to install in order to test 16:21:45 its hard enough to find the darn dvd 16:22:10 we are ot now 16:22:11 everyone gets sent to live cds 16:22:17 #topic (853415) firstboot isn't installed and run during first boot 16:22:17 #link https://bugzilla.redhat.com/show_bug.cgi?id=853415 16:22:17 #info Proposed Blocker, MODIFIED 16:22:19 Bug 853415: unspecified, unspecified, ---, notting, MODIFIED , firstboot isn't installed and run during first boot 16:22:34 vlocker 16:22:38 this is not fixed 16:22:38 blocker 16:22:54 dan408: it wasn't in TC5, but it will be in TC6 16:22:57 and probably in pre-TC6 16:22:59 no 16:23:01 if you use netinst for installation, it's fixed. so we just need to do a new compose 16:23:03 i got firstboot from a pre-TC6 install test 16:23:11 DVD? 16:23:12 this was not fixed in tc-6 unless I missed it' 16:23:14 netinst 16:23:17 dvd. 16:23:18 +1 blocker 16:23:18 DVD 16:23:22 Viking-Ice: there is no tc6 yet. 16:23:30 yum update updates firstboot 16:23:33 run firstboot 16:23:35 +1 blocker 16:23:40 dan408: if it got installed but didn't run, that's not this bug. 16:23:41 does not work properly 16:23:56 that's the other bug. 16:23:56 it runs. 16:23:59 there are several 16:24:05 adamw, sorry "pre" 16:24:15 proposed #agreed 853415 - AcceptedBlocker - Violates the following F18 alpha release criterion: "In most cases (see Blocker_Bug_FAQ), a system installed according to any of the above criteria must boot to the 'firstboot' utility on the first boot after installation, without unintended user intervention, unless the user explicitly chooses to boot in non-graphical mode. The firstboot utility must be able to create a working user account" 16:24:26 ack 16:24:29 ack 16:24:30 ack 16:24:31 ack 16:24:31 proposed #agreed 853415 - AcceptedBlocker - Violates the following F18 alpha release criterion: "In most cases, a system installed according to any of the above criteria must boot to the 'firstboot' utility on the first boot after installation, without unintended user intervention, unless the user explicitly chooses to boot in non-graphical mode. The firstboot utility must be able to create a working user account" 16:24:40 does that all show up? 16:24:46 yes 16:24:48 #agreed 853415 - AcceptedBlocker - Violates the following F18 alpha release criterion: "In most cases, a system installed according to any of the above criteria must boot to the 'firstboot' utility on the first boot after installation, without unintended user intervention, unless the user explicitly chooses to boot in non-graphical mode. The firstboot utility must be able to create a working user account" 16:24:57 this bug is for it doesn't get installed _at all_ 16:24:58 #topic (853609) liveinstaller crashes when selecting non english language 16:25:00 yes tflink 16:25:01 #link https://bugzilla.redhat.com/show_bug.cgi?id=853609 16:25:03 Bug 853609: unspecified, unspecified, ---, anaconda-maint-list, NEW , liveinstaller crashes when selecting german language 16:25:04 #info Proposed Blocker, NEW 16:25:06 adamw, hm let me check 16:25:35 adamw: is the dvd compiled from updates-testing? 16:25:45 dan408: no 16:25:56 dan408: but for 853415, the issue is not any package, but comps 16:25:57 i think it should be. 16:26:02 no, that would be completely wrong 16:26:06 at least for alpha 16:26:14 the whole point of the freeze is to keep the compose package set stable 16:26:16 I don't think that I grabbed an updated comps for pretc6 16:26:25 tflink: ah. 16:26:30 ok that might have been it 16:26:42 adamw, firstboot got installed of the dvd but not run 16:27:04 * kparal add 853609: please also see "see also" bugs, they might be related 16:27:09 and it probably didnt run due to comps change 16:27:12 Viking-Ice: what version of firstboot? 16:27:24 dan408: no, comps affects the installed package set only. the compose must have used a recent-enough comps. 16:27:31 * adamw is +1 blocker on this bug, btw... 16:27:42 well base was renamed standard... last night. 16:27:44 18.2.2 16:27:57 yeah it's still a blocker 16:27:57 Viking-Ice: hrm, that's bad. i'd expect it to have run. oh, you said KDE? 16:28:05 yeah, I'm probably +1 blocker since it gets crashy 16:28:16 the crash also occurs for Spanish 16:28:22 adamw, Gnome and the graphical target in general seem messed up 16:28:23 IIRC 16:28:26 i ran it manually and it came up in ncurses terribly 16:28:46 Viking-Ice: like i said, i tested a netinst install and it worked fine...firstboot worked, gnome was fine 16:28:57 it's crasher... but do we have criteria for installer translation? 16:29:03 * dan408- notes that he did use kde 16:29:11 jreznik: nope 16:29:19 jreznik: it's a conditional fail of the 'installer must work' criterion 16:29:23 adamw, I did dvd in vm ( and will to another with live-cd to usb test in hour or so ) 16:29:28 jreznik: in the case of some languages 16:29:29 s/to/do 16:29:32 regardless.. i couldnt run tar because of the comps change for example 16:29:47 proposed #agreed 853609 - AcceptedBlocker - Violates the following F18 alpha release criterion when selecting some non-english languages - "The installer must boot and run on all primary architectures, with all system firmware types that are common on those architectures, from default live image, DVD, and boot.iso install media when written to an optical disc and when written to a USB stick with at least one of the officially supported methods" 16:29:50 so whether it's a blocker is a question of how common we think the cases that cause the problem are. which, if we're talking german and spanish, i'd say is pretty common 16:29:51 ack 16:29:57 ack 16:30:03 ack, just checked 16:30:03 Viking-Ice: i wonder if it matters whether you set a root password during install 16:30:05 Viking-Ice: did you? 16:30:09 this sadly has to be ack 16:30:10 ack 16:30:14 adamw, yup I did 16:30:20 Viking-Ice: yeah, me too. hrm. 16:30:25 i guess we'll see what happens with tc6... 16:30:27 #agreed 853609 - AcceptedBlocker - Violates the following F18 alpha release criterion when selecting some non-english languages - "The installer must boot and run on all primary architectures, with all system firmware types that are common on those architectures, from default live image, DVD, and boot.iso install media when written to an optical disc and when written to a USB stick with at least one of the officially supported methods" 16:30:41 #topic (852875) firstboot's service file needs updating for replacement of prefdm.service with per-dm services and systemd presets 16:30:44 #link https://bugzilla.redhat.com/show_bug.cgi?id=852875 16:30:46 #info Proposed Blocker, ON_QA 16:30:49 Bug 852875: high, unspecified, ---, vpodzime, ON_QA , firstboot's service file needs updating for replacement of prefdm.service with per-dm services and systemd presets 16:30:50 adamw: you have to set a root pw or you cant login because firstboot didnt start anyway but are you saykng firstboot checks if a root user exists? 16:31:17 sounds like a blocker to me 16:31:26 sure 16:31:29 yup 16:31:55 dan408: not 'check', but that somehow it doesn't work if you don't set a root password. but that doesn't appear to be the case. 16:32:03 +1 16:32:23 yeah not the case here 16:33:05 ok 16:33:19 proposed #agreed 852875 - AcceptedBlocker - Violates the following F18 alpha release criterion: "In most cases, a system installed according to any of the above criteria must boot to the 'firstboot' utility on the first boot after installation, without unintended user intervention, unless the user explicitly chooses to boot in non-graphical mode. The firstboot utility must be able to create a working user account" 16:34:01 #5 says update is pushed 16:34:04 ack 16:34:07 ack 16:34:08 ack 16:34:14 #agreed 852875 - AcceptedBlocker - Violates the following F18 alpha release criterion: "In most cases, a system installed according to any of the above criteria must boot to the 'firstboot' utility on the first boot after installation, without unintended user intervention, unless the user explicitly chooses to boot in non-graphical mode. The firstboot utility must be able to create a working user account" 16:34:21 it is pushed and with netinst firstboot runs just fine 16:34:23 #topic (853238) Yum tries to size check the DVD when getting a local file 16:34:26 #link https://bugzilla.redhat.com/show_bug.cgi?id=853238 16:34:27 Bug 853238: unspecified, unspecified, ---, packaging-team, VERIFIED , Yum tries to size check the DVD when getting a local file 16:34:28 #info Proposed Blocker, VERIFIED 16:34:50 pretty clear blocker 16:35:08 yup 16:35:13 whart was the behavior with this one? 16:35:15 proposed #agreed 853238 - AcceptedBlocker - Violates the following F18 alpha release criterion: 'When booting from a DVD ISO image, the installer must be able to use the DVD local package source options' 16:35:27 dan408-: couldn't install using DVD as pkg source 16:35:33 ack 16:35:35 ack 16:35:36 this is fixed 16:35:38 ack 16:35:49 #agreed 853238 - AcceptedBlocker - Violates the following F18 alpha release criterion: 'When booting from a DVD ISO image, the installer must be able to use the DVD local package source options' 16:35:57 and it definitely didnt exist in tc5 16:36:07 that's because a new yum was pulled in 16:36:10 #topic (853253) anaconda (textmode) crashes with unexpected input 16:36:10 #link https://bugzilla.redhat.com/show_bug.cgi?id=853253 16:36:10 #info Proposed Blocker, ON_QA 16:36:12 Bug 853253: medium, medium, ---, jkeating, ON_QA , anaconda (textmode) crashes with unexpected input 16:36:21 ok so can we close that? 16:36:35 no, it's not pushed to stable yet 16:36:40 k 16:36:52 I'm -1 blocker +1 NTH on this 16:36:57 same here 16:37:14 im not so sure 16:37:18 nvm, I was mis-remembering criteria 16:37:21 +1 blocker 16:37:25 the criterion is probably " The installer must be able to complete an installation using the text, graphical and VNC installation interfaces " ? 16:37:31 +1 blocker 16:37:33 i am +1 blocker 16:37:34 all of them? 16:37:36 "The installer must be able to complete an installation using the text, graphical and VNC installation interfaces " 16:37:43 ack 16:37:46 kparal was faster 16:38:01 clear violation 16:38:20 proposed #agreed 853253 - AcceptedBlocker - Violates the following F18 alpha release criterion: "The installer must be able to complete an installation using the text, graphical and VNC installation interfaces" 16:38:26 ack 16:38:28 ack 16:38:29 yeah, this looks NTH-y 16:38:30 for some reason, I thought text was moved to beta 16:38:38 eh? why is this blocker? 16:38:45 it only crashes with "unexpected input" 16:38:47 tflink: I'm wondering about that as well 16:38:51 i.e. if you stick to "expected input", it works 16:38:56 hehe 16:38:57 so it doesn't prevent text install from working... 16:39:03 twe can review it later 16:39:11 text mode is important to me 16:39:17 and 16:39:17 adamw: you have a point 16:39:50 adamw: agree 16:39:53 * tflink is definitely +1 NTH 16:39:58 what do we think about blocker? 16:39:59 it prevents text install from installing 16:40:04 dan408: it doesn't say that. 16:40:06 +1 blocker 16:40:07 dan408-: not if you type correctly 16:40:16 dont be ridiculous 16:40:17 i could wish for more context, though. 16:40:25 "input it wasn't expecting, in this case "12" instead of "1":" is a bit vague 16:40:38 I believe that's when selecting a menu option 16:40:40 adamw: what do you want to know? 16:40:42 right so lets review it keep it as blocker 16:40:49 yes, the text mode asks you for input 16:40:54 i.e. 1) to select timezone 16:41:00 ah, ok 16:41:02 then 1-20) for selecting the timezone 16:41:03 etc 16:41:06 right 16:41:12 so it's when you're typing one of those 16:41:22 and you put in incorrect value 16:41:23 eh, i don't want to hold things up too much 16:41:30 since we have the fix, nth/blocker isn't a huge deal 16:41:35 either way it goes in... 16:41:38 my fat fingers shouldnt crash text mode installer 16:41:38 it's a blocker per criteria 16:41:40 at the moment, sure 16:42:01 either the text installer is expected to work or not 16:42:04 dan408: :) 16:42:07 I'm with adam on this one. doesn't sound 100% blocker-y but I don't think it's worth spending 20 minutes arguing 16:42:16 Viking-Ice: it's a conditional failure, with the condition being 'you fat-finger an invalid entry'. that's a judgement call, not a clear-cut one. 16:42:23 tflink: +1 16:42:31 no the installer should not crap it self 16:42:32 Viking-Ice: i'm not sure you've yet understood that it *does* work - it only fails in the case where you give a completely invalid answer to a prompt. 16:42:56 but so long as that's clear and you're +1 blocker, fine by me... 16:43:00 then the breakage occurs in the installer for allowing the user to give invalid answer to begin with 16:43:02 Viking-Ice: no but I don't think that I'd be for slipping alpha if this was the last blocker left, either 16:43:20 but you would for "liveuser" 16:43:28 +1 blocker for now 16:43:37 Viking-Ice: sure, it's broken. you should always sanitize inputs. but broken != blocker. 16:43:40 * kparal is fine with both 16:43:42 sure, that happens regardless of whether or not the user makes a mistake 16:44:02 * tflink is somewhat remembering something about not spending 20 minutes arguing 16:44:09 any naks on the above proposed? 16:44:09 yeah, just call it and move on, i'll say ack 16:44:20 we can always revisit if the fix turns out to be a problem 16:44:27 #agreed 853253 - AcceptedBlocker - Violates the following F18 alpha release criterion: "The installer must be able to complete an installation using the text, graphical and VNC installation interfaces" 16:44:37 #topic (853576) Rescue mode fails in F18 Alpha TC4 - "cannot import name expandLangs" 16:44:40 #link https://bugzilla.redhat.com/show_bug.cgi?id=853576 16:44:42 Bug 853576: high, unspecified, ---, jkeating, ON_QA , Rescue mode fails in F18 Alpha TC4 - "cannot import name expandLangs" 16:44:42 #info Proposed Blocker, ON_QA 16:45:06 I think this is clear +1 blocker per criterion cited in comment 1 16:45:07 hrm, rescue mode worked for me on pretc6 16:45:39 there's a fix in for it, so that makes sense. 16:45:41 rescue mode is useless to me and i think the feature should be overhauled at some point 16:45:53 +1 blocker 16:45:56 ack 16:46:00 tflink: it's fixed in 18.6.5, which you put in pretc6. 16:46:00 +1 blocker 16:46:28 adamw: sure, but there's no mention of that in the bug 16:46:35 tflink: er, yes there is? 16:46:40 i think you need to hit refresh :) 16:46:49 comment #3 and #4 16:47:15 proposed #agreed 853576 - AcceptedBlocker - Violates the following F18 alpha release criterion: " The rescue mode of the installer must start successfully and be able to detect and mount an existing default installation" 16:47:21 ack 16:47:33 yeah, I had my numbers mixed up. I thought that .5 was in TC5 and .6 was in pretc6 for some reason 16:47:34 ack 16:47:38 ack 16:47:42 ack 16:47:44 #agreed 853576 - AcceptedBlocker - Violates the following F18 alpha release criterion: " The rescue mode of the installer must start successfully and be able to detect and mount an existing default installation" 16:47:54 #topic (853510) Libreport attempts to submit an empty file to RHBZ on anaconda crash 16:47:57 #link https://bugzilla.redhat.com/show_bug.cgi?id=853510 16:47:58 Bug 853510: unspecified, unspecified, ---, abrt-devel-list, MODIFIED , Libreport attempts to submit an empty file to RHBZ on anaconda crash 16:47:59 #info Proposed Blocker, MODIFIED 16:48:13 nth 16:48:23 +1, per criteria. 16:48:29 er, +1 blocker that is. 16:48:31 +1, per criteria 16:48:51 + 1 16:49:00 oh right we had put this in criteria now 16:49:17 proposed #agreed 853510 - AcceptedBlocker - Violates the following F18 alpha release criterion: "The installer must be able to report failures to Bugzilla and local disk, with appropriate information included" 16:49:20 ack 16:49:40 ack 16:49:42 ack 16:49:48 #agreed 853510 - AcceptedBlocker - Violates the following F18 alpha release criterion: "The installer must be able to report failures to Bugzilla and local disk, with appropriate information included" 16:49:48 ack 16:49:56 ack 16:49:58 #topic (853899) offline installation can't be done without network connection 16:50:01 #link https://bugzilla.redhat.com/show_bug.cgi?id=853899 16:50:03 Bug 853899: unspecified, unspecified, ---, rvykydal, POST , offline installation can't be done without network connection 16:50:04 #info Proposed Blocker, POST 16:50:29 i thnk this is fixed 16:50:37 oh this one gets a clear +1 blocker from me 16:50:46 dan408: it's not fixed in TC5 16:51:06 ok +1 then 16:51:06 I wasn't sure of correct milestone, so I picked Alpha just to start discussion 16:51:11 yeah +1, live installer does not proceed without network 16:51:13 yeah, not a clear blocker via criteria but implied 16:51:29 i'd say this is a conditional breakage of "When booting from a DVD ISO image, the installer must be able to use the DVD local package source options", in the case where you have no network connection 16:51:34 itll probably get closed today 16:51:37 and it's bad enough to be +1 blocker 16:51:49 * jreznik_ is not sure... 16:51:52 just leave as is 16:51:57 this probably should be stuffed into an criteria 16:51:59 or you could use "The installer must be able to complete package installation with the default package set for each supported installation method " 16:52:09 Viking-Ice: yeah, we could certainly have an explicit criterion for it 16:52:18 i think that last one i quoted is the best we have atm 16:52:21 the installer must be able to install without network connection etc.. 16:52:34 proposed #agreed 853899 - AcceptedBlocker - Violates the following F18 alpha release criterion: "The installer must be able to complete package installation with the default package set for each supported installation method" 16:52:37 dan408: it has to be accepted as blocker or nth, really, or else we'd be 'wrong' to take the fix. 16:52:38 ack 16:52:39 ack 16:52:39 the dvd never required network before 16:52:41 ack 16:52:51 ack 16:52:52 #agreed 853899 - AcceptedBlocker - Violates the following F18 alpha release criterion: "The installer must be able to complete package installation with the default package set for each supported installation method" 16:52:53 ack 16:53:03 dan408: oh I have hit cases with this with anaconda before 16:53:05 #topic (854209) The remote software origin name was not found 16:53:05 #link https://bugzilla.redhat.com/show_bug.cgi?id=854209 16:53:05 #info Proposed Blocker, NEW 16:53:07 Bug 854209: unspecified, unspecified, ---, hughsient, ASSIGNED , The remote software origin name was not found 16:53:38 viking i dont know what youre talking about 16:54:04 this sounds like a blocker to me 16:54:15 yep, +1 for blocker 16:54:17 have not hit this yet 16:54:23 sure +1 16:54:38 I did some debugging today - it's not Apper only, but PackageKit issue... hughsie knows about it 16:54:52 it seems so, otherwise wouldn't be able to update their Alpha's 16:54:53 well... 16:54:55 proposed #agreed 854209 - AcceptedBlocker - Violates the following F18 alpha release criterion: "The installed system must be able to download and install updates with yum and the default graphical package manager in all release-blocking desktops" 16:54:58 it makes pkgkit useless - even for updates 16:54:59 does it actually affect updates? 16:55:01 ohh that i did hit jreznik 16:55:06 adamw: yep 16:55:07 ah, okay. if it's tested to affect updates, then +1 16:55:17 ack 16:55:18 is it different from https://bugzilla.redhat.com/show_bug.cgi?id=852403 ? 16:55:18 I did not hit this in the vm 16:55:18 had to manually install via yum and rpm 16:55:19 Bug 852403: unspecified, unspecified, ---, mgrepl, NEW , PolicyKit authentication in Fedora 18 Alpha TC3 results in selinux denial 16:55:26 and had no problem manually update with yum 16:55:39 Viking-Ice: this seems to affect PackageKit-based things, not yum. 16:55:40 adamw: no, it isn't 16:55:57 jreznik_: erm, sorry, i could've asked that more clearly. is it a dupe or not? :) 16:55:58 polkit works 16:56:03 ok 16:56:14 adamw: no... see my comment in 852403 16:56:28 roger 16:56:41 if users have no problem updating via yum from cli then it's an nth from me 16:56:57 Viking-Ice: the criterion specifies the graphical utilities, though 16:57:04 16:57:07 Viking-Ice: download and install updates with yum and the default graphical package manager 16:57:08 yeah, we specifically require the graphical tools to work 16:57:09 so +1 16:57:17 for alpha really 16:57:19 any other ack/nak/patch? 16:57:25 ack 16:57:27 if criteria says so ack 16:57:33 Viking-Ice: I'm not sure we need graphical tools for Alpha neither 16:57:39 ack 16:58:07 ack 16:58:11 #agreed 854209 - AcceptedBlocker - Violates the following F18 alpha release criterion: "The installed system must be able to download and install updates with yum and the default graphical package manager in all release-blocking desktops" 16:58:22 #topic (854471) anaconda stop at the "Error checking storage configuration" 16:58:25 #link https://bugzilla.redhat.com/show_bug.cgi?id=854471 16:58:27 Bug 854471: unspecified, unspecified, ---, anaconda-maint-list, NEW , anaconda stop at the "Error checking storage configuration" 16:58:28 #info Proposed Blocker, NEW 16:58:42 I don't understand point 2. in steps to reproduce here 16:59:00 but I was contacted by ohudlick having exactly the same problem 16:59:09 jreznik_: viking-ice: do go ahead and propose a criterion change if you think it should be changed, but check the archives for any explanation of the current state... 16:59:10 and he tried all ways of partitioning 16:59:21 i did not see this with tc-5 or tc-pre6 16:59:31 ah manual partitioning 16:59:32 I haven't seen this either 16:59:40 I think that we need more details before accepting or rejecting this 16:59:45 Viking-Ice: as I say, he also tried automatic partitioning 16:59:53 tflink: +1 17:00:09 needinfo to duplicate 17:00:13 3GB is pretty small 17:00:14 tflink: it seems so. we need the logs 17:00:17 maybe this happens on too-small disks? 17:00:25 yeah, i think we need logs and more details of the scenario to be sure on this 17:00:28 adamw: oh, I didn't realize this. good point 17:00:46 small but should work thou 17:00:51 proposed #agreed 854471 - While this sounds like something that could be a problem, there is not enough information on the causes or steps taken to reproduce this issue to make a decision on blocker status at this time. Will re-visit when there is more data. 17:00:58 it happens in vm when we select dynamic aocation 17:01:08 alocation 17:01:13 akshayvyas: have you reproduced it as well? 17:01:22 yeah in tc 5 17:01:33 akshayvyas: disk size? 17:01:55 disk size was 4 gigs 17:01:58 Viking-Ice: i think 3GB is too small for a dvd install usually? 17:02:15 akshayvyas: please attach logs into that report if you can, thanks 17:02:26 punt now 17:02:29 ack 17:02:32 hm then the installer should know that 17:02:32 ack 17:02:34 ack 17:02:39 kpara: sure i will 17:02:42 #agreed 854471 - While this sounds like something that could be a problem, there is not enough information on the causes or steps taken to reproduce this issue to make a decision on blocker status at this time. Will re-visit when there is more data. 17:02:42 ack 17:02:50 Viking-Ice: yeah, it'd certainly be a bug, oldui did complain about too small disks i think. 17:02:51 #topic (854688) Live installation hangs with some languages 17:02:51 #link https://bugzilla.redhat.com/show_bug.cgi?id=854688 17:02:51 #info Proposed Blocker, NEW 17:02:53 Bug 854688: unspecified, unspecified, ---, anaconda-maint-list, NEW , Live installation hangs with some languages 17:03:12 is this a dupe of the other one? 17:03:23 might be 17:03:27 not sure yet 17:03:50 must be a dupe 17:04:44 kind of sounds that way 17:05:03 but I'm probably +1 blocker on this 17:05:06 tflink: yeah i think so 17:05:14 if it gets duped, it gets duped 17:05:16 * jreznik_ is rereading both 17:05:17 Viking-Ice: well, the superficial symptoms are different, this is a later crash 17:05:27 Viking-Ice: but kparal says the underlying cause might be the same (locale being set wrong) 17:05:31 so seems like it's uncertain right now 17:05:52 well after install local chosen in anaconda is not set et all 17:05:57 I'm still stuck on US 17:05:59 layout 17:06:08 so +1 for me too 17:06:13 and dupe it later if we have to 17:06:14 ack 17:06:26 adamw: +1 17:06:34 +1 17:06:45 proposed #agreed 854688 - AcceptedBlocker - Conditional volation of the F18 alpha release criterion for some non-english languages: "The installer must boot and run on all primary architectures, with all system firmware types that are common on those architectures, from default live image, DVD, and boot.iso install media when written to an optical disc and when written to a USB stick with at least one of the officially supported methods" 17:06:58 ack 17:06:59 ack 17:07:00 ack 17:07:15 #agreed 854688 - AcceptedBlocker - Conditional volation of the F18 alpha release criterion for some non-english languages: "The installer must boot and run on all primary architectures, with all system firmware types that are common on those architectures, from default live image, DVD, and boot.iso install media when written to an optical disc and when written to a USB stick with at least one of the officially supported methods" 17:07:27 #topic (854203) F18 uses the same desktop background as F17 17:07:28 #link https://bugzilla.redhat.com/show_bug.cgi?id=854203 17:07:28 #info Proposed Blocker, MODIFIED 17:07:29 Bug 854203: unspecified, unspecified, ---, davidz, MODIFIED , F18 uses the same desktop background as F17 17:07:50 not a blocker 17:08:12 +1 blocker, per criterion "The default desktop background must be different from that of the two previous stable releases" 17:08:14 not a blocker + I proposed we should just default to upstream background up to final on the -test list I believe 17:08:26 that's one stupid criteria 17:08:43 let's block the release because artwork aint ready enough 17:08:45 Viking-Ice: +1 17:09:02 Viking-Ice: that's the new criterion which just got reviewed on the list, so... 17:09:05 Viking-Ice: the reasons are stated on the mailing list. we don't want people to mistake F17 for F18 17:09:07 it's significantly less tight than the last one. 17:09:14 so, +1. 17:09:19 +1 as well 17:09:22 +1 17:09:23 it's in the criteria so ack 17:09:29 +1 nth 17:09:53 proposed #agreed 854203 - AcceptedBlocker - Violates the following F18 alpha release criterion: "The default desktop background must be different from that of the two previous stable releases" 17:09:55 ack 17:09:56 ack 17:10:00 ack 17:10:02 #agreed 854203 - AcceptedBlocker - Violates the following F18 alpha release criterion: "The default desktop background must be different from that of the two previous stable releases" 17:10:13 #topic (854512) root has a password on Live 17:10:13 #link https://bugzilla.redhat.com/show_bug.cgi?id=854512 17:10:13 #info Proposed Blocker, ASSIGNED 17:10:15 Bug 854512: unspecified, unspecified, ---, kanarip, ASSIGNED , root has a password on Live 17:10:30 this gets back to the livecd working correctly 17:10:36 not sure about blocker on this one, though 17:10:46 you can test livecd w/o root for the most part 17:11:08 I'm -1 blocker +1 nth on this one 17:11:18 what about bug reporting? 17:11:22 it didnt work that way on my side 17:11:24 Alpha is for public consumption 17:11:30 we want public to report bugs 17:11:35 e.g. attach /var/log/messages 17:11:45 tc5 live is not asking for root passwd 17:11:48 we don't have a criterion for this, so we'd have to agree there ought to be one, to take this as a blocker 17:11:54 akshayvyas: which one? 17:11:56 yes this bug says nothing about the live user not being in the wheel group you know like sudo su - 17:12:05 tc5 live gnome 17:12:07 or sudo or su - 17:12:07 hrm 17:12:32 does anyone else have the tc5 desktop live handy to check? 17:12:38 hmm 17:12:38 kparal: can you re-test and make sure you still see this? 17:12:45 sorry i just got into the office 17:12:47 let me check 17:12:49 adamw: re-test with what changes? 17:12:51 * jreznik_ is booting 17:12:56 kparal: does sudo work? 17:13:13 kparal: no changes, just try it again, since akshayvyas says he doesn't see it 17:13:27 tflink: sudo doesn't work 17:13:33 * kparal is booting Live TC5 17:13:40 * akshayvyas is testing again 17:13:54 yeah i dont have the live cd 17:14:15 almost there... liveuser... 17:14:38 no root password set 17:14:42 gosh, it works! 17:14:46 but it didn't! 17:14:50 kparal: :) 17:14:58 propose #agreed kparal to leave off the crack pipe 17:15:03 :D 17:15:04 * kparal is very confused now 17:15:11 :P 17:15:24 * kparal hides 17:15:32 yeah crack is bad for you alcohol on the other hand.. 17:15:39 let's skip this bug then 17:15:45 kparal, stay away from sober testing! 17:15:48 I'll re-test properly, both architectures etc 17:15:53 balmer peak 17:16:17 proposed #agreed 854512 - RejectedBlocker - It appears that if this is a problem, it doesn't show up every time. If it turns out to be a regularly re-occuring issue, please resubmit as a blocker 17:16:30 ack 17:16:30 i'm okay with that, or punt 17:16:30 ack 17:16:31 ack 17:16:39 ack 17:16:40 ack 17:16:53 #agreed 854512 - RejectedBlocker - It appears that if this is a problem, it doesn't show up every time. If it turns out to be a regularly re-occuring issue, please resubmit as a blocker 17:17:03 #topic (853988) liveinstall: kernel panic - unable to mount root fs on unknown-block(0,0) 17:17:06 #link https://bugzilla.redhat.com/show_bug.cgi?id=853988 17:17:07 Bug 853988: unspecified, unspecified, ---, anaconda-maint-list, NEW , liveinstall: kernel panic - unable to mount root fs on unknown-block(0,0) 17:17:08 #info Proposed Blocker, NEW 17:18:22 Vratislav is not sure how to solve this, but the issue is real 17:18:25 this time! 17:18:31 so this is the bug where live installs fail to boot? clear +1 17:18:38 yes 17:18:42 kparal: sure it's real this time :-P 17:18:45 +1 blocker 17:18:48 yup 17:19:56 +1 17:20:22 proposed #agreed 853988 - AcceptedBlocker - Violates the following F18 alpha release criterion: "In most cases, a system installed according to any of the above criteria must boot to the 'firstboot' utility on the first boot after installation, without unintended user intervention, unless the user explicitly chooses to boot in non-graphical mode. The firstboot utility must be able to create a working user account" 17:20:27 ack 17:20:28 I hate that criterion 17:20:31 ack 17:20:35 ack 17:20:36 ack 17:20:38 the content is fine, just the length 17:20:48 ack 17:20:50 #agreed 853988 - AcceptedBlocker - Violates the following F18 alpha release criterion: "In most cases, a system installed according to any of the above criteria must boot to the 'firstboot' utility on the first boot after installation, without unintended user intervention, unless the user explicitly chooses to boot in non-graphical mode. The firstboot utility must be able to create a working user account" 17:21:03 #topic (853587) Patch for "fix QtScript JIT crash (QTBUG-23871, kde#297661)" applied in qt-4.8.2-5 causes frequent segmentation faults 17:21:06 #link https://bugzilla.redhat.com/show_bug.cgi?id=853587 17:21:08 Bug 853587: unspecified, unspecified, ---, than, MODIFIED , Patch for "fix QtScript JIT crash (QTBUG-23871, kde#297661)" applied in qt-4.8.2-5 causes frequent segmentation faults 17:21:08 #info Proposed Blocker, MODIFIED 17:21:38 not sure this is a blocker since it doesn't appear to be reproducable 17:21:54 tflink: i've tried to shorten that criterion but couldn't see how, without losing meaning :/ suggestions welcome 17:22:10 footnotes? 17:22:13 is this just not a regular bug? 17:22:16 well, my understanding is that all sorts of qt-based apps crash all over the place 17:22:18 either way, can figure it out later 17:22:25 but yeah, it's not entirely clear 17:22:30 -1 blocker +1 nth 17:22:33 punt, wait for info 17:22:43 +1 nth 17:22:51 -1 blocker 17:22:58 *DE testing is for BETA! 17:23:14 +1 nth at least, punt on blocker 17:23:14 it's easily reproducible 17:23:21 just install kde into kvm... 17:23:32 100% reproducible there 17:23:45 jreznik: i have KDE working fine on preTC6 17:23:49 jreznik: how to reproduce 17:23:54 dan408: live or installation"? 17:23:58 installation 17:24:00 is this for live? 17:24:08 jreznik, that does not make it an alpha blocker thou you can easially reproduce it 17:24:10 ah, so it's not so much the crash but the origin of the issue and it's fix? 17:24:11 hmm, strange... a few people reports the same 17:24:20 just tell me a qt app to run 17:24:24 i dont normally use qt 17:24:36 vlc 17:24:44 Viking-Ice: but I expect it will affect most of the installations... 17:24:58 i base program please. 17:25:04 irrelevent DE testing is for BETA! 17:25:05 part of the @kde group 17:25:06 akshayvyas: no, the crash is in QtJavaScript - so it has to be JS one... kwin crashes for instance... 17:25:23 oops 17:25:27 kwin 17:25:28 Viking-Ice: we require some minimum desktop stuff to work at alpha. if kwin crashes, that's bad enough to hit. 17:25:35 we can not test DE functionality until after alpha history has touch us that much 17:25:53 kwin is fine 17:26:01 jreznik we'll discuss offline 17:26:03 well those of us that was here and live through it 17:26:04 adamw: I can't tell you more, for me it's 100% in KVM, reported by a lot of people here 17:26:04 a crash happy alpha seems like a bad idea if this is as bad as it sounds 17:26:16 i repeat, +1 nth and punt? 17:26:23 either way, sounds like punt blocker, +1 nth 17:26:26 since there's a fix all ready, if we just take it as nth the issue goes away... 17:26:36 +1 nth 17:26:37 it's definitely +1 nth, fix is ok 17:26:38 jreznik: using virtualbox here 17:26:49 +1 nth 17:26:50 dan408: maybe that's the problem but kvm is the must for us 17:26:55 i know 17:26:58 is kvm qt? 17:27:10 the build is done, if it as nth goes into, I'm ok 17:27:20 im just saying if kwin is qt wouldn't the entire DE crash? 17:27:41 proposed #agreed 853587 - AcceptedNTH - We need more information on the severity/frequency of the crash and testing of the fix before deciding on blocker status. However, releasing alpha with a frequently crashing KDE spin is not desired and thus, accepted as NTH for F18 alpha 17:27:44 dan408: no but also plasma crashes, you got black screen :) 17:27:51 i see 17:27:52 ack 17:27:52 ack 17:28:00 ack for now, I'll try to find more data 17:28:02 ack 17:28:15 all distros reverted that patch as far as I know 17:28:26 #agreed 853587 - AcceptedNTH - We need more information on the severity/frequency of the crash and testing of the fix before deciding on blocker status. However, releasing alpha with a frequently crashing KDE spin is not desired and thus, accepted as NTH for F18 alpha 17:28:35 #topic (835601) libparted crashes in mac_read on cheapo USB drive 17:28:36 #link https://bugzilla.redhat.com/show_bug.cgi?id=835601 17:28:36 #info Proposed Blocker, VERIFIED 17:28:38 Bug 835601: unspecified, unspecified, ---, bcl, VERIFIED , libparted crashes in mac_read on cheapo USB drive 17:29:27 this is why KDE Live on USB crashes 17:29:45 i don't see that it'd be desktop-specific? 17:29:53 I think this is just regular bug 17:30:05 afaik the trigger is to try and install from a live image written to USB 17:30:07 I'm not sure about GNOME, it might be affected too 17:30:17 possibly has to be a particular format stick or something, possibly any USB stick is enough 17:30:45 oh, not even a live image, just any 'write to USB and try to install' case 17:30:45 badly burned image is not blocking the release 17:30:51 Viking-Ice: i don't think it's 'badly burned' 17:30:59 though it's not 100% clear 17:31:00 it sounds like the read was getting messed up 17:31:07 cheap cd/dvds not working are not blocking the release 17:31:13 * adamw sees if he can ping bcl 17:31:13 "It ends up that the problem was in max_read, it would change the sector_size to 2048 without re-allocating the read buffer." 17:31:34 it should not be desktop specific, I don't see any reason - as it's in parted 17:31:36 Viking-Ice: while the title and description mention cheap USB sticks, I'm not convinced that those are requied to reproduce 17:31:43 * adamw is asking bcl 17:31:43 this affects probably all USBs, certainly affects ours in the office 17:32:08 kparal: they weren't bad burns, right? 17:32:16 adamw: no, tried several times 17:32:18 * nirik notes fesco is discussing anaconda ticket if anyone in here wants to weigh in or watch. 17:32:24 adamw: btw. fesco! 17:32:33 talking about upgrades 17:32:40 ah, nirik was faster :) thx 17:32:50 should we pause this meeting for a while? 17:33:18 yep 17:34:04 sorry, distracted by fesco meeting 17:34:29 hey 17:34:40 hey bcl 17:35:07 so we just need to be clear about the trigger for 835601 17:35:14 is it as simple as 'any install from USB is going to hit it'? 17:35:17 so, I'm not sure if you will always see this, since it is a memory corruption. 17:35:24 or is there some kind of specific property of the USB stick that causes it? 17:35:37 But I've seen it here on 2 machines with 2 different usb sticks. 17:35:55 * tflink hasn't gotten around to testing on bare metal yet 17:36:19 it was running off the end of a 512b buffer, so behavior could be undefined. 17:36:39 okay, thanks 17:36:43 for me that's bad enough for blockeriness 17:36:51 clumens also saw this a while back and at that time I couldn't duplicate it, so I'm pretty happy. 17:36:52 +1 17:37:00 i'd only be -1 if you needed a really weird stick or a badly-burned one to hit it 17:37:14 +1 17:37:27 yeah, I hit it with TC3 and F17 netinst.iso 17:38:07 proposed #agreed 835601 - AcceptedBlocker - Conditional violation of the following F18 alpha release criterion for a non-insignificant number of USB devices: "The installer must boot and run on all primary architectures, with all system firmware types that are common on those architectures, from default live image, DVD, and boot.iso install media when written to an optical disc and when written to a USB stick with at least one of the officially sup 17:38:17 ack 17:38:34 ack 17:38:58 any other ack/nak/patch? 17:39:10 ack 17:39:18 * tflink prefers to have at least 3 unless there's an obvious violation 17:39:24 #agreed 835601 - AcceptedBlocker - Conditional violation of the following F18 alpha release criterion for a non-insignificant number of USB devices: "The installer must boot and run on all primary architectures, with all system firmware types that are common on those architectures, from default live image, DVD, and boot.iso install media when written to an optical disc and when written to a USB stick with at least one of the officially supported me 17:39:40 OK, that would be all of the proposed blockers that we had at the start of the meeting 17:39:46 on to proposed NTH 17:39:59 #topic (849731) pungi needs new magic file location for powerpc ISOs 17:39:59 #link https://bugzilla.redhat.com/show_bug.cgi?id=849731 17:39:59 #info Proposed NTH, ON_QA 17:40:01 Bug 849731: urgent, urgent, ---, dennis, ON_QA , pungi needs new magic file location for powerpc ISOs 17:40:24 if this is PPC-only, it's NTH. 17:40:50 yeah, it's only proposed as NTH 17:41:28 I'm OK with NTH but would like to see it tested more before pushing to stable 17:41:44 oh, we're on proposed nth. ok 17:41:46 missed that 17:42:15 done with proposed blockers for today 17:43:17 proposed #agreed 849731 - AcceptedNTH - This is a blocker for PPC, making it an NTH overall. However, it would be good to see some more testing of the new build with non-ppc arches before allowing it to be pushed to stable or used in an alpha TC/RC 17:43:25 ack 17:43:57 ack 17:44:05 #agreed 849731 - AcceptedNTH - This is a blocker for PPC, making it an NTH overall. However, it would be good to see some more testing of the new build with non-ppc arches before allowing it to be pushed to stable or used in an alpha TC/RC 17:44:14 #topic (844463) Xorg blows assertion at startup: Xorg: privates.c:560: dixPrivatesSize: Assertion `!screen_specific_private[type]' failed. 17:44:17 #link https://bugzilla.redhat.com/show_bug.cgi?id=844463 17:44:18 Bug 844463: high, unspecified, ---, alevy, VERIFIED , Xorg blows assertion at startup: Xorg: privates.c:560: dixPrivatesSize: Assertion `!screen_specific_private[type]' failed. 17:44:19 #info Proposed NTH, VERIFIED 17:44:51 ah, this is the qxl bug 17:44:54 +1 NTH 17:45:44 +1 17:45:55 +1 17:46:00 +1 17:46:36 proposed #agreed 844463 - AcceptedNTH - Virt bugs are beta, so this is not a blocker but there is a lot of VM testing going on for alpha and a working default graphics adapter would be preferred 17:47:29 ack 17:47:36 ack 17:47:36 ack 17:47:43 #agreed 844463 - AcceptedNTH - Virt bugs are beta, so this is not a blocker but there is a lot of VM testing going on for alpha and a working default graphics adapter would be preferred 17:47:51 #topic (852845) ship systemd preset for lightdm 17:47:51 #link https://bugzilla.redhat.com/show_bug.cgi?id=852845 17:47:51 #info Proposed NTH, MODIFIED 17:47:53 Bug 852845: unspecified, unspecified, ---, rdieter, MODIFIED , ship systemd preset for lightdm 17:48:01 +1 NTH since it's a blocker for a non-primary DE 17:49:10 proposed #agreed 852845 - AcceptedNTH - Prevents lightdm from stating, which is a non-primary DM - makes it NTH 17:49:18 which DE uses lightdm? LXDE? 17:49:59 I think so 17:50:12 nirik? 17:50:25 Xfce does in f18 17:50:32 so ack 17:50:34 thx 17:50:36 LXDE still uses lxdm I think. 17:51:46 proposed #agreed 852845 - AcceptedNTH - Prevents lightdm from stating, which is the DM for XFCE. As a non-primary DE, any blocker there becomes an NTH 17:52:27 ack 17:53:04 #agreed 852845 - AcceptedNTH - Prevents lightdm from stating, which is the DM for XFCE. As a non-primary DE, any blocker there becomes an NTH 17:53:56 ack. :) 17:55:11 sorry, /me is engaged in the fesco meeting... 17:55:46 same here 17:56:00 mostly watching, though. I don't have much to add 17:56:07 no problem here 17:56:13 I'm reading that too 18:00:15 ok, we're done with proposed NTH 18:00:23 on to accepted, non-verified blockers 18:00:38 #topic (848641) Fedora 18 Alpha TC2 fails to boot from USB stick (written by livecd-iso-to-disk) 18:00:41 #link https://bugzilla.redhat.com/show_bug.cgi?id=848641 18:00:42 Bug 848641: high, unspecified, ---, mgracik, ON_QA , Fedora 18 Alpha TC2 fails to boot from USB stick (written by livecd-iso-to-disk) 18:00:43 #info Accepted Blocker, ON_QA 18:01:14 sounds like this needs testing but _should_ be fixed 18:01:25 pretc6 was built with the new lorax 18:01:42 the pre tc6 dvd images seem to be larger then the previous one thus I have not manage to confirm or deny it since I only have 4GB usb thumb drive handy 18:01:43 tflink: haven't tested that one yet 18:01:59 Viking-Ice: netinst should be enough to test 18:02:22 kparal, no not if you are going to install from usb drive 18:02:29 it occurs to me that I'm not sure if the spin-kickstart changes supposedly needed have made it through yet 18:02:33 off the thumbdrive 18:03:17 Viking-Ice: I meant just to check whether booting is Ok 18:03:17 well, since we have that bug for install not working from usb-written images, it kinda implies someone somewhere is managing to boot usb-written images =) 18:03:29 but yeah, bcl should know the status of booting-from-usb overall better than anyone 18:03:33 adamw: those are Lives 18:03:41 not the original report 18:04:08 TC5 Live can be converted to USB, TC5 DVD or netinst can't 18:04:16 #info fixed lorax was used for pretc6, will be used for TC6. This needs testing before moving to VERIFIED 18:04:42 dd should be working, litd still needs a few tweaks but I need a working .iso to make sure I'm testing against the 'real thing' 18:04:47 okay 18:04:49 with tc5 I manage to boot it not install from but the pre-tc6 dvd image is to large to fit the same usb now ( otherwise I would be testing it as we speak ) 18:04:52 so we should just spin up tc6/rc1 and see what happens 18:04:58 ? 18:05:18 yes. more rc's the better. 18:05:31 would testing with pretc6 be good enough for now instead of just hoping that TC6 will be OK? 18:05:43 pretc? 18:05:53 isn't that stacking things a bit deep :) 18:06:12 yeah is there a way i can compile my own DVD? 18:06:27 maybe, but it's a lot quicker to spin up only a DVD or boot.iso than a full TC 18:06:27 should also have the new parted ideally. 18:06:37 I should mention that there is an inst.stage= entry that gets create now on the pre-tc6 dvd 18:06:39 no offense but i dont want to wait around to get a compiled ISO with stuff from updates-testing 18:06:52 then I'd need to spin a new iso, pretc6 doesn't have the new parted 18:06:54 bcl: it's what we're calling the smoke-test images tflink builds, now. 18:07:03 why isn't this in git 18:07:05 Viking-Ice: it should be inst.stage2= 18:07:07 and why isn't compilable 18:07:12 dan408: you can build your own dvd, yeah. 18:07:17 how? 18:07:17 dan408: we are mostly testing the anaconda for alpha 18:07:22 dan408: search for using pungi 18:07:23 Viking-Ice: i know. 18:07:29 tflink: thanks. 18:07:38 are we on open floor yet? 18:07:41 no 18:07:44 k 18:07:46 no, we're reviewing accepted blockers 18:07:56 sorry im at work 18:07:57 tflink: where's the pretc? on alt? 18:08:03 in and out of conciousness here 18:08:08 bcl, it's inst.stage2= 18:08:10 bcl: http://imagebuilder.fedoraproject.org/testimage/18/pretc6/ 18:08:22 thanks 18:08:32 it sounds like I'll be spinning another test image with the blocker/NTH fixes from today, though 18:09:02 tflink: yes asap please a lot of stuff didn't get pulled 18:09:03 libreport and parted come to mind first, might be others 18:09:06 tflink, are you going to pull in the latest kernel for that one 18:09:06 if i may for a moment 18:09:15 last night i did a lot of testing 18:09:24 Viking-Ice: probably not unless it's been accepted as NTH or blocker 18:09:43 any other info on this USB install bug? 18:09:45 sorry, gnome-shell crashed 18:10:01 let's move on 18:10:03 #topic (851295) splitsep doesn't correctly handle variables with escaped spaces 18:10:06 #link https://bugzilla.redhat.com/show_bug.cgi?id=851295 18:10:08 Bug 851295: urgent, unspecified, ---, dracut-maint, MODIFIED , splitsep doesn't correctly handle variables with escaped spaces 18:10:09 #info Accepted Blocker, MODIFIED 18:10:19 oh, this is a good one, as we're not at all sure how to be sure it's fixed 18:10:28 bcl, can you tell from tc5 or pre-tc6 if the fix for this worked? 18:10:30 related to 848641, no? 18:10:43 yeah, iirc. 18:11:13 if it has inst.stage2=hd:LABEL= and label has spaces and it boots when you dd it, it worked. 18:11:24 kparal: lol 18:11:35 * kparal notes we have a new proposed blocker: 854586 18:11:40 bah 18:11:43 you just beat me to it :) 18:11:59 bcl: ah, okay. i'll add that to the ticket. should be easy to test. 18:12:07 beating adamw means I'm superman 18:12:10 #info still needs testing. if a dd'd USB iso has inst.stage2=hd:LABEL= and works, this can be moved to VERIFIED 18:12:47 #topic (850775) display managers aren't enabled after installation 18:12:47 #link https://bugzilla.redhat.com/show_bug.cgi?id=850775 18:12:48 #info Accepted Blocker, MODIFIED 18:12:50 Bug 850775: unspecified, unspecified, ---, systemd-maint, MODIFIED , display managers aren't enabled after installation 18:13:13 bcl, the current pre-tc6 format is inst.stage2=hd:LABEL=Fedora\x2018\x20x86_64 when using dd 18:13:16 sounds like this is mostly fixed but not quite 100% yet 18:13:50 Viking-Ice: does it boot? 18:14:07 yeah, i think we have kde and gnome fixes in at least now 18:14:10 this is related to xorg comps change 18:14:15 or caused 18:14:39 yep, looks like gnome/kde is fixed 18:14:58 adamw, the installer boots then stops with black screen and a mouse point but I'm sure that's because I did not large enough stick ( dd: writing `/dev/sdb': No space left on device ) I just went ahead and booted that stick anyway 18:15:08 jreznik: ok but what about the xorg group 18:15:25 will test tonight ( or rather as soon as I find my larger usb sticks ) 18:15:30 dan408: not part of this bug. 18:15:41 i understand but it probably caused this bug 18:15:46 no, it didn't. 18:15:47 or had something to do with it 18:15:55 this bug is to do with service enablement, nothing to do with package groups. 18:16:03 k 18:16:12 note 'aren't enabled', not 'aren't installed' 18:16:15 the window manager service, correct? 18:16:21 yes. 18:16:24 er, sorry 18:16:25 got it. 18:16:27 login manager, rather 18:16:30 yep 18:16:36 session manager or window manager? 18:16:43 i'd think session manager 18:17:26 I'm reading this as 90% fixed but there are still some changes needed before it's closed 18:17:57 am I missing something? Is it fixed enough to drop as a blocker or split the remaining issue(s) off into another bug? 18:17:59 okay 18:18:12 no we cannot drop this is a blocker 18:18:23 adamw, the proper way to handle things is with type oneshot unit these days not with rc.local 18:18:57 tflink: probably fixed enough, but we should confirm with tc6/rc1. 18:18:58 administrator then order that type oneshot unit they created as they see fit 18:19:16 i think the proper way to handle this is to make gnome overrule 18:19:17 Viking-Ice: well that's always been the case, the 'proper' way to do it with sysv is to create a service as well 18:19:30 just like every other version of fedora unless someone decides to change that 18:19:34 but rc.local is just for the case where you just want to run a one-liner and it really feels like too much effort to create a whole service for it (whether systemd-native or sysv-native) 18:19:45 #info this is probably fixed enough for alpha but still needs testing with TC6/RC1. If there are remaining issues after that testing, they may be split off into another bug 18:19:51 but the rc.local thing isn't blocker stuff, so not really on topic for this meeting 18:19:58 yup 18:20:10 yep 18:20:15 anything else on this bug? 18:20:39 please see my comments 18:21:01 which comments? 18:21:14 okay 18:21:32 question how is it supposed Fedora supposed to behave if you have multiple DE's installed? 18:21:35 tflink: nope. 18:21:50 that's also not an alpha-blocking case, so we don't have to care about it here. thankfully... 18:21:51 dan408: that sounds like it's outside the scope of this bug, to be honest 18:22:55 i dont think so, it's talking about de's and which would take over 18:23:07 with multiple DE's installed 18:23:14 unless im missing something 18:23:17 for alpha it's enough for each DE to work seperatly 18:23:18 please let me know 18:23:26 it's a complex case 18:23:30 does one DE fire up if multiple are installed? 18:23:32 Viking-Ice: maybe for alpha, but it's a major concern right now 18:23:32 and it may actually be relevant for the *bug* 18:23:38 but it's not relevant for the alpha-blocking part of the bug 18:23:43 fine 18:23:44 dan408: not to me it's not 18:23:57 tflink: frankly i think everyone's too confused to know. 18:23:58 adamw / tflink can we discuss offline 18:24:02 yeah, or in -qa 18:24:04 k 18:24:06 but let's move this meeting on 18:24:07 cool, moving on 18:24:11 #topic (852403) PolicyKit authentication in Fedora 18 Alpha TC3 results in selinux denial 18:24:14 #link https://bugzilla.redhat.com/show_bug.cgi?id=852403 18:24:16 Bug 852403: unspecified, unspecified, ---, mgrepl, NEW , PolicyKit authentication in Fedora 18 Alpha TC3 results in selinux denial 18:24:17 #info Accepted Blocker, NEW 18:24:45 i can reproduce this 18:24:46 sounds like more testing is needed, at least 18:24:58 ok so why the heck arent we shipping selinux in permissive mode? 18:25:04 in alpha 18:25:36 do we have no criteria for selinux has to be working and error free for alpha? 18:25:43 s/no/now 18:25:53 not really 18:25:53 tflink: Jan is the whole week out, fwiw 18:25:56 dan408: if you've been able to reproduce the bug with newer versions, can you add comments to the bug? 18:26:20 Viking-Ice: the logic is that any sufficiently serious selinux issue will simply manifest as a breakage of the criteria as they stand 18:26:27 as in this case: it breaks the criterion about installing updates 18:26:38 see my latest comment 18:26:50 selinux should be shipped in permissive mode up to beta not block the release 18:26:54 in tc5, properly installed + firsboot it works 18:27:10 ok 18:27:15 #info tested in TC5, seems to be fixed 18:27:23 I had the same issue with tc3 and skipped firstboot... 18:27:27 maybe it is firstboot that affects it, then? 18:27:33 but pls - retest it somehow... 18:27:33 because i don't think we pulled the new selinux-policy for tc5 18:27:35 adamw: yep 18:28:00 #info a little more testing would be nice before moving the bug to VERIFIED 18:28:45 then the question is if we really want the new build/policy 18:28:47 FYI: there's a planned bugzilla outage at 3pm EDT (which I think is in about 30min). 18:28:52 I'll talk to mgrepl tmrw 18:29:14 jreznik: thanks, yeah 18:29:20 then let's get this moving - we're almost done. 1 more approved blocker and the new proposed blocker 18:29:21 nirik: thanks 18:29:36 tflink: i'm just about to propose 853788, fwiw. 18:29:37 #topic (849997) anaconda freezed after boot 18:29:37 #link https://bugzilla.redhat.com/show_bug.cgi?id=849997 18:29:37 #info Accepted Blocker, ON_QA 18:29:38 Bug 849997: unspecified, unspecified, ---, vpodzime, ON_QA , anaconda freezed after boot 18:29:57 so, there is a fix for this but we're not sure how to test it 18:30:45 the only way how to fix it is to build a custom image that causes exception in a different than main anaconda thread 18:30:46 any thoughts on whether we close it, assuming it's fixed or ask an anaconda dev for help on an updates.img? 18:30:51 so it's not really easy 18:30:54 close it I would say 18:31:03 i think we can just let it be closed when we push anaconda stable 18:31:07 and re-open if it shows up again 18:31:12 I would close it and reopen if we see it again 18:31:15 yup 18:31:19 v +1 18:31:30 adamw: +1 18:31:59 proposed #agreed 849997 - There is a fix for this, but it's not trivial to test. Close the bug once the next anaconda version is pushed to stable, re-open if this bug becomes a problem again 18:32:06 ack 18:32:11 ack 18:32:24 ack 18:32:37 #agreed 849997 - There is a fix for this, but it's not trivial to test. Close the bug once the next anaconda version is pushed to stable, re-open if this bug becomes a problem again 18:32:55 OK, lets try to do the 2 new proposed blockers and hope we can finish before the BZ outage 18:33:52 #topic (8543471) anaconda stop at the "Error checking storage configuration" 18:33:55 #link https://bugzilla.redhat.com/show_bug.cgi?id=854471 18:33:56 Bug 854471: unspecified, unspecified, ---, anaconda-maint-list, NEW , anaconda stop at the "Error checking storage configuration" 18:33:57 #info Proposed Blocker, NEW 18:34:10 that's not the new one 18:34:23 nope we have dealt with this one 18:34:33 hurry up post the link to the next one! 18:34:42 * kparal says 854586 18:35:04 whoops 18:35:06 #undo 18:35:06 Removing item from minutes: 18:35:07 #undo 18:35:07 Removing item from minutes: 18:35:09 #undo 18:35:09 Removing item from minutes: 18:35:38 854586, right? 18:35:53 tflink: yes 18:35:57 #topic (854586) OSError: [Errno 2] No such file or directory 18:35:57 #link https://bugzilla.redhat.com/show_bug.cgi?id=854586 18:35:57 #info Proposed Blocker, POST 18:35:59 Bug 854586: unspecified, unspecified, ---, bcl, POST , OSError: [Errno 2] No such file or directory 18:36:17 this bug tells me absolutly nothing about what the actual problem is 18:36:33 sounds like anaconda is missing a requires that causes problems during install? 18:36:38 yeah, it would help to have a reproducer 18:36:55 i'm guessing this is triggered when anaconda tries to call nm-connection-editor to do something and finds it isn't there, though 18:36:59 bcl, do you have any useful details? 18:37:11 we need more info on what the actual problem is and how it's affecting the overall experience 18:37:23 https://bugzilla.redhat.com/attachment.cgi?id=610009 18:37:42 looks like pyanaconda/ui/gui/spokes/network.py calls nm-connection-editor when you want to edit a connection 18:37:47 manually editing network settings? 18:37:55 seems so 18:38:17 i'll see if i can reproduce in pre-tc6 18:38:49 well I'm leaning towards for alpha we really should not require more then dhcp provided ip addresses to work 18:38:58 punt and vote in ticket if it's a big issue? 18:39:12 punt +nth 18:39:13 adamw: nm-blahblah moved 18:39:16 yeah, i'm leaning the same way as viking, but punt seems reasonable 18:39:22 bcl: when exactly is it needed? 18:39:24 so you won't be able to edit network connections w/o this 18:39:32 a requires in the anaconda.spec 18:39:44 i mean, what do you do in anaconda to make nm-c-e run 18:39:51 bcl: also we can't add a password for wifi? 18:39:51 the binary :) 18:39:56 sigh 18:39:58 * adamw is failing 18:40:05 i'm asking for the reproducer 18:40:10 to reproduce, i launch an install and...what? 18:40:18 not sure, I just read the logs. 18:40:27 when I hit 'Configure...' in the network spoke on pre-tc6 nothing *happens*, but i don't get a tb 18:40:31 go to Network, click Configure ... and nothing happens 18:40:31 probably click on network spoke and try to edit a connections. 18:40:33 * kparal just tested 18:40:38 kparal: right, same here... 18:40:46 can I ask a really stupid question? 18:40:54 history suggests the answer is 'yes' 18:41:06 do anaconda devs to any actual QA/testing of their own? 18:41:12 better to ask a stupid question than not to ask and then assume the answer 18:41:14 yes. 18:41:18 are you sure? 18:41:23 proposed #agreed 854586 - AcceptedNTH - Editing any connection in anaconda causes a crash due to moved binary in nm. Waiting for more information before making a decision on blocker status 18:41:30 ack on that 18:41:32 ack 18:41:40 #agreed 854586 - AcceptedNTH - Editing any connection in anaconda causes a crash due to moved binary in nm. Waiting for more information before making a decision on blocker status 18:41:40 ack 18:41:41 bcl: does adding the dep work for the DVD case as well? 18:41:48 I'm interested whether you can connect to wifi 18:41:54 * adamw never entirely sure how the anaconda environment for the dvd/netinst is constructed 18:42:02 adamw: wasn't there another bug that you were proposing? 18:42:04 yeah 18:42:12 anaconda + wifi has never worked for me 18:42:14 853788 18:42:34 Viking-Ice: same. 18:42:37 adamw: the install env on the DVD is pretty much the same as boot.iso - pungi pretty much adds an internal repo to the boot.iso and remakes the iso 18:42:54 Viking-Ice: i noticed though some of the staging drivers are enabled in the 3.6-rc4 kernel now though so it might be fixed soon 18:43:04 kparal: is /usr/bin/nm-connection-editor present? 18:43:34 tflink: so, anything the anaconda package depends on will be pulled into the netinst/dvd anaconda env? okay. 18:43:34 ack on this being a blocker 18:43:40 bcl: I just closed it :/ 18:43:54 pretty much 18:43:58 like the kernel right? 18:44:11 The change was fairly recent, NetworkManager 0.9.3.997-1 18:44:12 adamw: anything not ripped out by lorax, yes 18:44:25 OK. 18:44:36 next bug! 18:44:38 #topic (853788) anaconda (text mode) set root password appears to not to work 18:44:41 #link https://bugzilla.redhat.com/show_bug.cgi?id=853788 18:44:42 fixed 18:44:43 Bug 853788: medium, unspecified, ---, jkeating, POST , anaconda (text mode) set root password appears to not to work 18:44:43 #info Proposed Blocker, POST 18:44:45 in tc6 18:44:51 seems like a pretty clear blocker 18:44:57 yup 18:45:01 oh is this for text mode? 18:45:16 tflink, can you pull in that patch for tc6 18:45:34 +1 blocker 18:45:34 well let's just rather call it rc1 18:45:39 ack 18:45:57 please keep it as tc6 18:46:11 proposed #agreed 853788 - AcceptedBlocker - Violates the following F18 alpha release criterion: "When booting a system installed without a graphical environment, or when using a correct configuration setting to cause an installed system to boot in non-graphical mode, the system should boot to a state where it is possible to log in through at least one of the default virtual consoles" 18:46:19 ack 18:46:20 ack 18:46:23 ack 18:46:35 Viking-Ice: I'll be pulling in any new blocker/nth fixes if there's another pretc6 18:46:43 #agreed 853788 - AcceptedBlocker - Violates the following F18 alpha release criterion: "When booting a system installed without a graphical environment, or when using a correct configuration setting to cause an installed system to boot in non-graphical mode, the system should boot to a state where it is possible to log in through at least one of the default virtual consoles" 18:47:14 Viking-Ice: unless you're talking about 853788 - I have no idea how to do anaconda builds 18:47:32 if its not in an anaconda build, I won't be pulling it in 18:47:34 probably compile from anaconda git 18:47:42 ooooh, are we done? 18:47:46 i think nirik and dgilmore could help you with that 18:47:49 I think the process is a bit more complicated than that, TBH 18:47:51 I was talking about Jesse's proposed patch in 853788 18:48:01 transfx privs etc. 18:48:12 spelling errors of tools aside ... 18:48:43 anyhow, I do believe that would be all of the bugs up for review today 18:48:45 any more bugs? 18:48:49 only 3 hours! 18:48:53 #topic Open Floor 18:48:55 ok 18:48:58 ok so i didnt see any of the issues i experienced last night really brought up 18:49:10 i did pretc6 dvd install 18:49:10 dan408: are there bugs filed? 18:49:16 im about to file them 18:49:23 want to talk to you guys first 18:49:43 #1) ongoing on dvd boot -> no selinux policy found and perfectmsr msg 18:49:46 anyone got anything on this? 18:50:17 not even sure what exactly that is, to be honest 18:50:21 k ill file a bug 18:50:31 dracut + selinux policy 18:50:33 I'd say file a bug, if all else fails, it can be closed/duped 18:50:42 #2) no way to isntall multiple DE's known bug with anaconda already 18:50:48 by design, notabug 18:50:56 #3) base comps name changed to standard 18:51:08 after I installed from DVD last night even the tar command didn't work 18:51:13 i was able to login as root 18:51:16 haven't heard about that one 18:51:25 X11 wasn't installed 18:51:32 tar didn't work 18:51:36 many basic things didnt work 18:51:41 did you strace it 18:51:53 tflink: notified notting it should be fixed hopefully next time you recompile tc6 18:52:05 dan408: is there a bug? 18:52:14 no but I'll be happy to file one now 18:52:20 what did notting say what the problem? 18:52:26 was missing there 18:52:30 he didnt even know there was a problem until i talked to him 18:52:33 he made a commit last night 18:52:34 to comps 18:52:40 dan408: the 'no selinux policy found' message has been around forever, it doesn't appear to be an actual problem 18:52:46 dan408: all my boots have that message, whether working or not 18:52:53 adamw: then hide it 18:53:05 sure, but it's not a major issue to worry about at this point. 18:53:10 i know 18:53:13 just not used to it 18:53:21 it's like f17 cannot open font file = true 18:53:23 oh 18:53:25 another one 18:53:26 grub menu 18:53:27 I actually think it's dracut/systemd/selinux which is being shipped with anaconda 18:53:37 has anyone tried to actually boot into single user mode yet? 18:53:43 yeah, I hit the grub menu one, too 18:53:49 haven't gotten around to filing a bug, though 18:53:51 is there a bug open on that? 18:53:54 ok i will file it 18:53:59 there might be, do a search first 18:53:59 that should be a blocker 18:54:10 if it's filed it's not a blocker 18:54:10 I remember seeing a report about it, not sure if a bug was ever filed 18:54:15 k 18:54:24 so basically last night 18:54:27 i installed KDE + a bunch of add ons 18:54:35 firstboot didn't run 18:54:46 ran yum update -> noticed firstboot got updated 18:54:51 ran it and graphics were messed up 18:54:59 downloaded kernel 3.6-rc4 source code 18:55:02 recompiled 18:55:08 I mentioned un-edible grub in vm on the test list 18:55:17 kinda helped but didn't fix the Xorg problem 18:55:20 Viking-Ice: do you know if a bug was filed? 18:55:31 dan408: did you try using vga drivers instead of qxl? 18:55:36 did yum install @base @standard xorg* @kde -y 18:55:40 logged in 18:55:42 ran startx 18:55:43 boom 18:55:47 KDE spherical cow 18:55:59 I did not file one I just cursed since for F18 I probably will be using gummiboot 18:56:24 dan408: did you figure out what the root of the problem was? 18:56:38 yeah 18:56:47 base comps being renamed standard 18:56:54 is there a bug filed? 18:56:58 someoen from the anaconda team wasi n #fedora-devel and was not happy 18:57:12 will file one 18:57:21 oh, I need to make sure I remember to check into spin-kickstarts for the dvd ks 18:57:23 but i ask you recompile tc6 first 18:57:33 bcl, does the anaconda team know about @standard? 18:57:37 renaming 18:57:41 they do now. 18:57:44 ok 18:57:45 #action tflink to check on whether spin-kickstarts is up to date enough for alpha 18:57:50 this is why i asked that really stupid question earlier 18:58:06 Viking-Ice: in reference to what? package groups? I can't speak for the whole team you know :) 18:58:07 the only question that is stupid is the one that get's never asked 18:58:24 bcl, I thought you where the team ;) 18:58:31 not even close. 18:58:40 comps changes are all sorts of fun and have a history of getting changed without telling anyone 18:59:06 just talking about it gives you an headache 18:59:07 There was something notting was doing earlier this morning, I haven't kept track. 18:59:09 ok gotta jump on a conf call 18:59:20 In general if stuff changes it is helpful to email the anaconda-devel list. 18:59:26 will bug you guys later @tflink and @adamw 18:59:43 any other topics to bring up? 18:59:59 plenty 19:00:02 but day job calls 19:00:06 those are the main ones 19:00:09 for this meeting? 19:00:12 bcl, are you guys running different version of dracut/selinux/system then is current in anaconda? 19:00:21 s/system/systemd 19:00:22 just that anaconda team needs to do more qa 19:00:24 and im godo 19:00:26 good* 19:00:45 #info Fedora 18 alpha blocker review meeting #7 will be on 2012-09-12 @ 16:00 in #fedora-qa if alpha slips again 19:01:44 Viking-Ice: sorry, that isn't specific enough. 'you guys' == ? We're using whatever is getting pulled in for the isos. Hopefully the latest and greatest stuff. We're trying to make the images match a normal system as best as we can. 19:02:00 comps changes are REALLY hard to test 19:02:12 if you don't know they're coming 19:02:25 they affect netinstalls and DVD/live installs differently 19:02:37 anyhow, I'm setting the fuse on this 19:02:39 bcl, meaning team anaconda and by versions I speaking of what is current in F18 19:02:41 3 hours is enough for now 19:03:12 aaannd .... we're done 19:03:17 * tflink will send out minutes shortly 19:03:18 okay 19:03:24 thanks for coming, everyone! 19:03:32 adamw: unless you had something to add? 19:03:55 * tflink assumes not 19:03:59 #endmeeting