17:00:20 #startmeeting F-15-Alpha Blocker Bug Review 17:00:20 Meeting started Fri Feb 11 17:00:20 2011 UTC. The chair is jlaska. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:20 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:00:37 #meetingname F15Alpha-bug-review 17:00:37 The meeting name has been set to 'f15alpha-bug-review' 17:00:43 #topic Roll call 17:00:44 * brunowolff is here 17:00:48 * rbergeron is here 17:00:49 hey bruno 17:00:55 * jlaska tips hat to rbergeron 17:01:02 * rbergeron waves back 17:01:42 * jlaska waits a few minutes longer for participants 17:01:47 * tflink is here 17:01:52 * bcl waves 17:01:57 hellooooo gents 17:02:01 * clumens THUD 17:02:03 lol 17:02:14 * heffer is here too. to lurk :D 17:02:19 * Viking-Ice joins in.. 17:02:48 * jsmith stumbles in late 17:02:49 hello lurkers! 17:02:52 * dgilmore is here 17:02:54 jsmith: just finishing roll call here 17:02:56 :) 17:02:57 * jsmith is here! 17:03:10 where I dont see him? 17:03:10 alright, we got dgilmore wearing the rel-eng cloak today 17:03:33 wow mubarak resigned. just as a side note :D 17:03:53 let's get started 17:03:57 #topic Introduction 17:04:09 Just a quick reminder, the SOP for this meeting is available at https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting 17:04:54 #info our purpose in this meeting is to review proposed _Alpha_ blocker bugs and nice-to-have bugs and decide whether to accept them, and to monitor the progress of fixing existing accepted blocker and nice-to-have bugs 17:05:48 * jlaska grabs bug links ... 17:06:49 17:06:53 * rbergeron whistles 17:07:05 dam I hate those elevator musics.. 17:07:52 okay, I have a query that lists the Proposed, but not reviewed, F15Alpha bugs 17:07:56 #link http://bit.ly/glBfr8 17:08:03 * rbergeron is really good at whistling muzak 17:08:31 as we review the bugs, the appropriate whiteboard text will be added: either AcceptedBlocker or RejectedBlocker 17:08:37 or it will be moved to another Beta or Final tracker 17:08:52 is anyone willing to assist with making the necessary changes to each bug? 17:09:12 alternatively, if someone wants to walk us through the bugs, I can make the changes to the bugs 17:09:33 alright ... we'll deal with it for each bug ... 17:09:49 #undo 17:09:49 Removing item from minutes: 17:09:55 Revised URL that is sorted by component ... 17:10:01 #link http://bit.ly/eBLZKl 17:10:12 and we'll start with anaconda ... 17:10:15 * rbergeron can make the changes to each bug 17:10:23 rbergeron: you rock, thank you! 17:10:26 #topic https://bugzilla.redhat.com/show_bug.cgi?id=676519 17:10:27 Bug 676519: high, unspecified, ---, anaconda-maint-list, NEW, anaconda 15.19 fails to assemble software raid 10 device 17:10:44 this issue was raised by Clyde on test@ 17:10:48 notablocker 17:10:58 Adam and I both added some feedback to the bug already that this does not appear to impact the current Alpha criteria 17:11:17 RAID-10 is something we *could* consider for Beta, but definitely a Final criteria 17:11:32 * rbergeron nods 17:11:33 applicable final criteria would be our catch-all ... "The installer must be able to create and install to any workable partition layout using any file system offered in a default installer configuration, LVM, software, hardware or BIOS RAID, or combination of the above " 17:11:40 dont think it's even a beta blocker but final criteria 17:12:02 well, our Beta criteria don't specifically address RAID-10, but other RAID levels 17:12:13 I don't think RAID-10 was intentionally omited 17:12:24 so what revisit at beta ? 17:12:25 has anyone else attempted to reproduce this? 17:12:31 clumens: I haven't yet 17:12:41 Viking-Ice: lemme note that we need to revisit RAID-10 for beta perhaps? 17:13:29 #help Should RAID-10 install scenarios qualify under the Beta release criteria? 17:13:48 so I think this is straight forward ... 17:13:50 and therefore, should i make a storage test for them? 17:14:00 clumens: oh ... I see your point 17:14:11 certainly worth adding to the TODO list ... not sure about priority yet though 17:14:30 I was actually referring to the bug revisit it on beta blocker meeting 17:14:54 if the beta criteria says raid it means all raid combo one would think 17:15:20 but this one is not a alpha blocker I think 17:15:22 proposed #agreed 676519 - does not impact Alpha release criteria - move to F15Beta and review RAID criteria for Beta 17:15:29 ack/nack/patch? 17:16:00 * dgilmore is ok with beta for this 17:16:21 I've got 3 acks from adamw, Viking-Ice and jlaska I think 17:16:29 any objections .. moving on in 10 ... 17:16:33 jlaska: and an ack from me 17:16:44 thx 17:16:53 #agreed 676519 - does not impact Alpha release criteria - move to F15Beta and review RAID criteria for Beta 17:17:14 rbergeron: can you change this one to blocks: F15Beta, and maybe cut'n'paste the #agreed ? 17:17:24 Yes. :) 17:17:28 thank you! 17:17:38 #info need to assess whether RAID-10 meets Beta release criteria 17:17:47 next up ... 17:17:48 #topic https://bugzilla.redhat.com/show_bug.cgi?id=676551 17:17:49 Bug 676551: unspecified, unspecified, ---, anaconda-maint-list, NEW, on 15 Alpha TC1, stage1 doesn't prompt for mediacheck 17:17:56 patch is on the list. 17:18:08 * jlaska notes ... I'm going to try and move quickly on the bugs ... feel free to stop me or jump in if I miss anything 17:18:32 clumens: sweet ... what's the new intended behavior here? 17:18:55 NOTE: We do not presently have criteria that dictate whether mediacheck should pass 17:19:01 we should prompt for media check if you're doing an install from DVD. for netinst.iso usage, i don't think there's any point in doing media check (see comment in bug). 17:19:06 I dont think media check falls under alpha criteria ? 17:19:06 I don't think we need to specifically call that level of detail out, but I could be wrong 17:19:23 okay (to both) 17:19:32 clumens: i think thats fine 17:19:36 i definitely want media check running in the final release 17:20:05 proposed #agreed 676551 - Does not impact Alpha criteria, move to F15Blocker, update release notes with change? 17:20:08 ack/nack/patch? 17:20:13 +1 17:20:14 ack 17:20:18 ack 17:20:36 clumens: do we have someone helping the installer team with documenting behavior changes in the release notes? 17:21:01 not yet 17:21:20 but if we do, they can start with https://fedoraproject.org/wiki/Anaconda/Changes 17:22:23 jsmith: rbergeron: do either of you know how we would queue up something for the release notes 17:22:29 just add a '?' release_notes flag? 17:22:46 oyyyy. 17:23:01 jsmith: do you know if the docs folks do that? 17:23:18 let's do that, and synchronize with docs to see if that's acceptable. 17:23:37 if not, we have this notated in the meeting notes and we can figure out a more effecient/optimal way to make sure they know. 17:23:54 #agreed 676551 - Does not impact Alpha criteria, move to F15Blocker to track netinst.iso mediacheck prompt, ensure release notes are planned for updates about initrd.img changes. 17:24:13 People can fill in some base stuff in the doc beats. 17:24:18 * rbergeron nods 17:24:31 #info set '?' release_notes flag to ensure someone from the docs team can assist with documenting the initrd changes 17:24:31 I think the doc guys will fix things up a bit after that. 17:24:34 okay 17:25:18 clumens: should that be in MODIFIED? 17:25:30 jlaska: 676551? 17:25:32 oh wait ... patch, but not reviewed 17:25:32 nm 17:25:35 okay, moving on ... 17:25:38 #topic https://bugzilla.redhat.com/show_bug.cgi?id=676032 17:25:38 right. 17:25:39 Bug 676032: unspecified, unspecified, ---, anaconda-maint-list, MODIFIED, Import Error: No module named iutil 17:25:59 pretty straight forward on this one ... 17:26:16 do another alpha TC and you'll grab the fix. 17:26:20 likely impacts several criteria, but I believe this hits the Alpha criteria "The installer must boot (if appropriate) and run on all primary architectures from default live image, DVD, and boot.iso install media " 17:26:36 cool, is this already in the .20 build? 17:26:39 yes 17:26:48 okay ... 17:27:32 proposed #agreed 676032 - accepted as a F15Alpha blocker, will be available in anaconda-15.20 (TC#1) 17:27:43 isn't tc#1 15.19? 17:27:53 I did not encounter this bug when I tested tc1 ( x86_64 ) 17:28:03 I think this is happening when he himself composed a dvd 17:28:04 clumens: yeah 17:28:12 is it already in then? 17:28:19 Viking-Ice: did you go into the bootloader config screen? 17:28:25 * jlaska sees anaconda-15.20-1 in fixed-in field 17:28:32 jlaska: 15.20 is post tc#1, but is built. 17:28:40 right on 17:28:49 clumens: went straight into install 17:28:51 #info Fixed, and awaiting testing against TC#2 17:28:59 Viking-Ice: were you using any updates.img 17:29:00 ? 17:29:00 * dgilmore thinks its a blocker. 17:29:10 * jlaska agrees 17:29:18 it's a blocker if present 17:29:19 +1 blocker 17:29:25 okay, think we have enough ... 17:29:33 #agreed 676032 - accepted as a F15Alpha blocker, will be available in anaconda-15.20 (TC#2) 17:29:38 clumens: thanks, corrected to say TC#2 17:29:54 #topic https://bugzilla.redhat.com/show_bug.cgi?id=671922 17:29:55 Bug 671922: unspecified, unspecified, ---, dlehman, MODIFIED, ValueError: isys.umount() can only umount by mount point 17:30:00 same situation as previous bug. 17:30:26 #info Fixed in anaconda-15.20 and will be available in TC#2 17:30:40 this is the DVD.iso -> USB key use case right? 17:30:47 I don't think we've every fully ironed out whether this is supported or not 17:30:57 brunowolff: bcl? 17:31:06 jlaska: i thought it was advertised in F14 as supported 17:31:24 I dont think custom partitioning falls under alpha criteria 17:31:24 dvd iso on usb? That typically works. 17:31:27 jlaska: comment #5 opens it up a bit too 17:31:33 dgilmore: oh was it ... I'll need to double check. I remember stickster and I updating the docs to avoid recommending USB for anything but Live ISO's 17:31:45 "It's also triggered when testing F15-alpha-tc1 using 17:31:45 repo=nfsiso::." 17:31:52 ah 17:31:53 I hadn't actually looked at this one yet. It's a bit out of my area of expertise. 17:32:19 okay, that _possibly_ falls under the beta criteria "The installer must be able to use the HTTP, FTP and NFS remote package source options " 17:32:28 but definitely the final criteria which covers _all_ installation sources 17:32:41 either way, our good friends in anaconda-devel have a fix ready for testing in the next release 17:32:49 brunowolff: me too! :D 17:32:49 clumens: this is patched in current anaconda? 17:32:53 dgilmore: it is. 17:32:56 This is also with pungi; I mostly play with live spins made with livecd-creator. 17:33:14 then i say its a blocker since we will have the fix 17:33:24 Works for me 17:33:41 proposed #agreed 671922 - Likely impacts Beta release criteria. Already fixed in anaconda-15.20, available in TC#2 for testing. 17:33:49 its probably a beta blocker but since we have a fix i say we accept it 17:33:54 +1 to that 17:33:56 ack 17:34:02 okay, back in about five minutes then. 17:34:06 (picking up lunch) 17:34:17 clumens: thanks,cya 17:34:57 #agreed 671922 - Likely impacts Beta release criteria. Already fixed in anaconda-15.20, available in TC#2 for testing. 17:35:09 I think we had enough +1's before I typed the proposed text 17:35:21 #topic https://bugzilla.redhat.com/show_bug.cgi?id=579838 17:35:22 Bug 579838: medium, low, ---, nickc, ASSIGNED, glibc not compatible with AMD Geode LX 17:35:57 we have this fixed in glibc 17:36:19 According to adamw in the bug ... 17:36:19 This hits "The installer must boot (if appropriate) and run on all primary 17:36:23 architectures from default live image, DVD, and boot.iso install media", IMO, 17:36:26 so is an Alpha blocker. +1 17:36:32 +1 17:36:37 +1 17:36:44 dgilmore: is this in a newer glibc build? 17:36:51 (or binutils) 17:37:03 jlaska: i built the glibc before kicking off the mass rebuild 17:37:09 jlaska: glibc 17:37:14 dgilmore: okay ... should we move this to modified? 17:37:26 with a fixed in like 'glibc-2.13.90-3' ? 17:38:02 Would be nice to know how many users have AMD Geode LX 17:38:06 jlaska: glibc-2.13.90-2 17:38:13 jlaska: every XO 17:38:17 right 17:38:35 outside of that probably only some terminal servers 17:38:36 dgilmore: aren't the newer XOs Via or ARM based? 17:38:36 It's already fixed it sounds, so that's good 17:38:38 wasn't this an issue in f14 as well? 17:38:44 rbergeron: looks to be 17:38:57 tflink: there are via based ones, the arm based ones are still being developed 17:38:59 not that the older ones aren't important 17:39:12 I'm not 100% clear how XO bugs would impact the criteria, but we can go with this for the Alpha 17:39:27 tflink: there are a couple of million xo-1.0's i believe 17:39:37 back. 17:39:39 not to say XO bugs aren't important, just not clear how bugs affecting derived distros should be reflected in Fedora release criteria 17:40:01 We do claim to support the processor they use. 17:40:04 jlaska: its the baseline supported hardware 17:40:17 oh, I didn't know that 17:40:41 * jlaska notes ... I'm not arguing against taking this ... just not clear which criteria it would directly impact other than what adamw listed 17:40:58 jlaska: its the minimum hardware we support, at least thats what we said when going from i586 to i686 17:41:03 dgilmore: would you mind moving this to MODIFIED and updating fixed_in appropriately? 17:41:08 jlaska: sure 17:41:17 dgilmore: oh okay ... that'll be a good link/reference to add to the criteria pages 17:42:08 proposed #agreed 579838 - accepted as Alpha blocker as this impacts all XO's and is already fixed 17:42:30 ack/nack/patch? 17:42:33 ack 17:42:35 ack 17:42:35 ACK 17:42:41 ack 17:42:44 jlaska: http://fedoraproject.org/wiki/Features/F12X86Support thats where we state it 17:42:57 dgilmore: awesome, thanks ... I'll queue this for absorbtion after the meeting 17:43:03 #link http://fedoraproject.org/wiki/Features/F12X86Support 17:43:08 #agreed 579838 - accepted as Alpha blocker as this impacts all XO's and is already fixed 17:43:33 #topic https://bugzilla.redhat.com/show_bug.cgi?id=676485 17:43:35 Bug 676485: unspecified, unspecified, ---, mbarnes, NEW, repoclosure fails on 15-Alpha.TC1 17:43:55 this is a repoclosure bug which I believe we have covered in the Alpha criteria ... 17:44:00 "There must be no file conflicts (cases where the files in some packages conflict but the packages have explicit Conflicts: tags are acceptable) or unresolved package dependencies during a media-based (CD/DVD) install " 17:50:42 gnome-pilot still had conflicts just before the branch. 17:50:43 I am still getting my F15 repo sync'd up, so don't know for sure if it is fixed yet. 17:50:43 there was half a dozen or so packages i blocked today 17:50:43 i dont know if that will fix this 17:50:43 we have had issues with mash failing 17:50:43 so there has been no rawhide for a few days 17:50:43 and branched compose is still waiting on packages to be signed 17:50:43 i agree its a blocker 17:50:43 but we can know just yet if its fixed or not 17:50:43 s/can/can't/ 17:50:45 dead air alarm! 17:50:45 I am seeing some ping timeouts now. 17:50:45 hrrm 17:50:45 netsplit coming? 17:50:46 yeahh 17:51:31 Certainly looks like a blocker to me 17:51:32 and the gnome-pilot package is accessible through the 'customize now' package set, so this seems to fit the mold 17:51:32 okay ... /me preps proposed stmt ... 17:51:33 well ... should we pull in mbarnes for thoughts on how to appropriately fix this 17:51:33 since I think this is related to the GNOME3 and related panel library changes 17:51:33 * jlaska doesn't see him online 17:51:33 remove the package is probably the fix 17:51:33 definitely another option for the alpha 17:51:33 #info Recommend to resolve the dependency problem, or remove 'gnome-pilot' from comps for F15Alpha 17:51:34 proposed #agreed 676485 - accepted as F15Alpha blocker 17:51:34 I think the desktop sig should decide basically this one if we want to ship by default legacy apps that is.. 17:51:34 yeah 17:51:34 anyone from #desktop lurking? 17:51:34 * jlaska invites mclasen 17:51:34 tflink has been cloned! 17:51:35 :) 17:51:35 * tflink_ hates his DSL modem with a passion 17:51:35 as is this it's a blocker 17:51:35 s/it's/is 17:51:36 okay, I think we've got enough ack's 17:51:36 so ack from me 17:51:36 well, no objections at least :) 17:51:36 #agreed 676485 - accepted as F15Alpha blocker. Work with desktop SIG to identify how to proceed for Alpha 17:51:37 #topic https://bugzilla.redhat.com/show_bug.cgi?id=670379 17:51:38 Adam and I are in agreement here, I think this qualifies as a Alpha blocker 17:51:38 * jlaska locating impacted criteria ... 17:51:38 yup it's an blocker 17:51:38 +1 to blocker 17:51:38 "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 " 17:51:38 btw RemainAfterExit=yes will fix the reported but not the underlying problem 17:51:38 and also ... 17:51:38 "It must be possible to run the default web browser and a terminal application from the default desktop environment. The web browser must be able to download files, load extensions, and log into FAS " 17:51:38 Bug 670379: medium, low, ---, mgracik, ASSIGNED, Unknown lvalue 'ValidNoProcess' in section 'Service'. 17:51:42 wow 17:52:06 ouch 17:52:12 hey jlaska! 17:52:22 so I'm hearing agreement that #topic is an Alpha blocker 17:52:32 i just saw like 10 minutes of meeting float by in 10 seconds :( 17:52:38 yup me too 17:52:43 Viking-Ice: have you confirmed that using RemainAfterExit=yes resolves the issue? 17:52:54 clumens: bcl: do you know when mgracik returns? 17:52:56 it will resolve the systemd error but not the issue 17:53:15 as in firstboot will still fail to start 17:53:19 okay 17:53:38 I'm sure mgracik will be able to handle this one just fine ... but he's on PTO at the moment 17:53:41 iirc 17:53:43 jlaska: i think he'll be back on monday 17:53:52 okay 17:53:59 * jlaska checks calendar 17:54:05 my gut says it's the X detection code snippets 17:54:33 Viking-Ice: so not firstboots fault, but something xorg* related? 17:54:34 yes we've all read the bug 17:54:48 okay, that'll give us time before the RC is spun next Thu 17:55:06 dgilmore: when do you need all RC content in order to start your RC1 spin next week? 17:55:22 anyway ack for it being a blocker from me.. 17:55:23 jlaska: monday or tuesday 17:55:48 dgilmore: okay, so that will make it tight for this issue ... I could see this potentially introducing some slippiness into the schedule 17:56:06 jlaska: Is 'slippiness' the technical term? 17:56:14 yes, industry term, if you will 17:56:15 :) 17:56:24 although, I don't want to guess which industry 17:56:30 anyway 17:56:38 Sounds like something from a fish packing plant :-/ 17:56:45 jlaska: i think we have a small amount of flexibility there 17:56:47 lol 17:56:57 jsmith: or the oil industry 17:57:04 rbergeron: You've obviously never worked in a fish packing plant 17:57:15 #agreed 670379 - accepted as F15Alpha release blocker as this impacts ability login as non-root user and also hits Alpha desktop criteria 17:57:28 #action mgracik - start off the week battling firstboot + systemd integration 17:57:43 perhaps the fish oil industry? 17:57:45 lucky 17:58:18 5 more bugs ... let's keep rolling ... 17:58:24 5 more proposed Alpha blockers that is ... 17:58:26 #topic https://bugzilla.redhat.com/show_bug.cgi?id=674978 17:58:27 Bug 674978: high, unspecified, ---, rstrode, NEW, GDM in autologon error loop 17:58:55 I think this hits ... "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 " 17:58:57 I dont think autologon qualifies as an alpha blocker 17:59:02 * dgilmore thinks its a blocker 17:59:06 it is if it's enabled by default on all Live images 17:59:08 makes live media untestable 17:59:15 users can still click the liveuser and login 17:59:40 Viking-Ice: i think in this case they can't 17:59:45 we have a clause in the criteria that might apply here stating "without user intervention" 17:59:46 you can't click anything 17:59:49 I neer hit this bug 17:59:59 I never hit this bug 18:00:00 yeah, I think the login keeps cycling here 18:00:00 and you can't get to a console, at least in a virt. 18:00:02 at least that's what i experienced. you can't click anything 18:00:10 yup yup 18:00:15 the 2/7 nightly has this bug 18:00:17 jlaska: o a blocker 18:00:22 so a blocker 18:00:31 alright, +1 from me+dgilmore 18:00:33 other votes? 18:00:41 refer to criteria listed above 18:00:42 throw in a neutral here 18:00:43 +1 blocker 18:00:50 +0 from Viking-Ice 18:00:55 I have seen this on test spins I have built. 18:01:03 okay, I think we've got enough for Alpha ... 18:01:11 I am a bit distracted at work for a few minutes. 18:01:21 brunowolff: okay, thanks for heads up 18:01:38 i think it should be fixed in alpha as this essentially makes the desktop live unusable 18:01:52 I might have repsoned about the wrong gdm bug, like i said I am a bit distracted here, 18:01:58 #agreed 674978 - accepted as a F14Alpha blocker, impacts logging into desktop on all live images 18:02:10 but i'm have no idea on whether i'm allowed to vote on anything here :D 18:02:34 heffer: If you care enough to attend the meeting, you have a vote :-) 18:02:42 :) 18:03:06 mclasen: hi there ... we've moved on to another bug now, but I've linked to the bug in question on #fedora-devel 18:03:34 Anyone want to check-in with halfline after the meeting on this bug? 18:03:51 jlaska: I'll have a look 18:04:06 halfline is out sick, though 18:04:18 oh no, plague is circulating in Westford 18:04:34 * mclasen stayed home as a defensive measure 18:04:38 good choice 18:04:46 anyone else who might be able to assist with gdm issues? 18:05:15 mclasen: I may have missed it ... wasn't sure if you were volunteering for this bug 18:05:19 depends on the issue; halfline is certainly the most familiar with recent changes 18:05:38 jlaska: volunteering will amount to just trying to get gnome-pilot to build against current deps 18:05:53 mclasen: oh for the gnome-pilot one, great thanks! 18:06:11 okay ... let's circle back with halfline on Monday to get his input on #topic bug 18:06:28 #info halfline under the weather, check-in with him early next week for guidance on resolving 674978 18:06:35 next up ... 18:06:36 #topic https://bugzilla.redhat.com/show_bug.cgi?id=673921 18:06:37 Bug 673921: medium, unspecified, ---, kaboom, NEW, cannot show user names on the graphical login screen 18:06:37 i'll try to reproduce that one, too 18:06:45 but yeah,might have to wait for halfline 18:06:58 * mclasen still one bug behind... 18:07:18 mclasen: sorry, I'm trying to move fast through the bugs ... in the interest of meeting participant sanity (and mine) 18:07:19 I've come across this one and a failed login from other ( or succesful login and logout ) will get user listed in the gdm list 18:07:25 I seem to be getting a variant of this bug 18:07:28 me too 18:07:32 I get no usernames every *other* login 18:07:36 I added this to the list for consideration 18:07:38 it does seem transient 18:07:53 if it happened *every* time, I think it would fall under: 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:07:59 users still can login via their regular username by typing it in the other feeled 18:08:12 field 18:08:13 * dgilmore thinks this is not a blocker 18:08:13 I mean 18:08:18 they can log in 18:08:20 that seems like a reasonable workaroudn 18:08:21 yeah 18:08:21 not a blocker from me 18:08:29 Yeah... I'd certainly nominate it as a Beta blocker, but is ambivalent about calling it an Alpha blocker 18:08:36 s/but is/but I'm/ 18:08:44 I've seen no usernames on GDM after reboot, but assumed it was the other X issues that I was seeing. it wasn't every time either 18:08:50 * mclasen is fairly sure that is fixed in current gdm 18:09:00 oh ... well that would be good 18:09:09 once the branched repo starts flowing, this might fix itself then? 18:09:28 mclasen: how recent gdm 18:09:40 newer than this morning updates 18:09:46 this might even be fixed in tc2 18:09:46 if so maybe if not no 18:09:49 ok 18:10:00 but not a blocker from me 18:10:01 Viking-Ice: there has been no updates in 3 days 18:10:16 I'm pulling stuff from koji repo 18:10:41 so I pull all the rebuilds :) 18:10:44 Viking-Ice: ok 18:11:07 proposed #agreed 673921 - not accepted as a F15Alpha blocker. Reasonable workaround of typing in username exists 18:11:20 Viking-Ice: no, not newer than this morning 18:11:27 then still present 18:11:33 tangent ... dgilmore, how does one go from rawhide to branched ... update to a branched fedora-release package? 18:11:48 Viking-Ice: can you add that comment to the bug, along with the versions tested? 18:11:58 ok 18:13:17 don't think I hear any objections to the proposed .. 18:13:33 ack on not alpha blocker 18:14:17 * rbergeron nods 18:14:37 #agreed 673921 - not accepted as a F15Alpha blocker. Reasonable workaround of typing in username exists 18:15:04 rbergeron: could you mind moving this to F15Beta as well? 18:15:11 s/could/would/ 18:15:34 jlaska: enabling fedora repo and disabling rawhide should do iy 18:16:10 dgilmore: thanks 18:16:16 okay, moving on ... 18:16:20 #topic https://bugzilla.redhat.com/show_bug.cgi?id=675509 18:16:21 Bug 675509: unspecified, unspecified, ---, sandmann, NEW, default cursor theme should not depend on used desktop environment 18:16:57 not a blocker 18:16:59 This doesn't seem like an alpha blocker. 18:17:07 agreed, I don't believe we have criteria for this 18:17:22 agreed, doesn't seem like an alpha blocker 18:17:27 rdieter and adamw support -1 to Alpha blocker on this as well 18:17:44 this dependency preferable should be fixed before final 18:17:50 * jlaska adds CommonBugs keyword 18:18:11 I don't even know what criteria this would fit under 18:18:16 nice to have 18:18:16 (for Final) 18:18:21 yeah, certainly nice-to-have 18:18:22 nice to have 18:18:27 fixed 18:18:31 for Alpha, Beta, Final? 18:18:35 final 18:18:37 proposed #agreed 675509 (Meeting topic: F-15-Alpha Blocker Bug Review) 18:18:42 ergh ... one sec. 18:19:22 id like to see something better for beta 18:19:28 but not a alpha blocker 18:19:54 proposed #agreed 675509 - Rejected as F15Alpha blocker, appears more of a polish issue, than a core functionality problem. Accepted as F15Beta-accepted (Nice to have) 18:20:10 I don think we consider weird package dependancy blocker of any kind 18:20:22 if we did we would never release 18:20:31 package dependency conflicts on the ISO media are part of the criteria 18:20:35 Viking-Ice: right, if it never gets fixed we would live 18:20:39 its just nice to have 18:20:51 right, we'll take a fix if it's non-invasive and ready in time 18:20:51 yup nice to have fixed 18:21:03 any objections to #agreed 18:21:26 none 18:21:48 #agreed 675509 - Rejected as F15Alpha blocker, appears more of a polish issue, than a core functionality problem. Accepted as F15Beta-accepted (Nice to have) 18:22:10 rbergeron: if you're playing the home game, we can move this to blocks: F15Beta-accepted. Otherwise I'll grab it post-meeting 18:22:21 #topic https://bugzilla.redhat.com/show_bug.cgi?id=672265 18:22:22 Bug 672265: high, medium, ---, mclasen, NEW, "Install to harddrive" fails with "not a live image" 18:22:29 blocker 18:22:43 agreed 18:22:45 from adamw ... 18:22:47 +1 blocker, hits the intersection of "The installer must boot (if appropriate) 18:22:49 jlaska: i am just going to go through the full list post-meeting, now that i have my awesome privs. :) 18:22:50 and run on all primary architectures from default live image, DVD, and boot.iso 18:22:51 I am past the distracted phase of what i was doing at work. 18:22:53 install media" and "In most cases, the installed system must boot to a 18:22:56 functional graphical environment without user intervention (see 18:22:58 Blocker_Bug_FAQ)" (implication of the criteria is clearly that live install 18:23:02 should be possible at Alpha stage). 18:23:02 brunowolff: welcome back :) 18:23:06 I suspect there may really be two separate problems here. 18:23:14 rbergeron: okay, I'll be happy to work the list in the opposite direction and we can meet in the middle 18:23:22 brunowolff: go ahead ... 18:23:31 jlaska: sounds good 18:23:37 * dgilmore is good with this being a blocker 18:23:49 mclasen: how'd this get assigned to you? 18:23:52 Sometimes osmin.img is corrupted and sometimes it is OK, but the same result in the end happens either way. 18:24:02 what the heck is the "LiveCD" component in bugzilla? 18:24:10 should this be livecd-tools? 18:24:17 jlaska: si sehnor 18:24:20 jlaska: I assigned it to LiveCD since it seemed to be at a higher level than livecd-tools and device-mapper didn't want it :) 18:24:21 okay 18:24:30 jlaska: I am the unlucky owner of 'LiveCD' 18:24:34 bcl: aah, I see ... something different is lurking 18:24:36 its a honeypot 18:24:37 I think we may need some help from dracut people as well. 18:24:42 sorry gang, I didn't know what that component was 18:24:55 jlaska: id never heard of it before now 18:24:56 26 users on the cc list ... wow, certainly a popular one 18:24:57 (which may not be right, I'm not sure who owns the whole livecd idea) 18:25:04 I am not sure enough about how osmin gets used to to testing to further isolate the problem. 18:25:23 brunowolff: so in all cases, we are failing to install to hard disk when running in live image? 18:25:34 yup 18:25:44 hence it's a blocker 18:25:49 The osmin.img corruption is also odd. I haven't seen squashfs.img corruption on any tests. 18:25:59 Viking-Ice: it hasn't been accepted yet 18:26:07 that's why it's on #topic 18:26:31 Yes, install to hard drive doesn't work whether or not osmin.img is corrupted (as in not being a valid squashsfs image). 18:26:47 proposed #agreed 672265 - Accepted as F15Alpha blocker, impacts *all* live image installs. 18:26:51 ack/nack/patch? 18:26:53 is the corruption due to the change to xz? 18:26:58 ack 18:27:01 ack 18:27:03 ack 18:27:09 that's enough for me ... 18:27:11 #agreed 672265 - Accepted as F15Alpha blocker, impacts *all* live image installs. 18:27:24 There is also some problem with the osmin cow image embedded in the osmin.img squashfs image. 18:27:30 okay ... how do we make progress on this issue ... who owns it? 18:27:34 mclasen: brunowolff: bcl ? 18:27:54 or who do we need input from 18:28:00 I think livecd tools owns it, but I don't have the ability to fix this in a timely matter. 18:28:31 I've tried to sort it out and got stuck. 18:28:40 fun 18:28:52 I was hoping LiveCD would have a better idea of how osmin is used. 18:28:56 I think we really need to split this in two parts. 18:29:07 brunowolff: what's your recommendation? 18:29:23 Someone needs to find out why osmin.img sometimes gets corrupted, and someone else needs to 18:29:35 look at what's going on with the cow image. 18:29:40 is there a ticket on that part? 18:29:46 bz 18:29:49 brunowolff: are both considered Alpha issues? 18:29:50 There may possibly be some underlying common cause. 18:30:20 I would think so, but I wouldn't hold up the alpha indefinitely if we can't get them resolved. 18:30:27 brunowolff: if you have a moment, can you file another bz to track your thoughts on the other issue, perhaps linking it as a dep of #topic? 18:31:03 Yes. 18:31:06 mclasen: any thoughts on what else we might need to move this forward? 18:31:21 brunowolff: awesome thank you ... I'd certainly not have enough info to file a meaningful report on this 18:32:16 #action brunowolff cloning a new bug from 672265 to handle a potential second, but related, problem affecting the cow image 18:32:40 I'd like to move on to the next issue, but it seems like we are blocked on how best to proceed with resolving the issue 18:32:56 any thoughts/recommendations/three_wishes? 18:33:26 i wonder if we should revert the change to xz and see if it magically works 18:33:27 Should I move the component to livecd-tools? 18:33:36 brunowolff: probably 18:33:59 OK, I move both bugs to livecd-tools. 18:33:59 brunowolff: I think bcl (who owns livecd-tools) felt this might be caused by something else 18:34:01 at least to rule out the change of compression used as a culprit 18:34:21 dgilmore: where would that revert happen, livecd-tools? 18:34:34 I can do some test builds this weekend using gzip. 18:34:35 jlaska: thats where it was added i believe 18:34:40 okay 18:35:02 do we have an idea as to when it broke? 18:35:04 #help 672265 could use some extra eyes to determine what might be causing this issue (possibly introduction of xz compression) 18:35:07 It's also possible we have triggered a squashfs 4.2 bug that affects osmin.img, but not squashfs.img. 18:35:30 It was broken before the xz change. 18:35:36 ah 18:35:38 bcl: ok 18:35:44 I don't know when it broke, as I don't do installs from live images. So it could have been a long time as far as I know. 18:35:47 well im done pulling at straws 18:36:02 If we found out that might suggest some other places to look. 18:36:23 how many potential blocker bugs do we have left ? 18:36:39 Viking-Ice: 1 after this 18:36:43 i think we can all agree that this is a blocker 18:36:53 yup, I listed that aboev 18:36:53 and that we can move on to the next bug 18:37:00 was hoping to clarify who had the ball on this issue 18:37:13 jlaska: i guess bcl, and brunowolff 18:37:26 okay 18:37:29 we can let them pull in what they need to 18:37:40 what and who 18:37:49 yeah, I'll keep chipping away at it as well 18:37:54 bcl: brunowolff: feel free to raise the pantscon level 18:38:03 ... as needed 18:38:06 I am not sure how to do that? 18:38:12 me neither! 18:38:26 brunowolff: sorry, old joke from adamw re: DEFCon alert level 18:38:34 okay ... last one ... 18:38:36 #topic https://bugzilla.redhat.com/show_bug.cgi?id=673907 18:38:38 Bug 673907: unspecified, unspecified, ---, mgracik, MODIFIED, Install from DVD fails: /var/run/dbus/system_bus_socket is missing 18:38:51 brunowolff: If you need help getting general attention to an issue, I can help raise a ruckus! 18:39:00 brunowolff: related to a bug that could cause a pants crapping moment ... e.g. pantscon 18:39:27 good news on this bug 18:39:46 clearly a blocker, since I think this was impacting all installs I _think_ 18:39:48 OK. I'd really like a DM person to at least look at the case where osmin.img file looks OK, but osmin has a problem anyway. 18:39:59 +1 on being a blocker from me 18:40:14 +1 from me 18:40:16 i think its likely a blocker 18:40:25 but i think the proposed fix is wrong 18:40:29 and it's already fixed in lorax I believe 18:40:47 dgilmore: Care to elaborate (either here or in the bug itself?) 18:41:18 It's Friday hence I need run to the *milk store* before it close which is eta in 20 minutes.... 18:41:22 catch you later.. 18:41:24 Viking-Ice: okay ... thanks for your help in the meeting 18:41:37 jsmith: if dbus is needing /var/run/dbus/ to exist. it should be providing it 18:41:43 well, I think we can easily accept this and add #info's for anyhting else 18:41:46 dgilmore: it wasn't needed iirc 18:42:18 or wait, I'm thinking of a previous lorax bug .. nm 18:42:30 jlaska: is dbus creating the dir in the initscript startup? 18:43:12 dgilmore: sorry, I don't know ... mgracik might know more 18:43:30 jlaska: yeah. i just dont see how its a lorax bug 18:44:02 i know a thing or two about lorax. let me look. 18:44:23 #agreed 673907 accepted as F15Alpha blocker as this impacts all installs 18:45:05 I think it's already fixed anyway, right? 18:45:33 * jlaska waits a moment for clumens input 18:45:42 we have 1 proposed nice-to-have bug after this 18:45:50 and then I think we can call it quits for our first meeting 18:46:05 we'll review the CLOSED but non VERIFIED bugs for the next meeting (post-branch) 18:46:21 clumens: to me it looks like a packaging bug in dbus that buildinstall worked around, so a workaround has been added to lorax 18:46:41 dgilmore: dbus on my computer at least owns /var/run/dbus 18:47:25 someone want to add a comment + needinfo for mgracik in the bz? 18:47:27 or should we move on 18:47:47 you can move on 18:48:18 clumens: %ghost %dir %{_localstatedir}/run/dbus 18:48:43 anyway 18:48:44 ah 18:49:02 #info clumens and dgilmore reviewing whether an additional/different fix is required 18:49:40 alright ... that's it for BLOCKERS 18:49:46 now 1 proposed NICE-TO-HAVE 18:49:53 #topic https://bugzilla.redhat.com/show_bug.cgi?id=669037 18:49:54 Bug 669037: high, low, ---, bnocera, NEW, [abrt] gnome-settings-daemon-2.91.8-1.fc15: Process /usr/libexec/gnome-settings-daemon was killed by signal 11 (SIGSEGV) 18:50:25 for those enjoying the home game, nice-to-have bugs are decribed in detail here ... https://fedoraproject.org/wiki/QA:SOP_nth_bug_process 18:50:34 #info Nice-To-Have bug process - https://fedoraproject.org/wiki/QA:SOP_nth_bug_process 18:50:51 "In general, nice-to-have bugs are usually bugs for which an update is not an optimal solution, and for which the fix is reasonably small and testable (this consideration becomes progressively more important as a release nears, so bugs may be downgraded from nice-to-have status late in the release process if it transpires that the fix is complex and hard to test). " 18:51:24 +1 for a nice-to-have 18:51:27 * jlaska looking for mcepl 18:52:01 "Crash happened while I was using abrt-gui to report a previous 18:52:02 gnome-settings-daemon crash!" 18:52:10 "Plugged in a removable drive, it auto-mounted, g-s-d crashed" 18:52:58 mclasen: does this ring any bells from upstream GNOME3? 18:53:40 jlaska: FWIW, I'm no longer seeing those crashes on the latest packages 18:53:45 jlaska: It may have already been fixed 18:53:52 "Automatic mounting on insertion of 18:53:52 removable 18:53:53 media must work in the default desktop environment " 18:53:57 ^^^ Beta release criteria 18:54:07 jsmith: okay, that's good to know 18:54:25 jsmith: do you recall if your reproducer involved removable media? 18:55:17 proposed #agreed 669037 - Accepted as Alpha NICE-TO-HAVE (F15Alpha-accepted) 18:55:36 I feel like I'd need to know more about what's causing it... the reproducers seem to be all over the palce 18:55:39 place 18:55:40 ack/nack/patch? 18:55:52 ack 18:55:57 would be nice to have 18:56:33 that's 3 nice-to-haves 18:56:55 I'll defer to adamw on his other idea for also moving this to F15Blocker 18:56:59 * jlaska needs more info on the reproducers 18:57:03 #agreed 669037 - Accepted as Alpha NICE-TO-HAVE (F15Alpha-accepted) 18:57:29 #info potentially consider for F15Beta blocker since this *may* impact insertion/removal of removable media 18:57:39 #topic Open discussion - 18:57:54 okay folks ... congrats, that's it for the proposed BLOCKER and NICE-TO-HAVE bugs 18:58:10 we agreed to also review CLOSED but not VERIFIED blocker bugs 18:58:24 but since we're just now accepting blockers, I'll leave that as a task for after this meeting 18:58:41 if there aren't any bugs you'd like to propose, we'll close this meeting in 2 minutes 18:58:44 * jlaska sets fuse 18:59:28 thansk jlaska 18:59:45 1 minute until #endmeeting ... 18:59:56 dgilmore: thank you, and everyone else who participated 19:00:03 very helpful having active participants in these meetings 19:00:13 rbergeron: thanks for your help with the bug changes 19:00:18 hugs all around everyone! 19:00:35 10 seconds till #endmeeting ... 19:00:44 time! 19:00:47 #endmeeting