16:00:15 #startmeeting Fedora 14 Alpha Blocker Meeting 16:00:15 Meeting started Fri Jul 30 16:00:15 2010 UTC. The chair is poelcat. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:15 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:00:33 #meetingname blocker-review 16:00:33 The meeting name has been set to 'blocker-review' 16:00:41 who is in the house? 16:01:12 * adamw is in the residence 16:01:15 * cyberpear lurks 16:01:24 * fcami lurks behind cyberpear 16:01:33 jlaska: around? 16:02:55 #info attendees adamw cyberpear fcami poelcat 16:02:55 nirik: how bout you? I have a feeling we'll need you for live cd stuff 16:03:05 I'm sorta here. ;) 16:03:11 #info attendees adamw cyberpear fcami poelcat nirik 16:03:27 #chair adamw cyberpear fcami nirik 16:03:27 Current chairs: adamw cyberpear fcami nirik poelcat 16:03:43 * satellit__ lurks 16:03:47 let's start with something easy... 16:03:57 #topic https://bugzilla.redhat.com/show_bug.cgi?id=597858 16:03:58 Bug 597858: high, high, ---, gecko-bugs-nobody, NEW, "SELinux is preventing firefox from making its memory writable and executable." crashes rawhide firefox start 16:04:07 such a fun bug. 16:04:13 per fedora-devel we're waiting for upstream and fesco 16:04:21 not much else to discuss for today? 16:04:45 should we add a note in the bug that we need a decision by Tuesday? 16:04:57 sure, if you like... 16:05:16 sounds good to me 16:05:33 * poelcat trying to remain cognizant of RC compose on Thurs 16:05:58 #action we're waiting for upstream and fesco + add a note in the bug that we need a decision by Tuesday to compose RC on time on Thurs 16:06:10 #action we're waiting for upstream and fesco + add a note in the bug that we need a decision by Tuesday to compose RC on time on Thurs https://bugzilla.redhat.com/show_bug.cgi?id=597858 16:06:11 Bug 597858: high, high, ---, gecko-bugs-nobody, NEW, "SELinux is preventing firefox from making its memory writable and executable." crashes rawhide firefox start 16:06:31 could we get a volunteer or two to update the bugs as we go? 16:06:37 yo 16:06:42 no special technical knowledge required 16:07:05 I can help if needed 16:07:13 thanks adamw fcami 16:07:14 or do it if adamw has * else to do 16:07:19 #topic https://bugzilla.redhat.com/show_bug.cgi?id=615443 16:07:20 Bug 615443: high, high, ---, dhuff, NEW, booting live images from nightly fails (can't mount root filesystem) 16:07:41 nirik: i think you may know best about the livecd issues? 16:07:57 There is some discussion in the dependent bug 619020. 16:07:58 Bug https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=619020 medium, high, ---, kmcmartin, ASSIGNED, dumpe2fs says Journal superblock magic number invalid! Ext4 filesystem from compose host's livecds 16:08:28 we should invite sandeen 16:08:28 maybe 16:08:30 yeah, it's looking like suashfs now. 16:08:35 squashfs. 16:08:48 So, it's being investigated more by the squashfs maintainer. 16:08:59 * adamw asked sandeen 16:09:03 But it is still odd that the symptoms didn't start until well after squashfs was updated and 16:09:03 anything else for us to discuss here today? 16:09:08 it's a very wacky one. 16:09:11 that it only happens on some systems. 16:09:33 Also, I am going to work with mmgrath later today to see about getting a kvm spin02 box to see if this issue is xen related. 16:09:39 It happens on the compose machine pretty much all of the time. I haven' gotten it to occur yet. 16:09:46 http://wiki.sugarlabs.org/go/Talk:Features/Soas_V4/Install_Test_Table#Test_results tests for soas 16:10:35 nirik: didn't i hit the same issue on a build i did on my own local system? 16:10:37 As another sticking point I am going to a game convention starting Sunday night and may not have good access for a week. 16:11:10 adamw: you might have... it's hard to collect the all the data we have gathered. 16:11:20 nirik: ah, i think this is an earlier failure than the one i saw 16:11:20 if someone can reproduce it on non xen that would be good, then I can rule that out. 16:11:22 Lougher expressed some interest in looking at it in 619020 comments. 16:11:36 also, it's unclear if it might be a x86_64 only issue. 16:11:40 it's probably worth putting the deadline in both bugs 16:12:11 Does the 4.0 version of squashfs work on the compose machine? 16:13:13 brunowolff: I don't know. I can try that if you like... 16:13:14 Do we having the option of composing using 4.0 on the compose machine while keeping 4.1 in rawhide to help testing? 16:13:21 sure. 16:13:30 should https://bugzilla.redhat.com/show_bug.cgi?id=619020 be added to blocker too? 16:13:30 althought thats nasty because it's confusing, IMHO. 16:13:31 Bug 619020: medium, high, ---, kmcmartin, ASSIGNED, dumpe2fs says Journal superblock magic number invalid! Ext4 filesystem from compose host's livecds 16:13:37 I'd rather not do an epoch bump. 16:13:47 brunowolff: I can try 4.0 this morning. 16:14:04 619020 should already be one by dependency. 16:14:24 * poelcat still afraid it might get lost 16:14:49 The 2.6.35 kernel has xattr support for squashfs so we kind of want 4.1 squashfs even if we don't do much with lzma. 16:15:05 brunowolff: any harm in adding f14alpha to it? 16:15:15 but that might be where the bug is... hard to say. 16:15:16 I don't think so. 16:15:50 can someone summarize the #action for 615443 ? 16:16:02 I am going to test build a squashfs img while the ext3 image is loop mounted and see if that triggers any issue. 16:16:06 if 615443 depends on 619020 that's fine, it makes 619020 implicitly a blocker. when we look at the f14alpha dependency tree we'll see it. 16:16:36 poelcat: I will test older squashfs. squashfs maintainer will investigate further with e2fstools maintainer helping. 16:17:00 wait. 16:17:05 I'd like to see 4.0 tested on the build machine with the idea that we can do composes there using it that will work for the 16:17:14 do we have a f14 branch published yet to compose off? 16:17:23 alpha release without rolling back squashfs tools. 16:17:23 #chair nirik 16:17:23 Current chairs: adamw cyberpear fcami nirik poelcat 16:17:30 #chair brunowolff 16:17:30 Current chairs: adamw brunowolff cyberpear fcami nirik poelcat 16:17:56 nirik: i believe jesse sent the branch announcement 16:18:09 adamw: nirik yes, he did 16:18:09 We need to continue trying to find what triggers the bug. 16:18:12 Subject: Fedora 14 has been branched! 16:18:12 Date: Thu, 29 Jul 2010 21:03:49 -0700 16:18:13 yes, but there is no f14-branched composes/mirrored yet 16:18:17 ah 16:18:24 hopefully later today I guess. 16:19:32 oxf: ^^^? 16:19:35 ah, not around 16:19:41 so... proposed #action: test older squashfs. squashfs maintainer will investigate further with e2fstools maintainer helping + add reminder to bugs that this must be resolved by Tuesday ACK/NAK ? 16:19:49 ACK 16:19:50 ack 16:19:51 ACK 16:20:13 #action: test older squashfs. squashfs maintainer will investigate further with e2fstools maintainer helping + add reminder to bugs that this must be resolved by Tuesday https://bugzilla.redhat.com/show_bug.cgi?id=615443 16:20:14 Bug 615443: high, high, ---, dhuff, NEW, booting live images from nightly fails (can't mount root filesystem) 16:20:16 ack, but note I will be in a car all day Monday and note available. 16:20:27 #action test older squashfs. squashfs maintainer will investigate further with e2fstools maintainer helping + add reminder to bugs that this must be resolved by Tuesday https://bugzilla.redhat.com/show_bug.cgi?id=615443 16:20:28 Bug 615443: high, high, ---, dhuff, NEW, booting live images from nightly fails (can't mount root filesystem) 16:20:46 same action for dependent bug? 16:21:07 I think, yes 16:21:25 #topic https://bugzilla.redhat.com/show_bug.cgi?id=619020 16:21:26 Bug 619020: medium, high, ---, kmcmartin, ASSIGNED, dumpe2fs says Journal superblock magic number invalid! Ext4 filesystem from compose host's livecds 16:21:27 If we have a work around for builds, we may not need the bug actually fixed by Tuesday. 16:21:34 that, too 16:21:43 tried to capture that in the comment 16:22:01 #action test older squashfs. squashfs maintainer will investigate further with e2fstools maintainer helping + add reminder to bugs that this must be resolved by Tuesday unless there is a work around for builds https://bugzilla.redhat.com/show_bug.cgi?id=619020 16:22:02 Bug 619020: medium, high, ---, kmcmartin, ASSIGNED, dumpe2fs says Journal superblock magic number invalid! Ext4 filesystem from compose host's livecds 16:22:15 #topic https://bugzilla.redhat.com/show_bug.cgi?id=618504 16:22:16 Bug 618504: medium, low, ---, enrico.scholz, NEW, Can not submit abrt bugs 16:22:42 Also note that Kyle hasn't been heavily involved with this. It's really been my work to try to get ready for lzma. 16:22:59 Perhaps I should change the assignment field to myself? 16:23:14 brunowolff: that would be great... then I won't nag the wrong person :) 16:23:38 for 618504 we haven't set as accepted blocker or not 16:23:45 I do it on both, since I am a comaintainer for both livecd-tools and squashfs-tools. 16:23:56 without abrt, some qa stuff might be difficult to do 16:24:13 we need that fixed before we start the test sessions 16:24:19 not necessarily before compose 16:24:20 well, according to the specific criteria, it's not a bug. we can argue it's a high severity issue in a critpath package (I think we made abrt critpath), but i think it probably isn't, since abrt works and generates reports which could be submitted later once the bug's fixed. 16:24:40 hmm, ok 16:24:45 oh, no, it's not critpath either. 16:24:55 k, not blocker from me then 16:25:11 so under the criteria, we really can't make it a blocker. we should probably have specific criteria about abrt and sealert, though, i'll have to draft some for the list. 16:25:48 adamw so you believe it should be an alpha blocker, we just don't have criteria that covers it presently? 16:25:54 in this case, no 16:26:03 ah, okay 16:26:15 the criterion i'd propose would be that any automated bug reporting tool intended to be present must be present and able to generate reports, i think 16:26:28 (at alpha stage) 16:26:39 is there anyone present that believes 618504 should remain an f14 alpha blocker? 16:26:43 actually submitting them isn't quite so vital 16:26:46 adamw: sounds good 16:26:47 that's probably beta or final 16:28:20 proposed #action this bug does not qualify as a release blocker under the release criteria. remove f14alpha block ACK/NAK? 16:28:30 ack 16:28:30 ack 16:28:47 oh, procedural issue: should we use RejectedBlocker whiteboard field for bugs considered but rejected? 16:29:03 ack 16:29:15 #action this bug does not qualify as a release blocker under the release criteria. remove f14alpha block https://bugzilla.redhat.com/show_bug.cgi?id=618504 + add RejectedBlocker whiteboard field 16:29:16 Bug 618504: medium, low, ---, enrico.scholz, NEW, Can not submit abrt bugs 16:29:17 * adamw also recently realized we should probably have put the release into the whiteboard field (e.g. AcceptedF14ABlocker), but that ship has sailed... 16:29:39 adamw +1 @ RejectedBlocker, but I think that should be RejectedF14AlphaBlocker 16:29:44 adamw: seems like a good idea if it gets revisted, though the comments would also show 16:29:53 ah, same idea 16:30:19 okay, ready to move on? 16:30:37 ok, after the meeting i'll update the wiki pages and do a search and adjust the whiteboard fields 16:30:42 next bug! 16:30:46 #topic https://bugzilla.redhat.com/show_bug.cgi?id=619238 16:30:47 Bug 619238: medium, low, ---, notting, NEW, can't login to normal rawhide install 16:30:57 need to decide if this is an accepted blocker or not 16:31:39 "In most cases, the installed system must boot to a functional graphical environment without user intervention" 16:31:40 = blocker 16:31:53 (we've already established that 'functional graphical environment' includes being able to login) 16:31:54 with the avc, shouldn't that go to selinux? 16:31:59 instead of "distribution"? 16:32:17 and yeah, +1 @blocker 16:32:38 that is, if this affects anyone but jens 16:32:43 * adamw hasn't rebooted his system for a day or two 16:32:56 I'll try to reproduce tonight 16:33:29 if I can reproduce the avc, I'll switch to component, ok? 16:33:30 i've seen a lot of people report failure to boot properly with systemd, but jens claims to be on upstart... 16:33:31 my system logs in fine, but I didn't just do a fresh from-disc instal 16:33:34 component = selinux I mean 16:33:45 proposed #action add as accepted F14alpha blocker "In most cases, the installed system must boot to a functional graphical environment without user intervention" + change component to SELinux 16:34:08 ack 16:34:08 I take that 16:34:17 s/SELinux/selinux-policy/ 16:34:25 If get to first boot on soas remix f14(rawhide) and fill in fields. sill cannot log in to gdm 16:34:25 drago01: thx 16:34:31 nack, i'm actually a bit worried about the 'uniqueness' of the report, now i think about it 16:34:37 adamw: I'll reproduce first 16:34:41 i'd like someone else to reproduce this... 16:34:59 poelcat: add "reproduce on latest rawhide" please 16:35:01 although i suppose he was doing a clean install 16:35:07 okay, on balance, ack for now :) 16:35:26 and I'll take it, if everyone agrees 16:35:52 ok 16:35:56 #action add as accepted F14alpha blocker "In most cases, the installed system must boot to a functional graphical environment without user intervention" + change component to "selinux-policy" + try to reproduce w/ latest compose 16:36:07 last one! 16:36:11 #topic https://bugzilla.redhat.com/show_bug.cgi?id=617115 16:36:12 Bug 617115: medium, low, ---, dhuff, ON_QA, rawhide live spins showing black screen instead of syslinux boot menu 16:36:25 check a quick checkin to see if this one is heading in the right direction 16:37:19 nirik ? 16:37:34 yes, that should be fixed. 16:37:35 i think this is fixed now, right? 16:37:36 I think that was more or less fixed by a syslinux update, not too sure 16:37:44 k 16:37:45 it was fixed by a livecd-tools update. 16:37:50 move to VERIFIED or CLOSED ? 16:37:52 * adamw can confirm that one 16:38:01 either, but I guess CLOSED. 16:38:13 have we checked the livecd-tools update made it into rawhide with all the shenanigans? 16:38:22 i just grabbed it from koji 16:38:59 * nirik checks 16:39:01 repoquery -i livecd-tools shows 032-5 for me 16:39:04 which is not a fixed build 16:39:09 livecd-tools-032-5.fc14 dist-f14 dmalcolm 16:39:18 thats the python rebuild one. 16:39:33 ahh, the python 2.7 branch merge would have overwritten the more recent builds 16:39:44 yeah, we need another f14/rawhide build I think. 16:39:52 wolf: you'll need to bump and rebuild it once more with the 033-2 changes 16:39:54 brunowolff: you still around? would you be willing to do that? or would you like me to? 16:39:55 doh 16:40:02 brunowolff: ^^^ 16:40:06 Yes. 16:40:29 I was reading some mail in another window and it took a bit to see the flashing xchat icon. 16:41:17 Your asking me to bump livecd-tools for python? 16:41:28 brunowolff: no, it's already been bumped for python 16:41:42 but the python rebuild was done off 032-4 and versioned 032-5; it doesn't have the changes from 033-1 and 033-2 16:41:47 proposed #action need another f14/rawhide build because of python 2.7 branch merge + confirm this bug is fixed and then move to VERIFIED/CLOSED 16:42:00 yeah, so it needs another bump and rebuild 16:42:06 so you need to check it out, re-add the 033-2 changes if necessary (I'm not sure exactly what will be in the repo), and rebuild it as 033-3 16:42:20 proposed #action need another bump + f14/rawhide build because of python 2.7 branch merge + confirm this bug is fixed and then move to VERIFIED/CLOSED 16:42:28 * adamw updated the bug already 16:42:28 ack 16:42:30 ack 16:42:34 Yes, I'll do that. 16:42:51 #action need another bump + f14/rawhide build because of python 2.7 branch merge + confirm this bug is fixed and then move to VERIFIED/CLOSED https://bugzilla.redhat.com/show_bug.cgi?id=617115 16:42:52 Bug 617115: medium, low, ---, dhuff, ON_QA, rawhide live spins showing black screen instead of syslinux boot menu 16:43:02 I haven't played with the new git stuff, so it will take me a bit longer than it would have otherwise. 16:43:10 great discussion and looks like maybe we saved ourselves some pain by doing so :) 16:43:14 #topic open discussion 16:43:20 anything else before we close for today? 16:43:23 brunowolff: there's an idiot's guide from oxf13 on -devel list 16:43:53 hmm, yes 16:44:12 if I can't reproduce the avc, I won't set the blocker flag 16:44:18 correct? 16:44:29 I figure it won't be too hard. But normally I think I could have had the new builds going in about 5 minutes. 16:44:41 was "In most cases, the installed system must boot to a functional graphical environment without user intervention" https://bugzilla.redhat.com/show_bug.cgi?id=619238 16:44:43 Bug 619238: medium, low, ---, notting, NEW, can't login to normal rawhide install 16:44:44 I'll need to be more careful since things aren't familiar. 16:44:52 fcami: it's already set, we just want to verify that it is fixed 16:44:54 fcami: if you can't reproduce, update the bug and ask for more info 16:45:07 ok, I'll do that 16:45:08 poelcat: no, he's talking about the earlier bug about rawhide not booting 16:45:11 oh :) 16:45:26 not accepting logins, yes 16:45:29 there is another 'blocker' issue: we need a few python rebuilds to clear the image composes 16:45:40 i've discussed these with dmalcolm, but we need to make sure they happen 16:45:42 adamw: how are we tracking those? 16:45:50 why not just throw on f14alpha 16:45:54 poelcat: mostly in mine and david's head =) 16:45:56 and i'll include in my periodic reminder 16:46:03 we don't have bug reports for each broken package, there'd be too many 16:46:04 bad adamw! :) 16:46:08 oh 16:46:18 we do have one report for a significant package - https://bugzilla.redhat.com/show_bug.cgi?id=618791 , technically that should probably be a blocker, i'll add it 16:46:20 Bug 618791: medium, low, ---, bnocera, NEW, totem does not build against libpeas-devel-0.5.3-2.fc14: missing symbols: peas_plugin_info_{s|g}et_visible 16:46:41 totem being broken in itself isn't a blocker, but the fact that the package has dependency issues would break the composes 16:46:43 A note about squashfs. 16:46:58 adamw: make sense then to add significant ones that we want to make sure we get to f14alpha ? 16:47:00 ACK for me to add it to F14Alpha and set AcceptedBlocker? 16:47:06 ACK 16:47:21 I was able to seemingly duplicate the problem by running mksquashfs while the ext3 was still loop mounted. 16:47:28 poelcat: there's five otehrs - gnome-dvb-daemon , gnumeric , blueman , wireshark , gnote. i'll try and file bugs for all of them if i can stand the tedium =) 16:47:36 adamw: ack 16:47:40 adamw: thanks! 16:48:31 proposed #action need to track unfinished python rebuilds, will add to 'f14alph' totem, gnome-dvb-daemon , gnumeric , blueman , wireshark , gnote 16:52:10 #action need to track unfinished python rebuilds: adamw will add totem, gnome-dvb-daemon, gnumeric, blueman, wireshark, and gnote to 'f14alpha' so we make sure they get done in time 16:52:19 closing meeting in 90 seconds 16:52:33 ok by me 16:53:11 ditto 16:54:10 thanks everyone... great meeting! 16:54:13 #endmeeting