15:03:34 <jlaska> #startmeeting
15:03:50 <adamw> first up:
15:03:51 <adamw> #link https://bugzilla.redhat.com/show_bug.cgi?id=486284
15:03:53 <buggbot> Bug 486284: medium, low, ---, pjones, MODIFIED, [PATCH] RFE: ext4 support in grub
15:04:00 <jlaska> #chair adamw
15:04:04 <adamw> gr.
15:04:08 <adamw> #link https://bugzilla.redhat.com/show_bug.cgi?id=486284
15:04:10 <buggbot> Bug 486284: medium, low, ---, pjones, MODIFIED, [PATCH] RFE: ext4 support in grub
15:04:15 <adamw> let's assume that worked. =)
15:04:39 <denise> AFAIK, 486284 is done but retest would be helpful
15:04:43 <adamw> this is the ext4 bug. according to comments all changes are committed. has anyone been able to test?
15:05:08 <jlaska> so with this change ... '/boot' will now default to ext4?
15:05:17 <jlaska> or is that another patch in the future?
15:05:26 <adamw> good question - denise, what's the expected behaviour exactly?
15:05:31 <denise> the default should be ext4
15:05:38 <adamw> denise: should it create an ext4 /boot, or just stick /boot on the root partition?
15:06:05 <denise> will get bz updated with exact description
15:06:10 <adamw> ok, thanks
15:06:14 <jlaska> #action jlaska - check for F12 install test case updates related to /boot as ext4
15:06:14 <adamw> and we should test it as a priority
15:06:42 <adamw> anything else on that one?
15:07:11 <notting> should probably check the livecd partitioning as well
15:07:27 <adamw> good point - test both cases
15:07:28 <notting> erm, strike that. that uses the same constraints as normal installs
15:08:10 <adamw> ok, next up:
15:08:16 <adamw> #link https://bugzilla.redhat.com/show_bug.cgi?id=510033
15:08:17 <buggbot> Bug 510033: urgent, high, ---, dlehman, MODIFIED, AttributeError: 'NoneType' object has no attribute 'name'
15:08:31 <adamw> this is the infamous one which was breaking either all or most installations
15:09:10 <adamw> we have one confirmation that it's fixed, but since it's so important i'm holding out for two before we mark it as such
15:09:25 <f13> yeah it may be fixed, but other installer issues prevented verification
15:09:28 <jlaska> I'd offer waiting until the fixed build is in rawhide too
15:09:44 <denise> f13 c'mon - other metwork manager issues ;-)
15:10:08 <f13> denise: whatever.  Issues with software in the anaconda runtime environment
15:10:37 <adamw> yeah, we can only test once the bug we're coming to in a minute is fixed, or by building a live CD image or something
15:10:47 <adamw> as maxamillion did
15:11:33 <adamw> so, let's go a bit out of order and take the other big installation-environment bug next
15:11:42 <adamw> #link https://bugzilla.redhat.com/show_bug.cgi?id=513020
15:11:43 <buggbot> Bug 513020: high, low, ---, davidz, ASSIGNED, Unable to acquire networking to perform network install
15:12:19 <f13> there was another dbus built last night
15:12:27 <f13> * Thu Jul 23 2009 Colin Walters <walters@redhat.co> - 1:1.2.16-3 - Remove conflicting -U option to useradd
15:12:50 <f13> that should clear up this particular issue
15:12:50 <jlaska> f13: rawhide (yesterday) still has anaconda-12.3-1 ... does anything special need to be done from a releng perspective to get builds in right now?
15:12:58 <adamw> would that likely have been in use when clyde did his test?
15:12:59 <f13> no, anaconda wasn't the fix
15:13:02 <f13> dbus was
15:13:04 <jlaska> f13: I konw
15:13:06 <jlaska> I didn't say it was
15:13:15 <adamw> it is the fix for the other issue, though...
15:13:32 <jlaska> f13: is any special tagging needed to get packages in to rawhide right now ... or does everything get pulled in?
15:13:44 <f13> we're not in a freeze, so there is nothing special needed
15:13:53 <jlaska> cool, thanks
15:14:07 <f13> 12.4/5 wre built yesterday
15:15:05 <f13> and anconda-12.5 was in the 20090723 rawhide
15:15:15 <f13> (which would be yesterday)
15:15:25 <jlaska> hmm, sounds like another syncing issue getting content pulled internally
15:15:46 <f13> yeah
15:15:53 <f13> that's been all FUBAR lately
15:16:22 <jlaska> f13: Do you think you could poke around there?
15:16:59 <jlaska> odd, gromit.redhat.com also has  anaconda-12.3-1
15:17:01 <adamw> so to summarize: for 501033 we need anaconda 12.5 to be pulled into the building of actual install images, and for 513020 we need the new dbus to hit rawhide and get propagated, which should hopefully happen today
15:17:03 <f13> one of the netapps is getting replaced I think.  THere are lots of other hands on it
15:17:06 <jlaska> adamw: sorry ... all you
15:17:21 <adamw> er, s/501033/510033/
15:17:35 <f13> adamw: the former is happening, and it happened yesterday.  The latter should be happening in the rawhide currently being composed
15:17:42 <jlaska> adamw: yeah I think that captures where we are at
15:19:19 <adamw> OK.
15:19:26 <f13> oh dear.
15:19:28 <adamw> ?
15:19:40 <f13> rawhide fell over last night
15:19:45 <notting> woo!
15:19:54 <f13> Running rpm_check_debug
15:19:55 <f13> ERROR with rpm_check_debug vs depsolve:
15:19:55 <f13> rpmlib(PayloadIsXz) is needed by glibc-2.10.90-7.1.i686
15:19:55 <f13> rpmlib(PayloadIsXz) is needed by glibc-common-2.10.90-7.1.i686
15:19:55 <f13> Complete!
15:19:57 <f13> (1, [u'Please report this error in http://yum.baseurl.org/report'])
15:20:27 <notting> OH. oops
15:20:47 <notting> -> #fedora-admin for this. we can move on here.
15:21:03 <adamw> OK.
15:21:06 <adamw> last bug on the list:
15:21:14 <adamw> #link https://bugzilla.redhat.com/show_bug.cgi?id=512377
15:21:16 <buggbot> Bug 512377: high, high, ---, steved, NEW, Upgrading nfs-utils on NFSv4 server kills downstream NFSv4 clients
15:21:23 <adamw> this is the one that was proposed by jeff garzik
15:21:48 <f13> not an Alpha blocker
15:21:56 <f13> but plenty of time to get it in
15:22:43 <adamw> yeah, as discussed on the list i can't strictly consider it a blocker, but it's definitely a 'would be nice to have fixed'
15:22:54 <jlaska> I'm inclined to agree ... however it is marked as severity high and has 103 votes
15:22:56 <notting> right, i'm not going to argue if they fix it
15:23:08 <jlaska> do we need consider this for any feature testing for the Alpha?
15:23:14 <adamw> jlaska: remember, vote count is tricky to consider in current bz
15:23:16 <notting> especially considering it affects F11 too ?!?
15:23:30 <adamw> it's actually 4 votes, because someone assigned 100 votes to it :)
15:23:40 <adamw> yeah, i'd argue fixing it in f11 should be a really major priority
15:23:49 <jlaska> heh ... yeah they aren't 100% accurate ... just another data point
15:23:57 <adamw> since from what i'm reading, a stable f11 update appears to have completely nerfed nfsv4 from all angles
15:25:21 <adamw> actually, the more i read, the more i wonder whether - strictly speaking - this affects rawhide at all
15:25:54 <adamw> see comment #2
15:25:59 * jlaska reads
15:26:25 <notting> well, you can update w/o rebooting
15:27:08 <jlaska> adamw: meaning the rawhide kernel should already have support for properly parsing /proc/fs/nfsd/versions ?
15:27:21 <adamw> that's what it looks like to me
15:27:30 <jlaska> same here
15:27:42 <adamw> suggestion: we drop it from f12alpha for now
15:27:49 <adamw> i post a comment asking for clarification from garzik
15:27:59 <adamw> if he's adamant that it affects rawhide and he explains why, we add it to f12blocker
15:28:06 <adamw> otherwise we don't
15:28:22 * jlaska likey
15:28:46 <jlaska> there is also a workaround for this issue ... albeit it involves hand editing an initscript
15:29:01 <adamw> yeah.
15:30:27 <adamw> ok, done
15:30:56 <adamw> shall we take a quick look through f12blocker?
15:31:15 <jlaska> let's doooeeeet
15:31:48 <notting> is the beta blocker empty?
15:31:51 <jlaska> #agreed drop bug#512377 from F12Alpha and post a comment asking for clarification
15:31:52 <buggbot> Bug https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=512377 high, high, ---, steved, NEW, Upgrading nfs-utils on NFSv4 server kills downstream NFSv4 clients
15:32:25 <adamw> oh, good question notting.
15:32:28 <adamw> f12beta has one bug: https://bugzilla.redhat.com/show_bug.cgi?id=512999
15:32:29 <buggbot> Bug 512999: medium, low, ---, bskeggs, ASSIGNED, xorg-x11-drv-nouveau displays colors incorrectly
15:32:30 <adamw> #link https://bugzilla.redhat.com/show_bug.cgi?id=512999
15:32:32 <buggbot> Bug 512999: medium, low, ---, bskeggs, ASSIGNED, xorg-x11-drv-nouveau displays colors incorrectly
15:32:51 <adamw> which was set by our very own jlaska
15:32:55 <adamw> defend yourself!
15:32:56 <adamw> :)
15:32:58 <jlaska> I don't trust him
15:33:16 <notting> get him a better camera! :)
15:33:36 <jlaska> this is a change in behavior from F11 on this nouveau system ... and surfaced while testing the liveCD for the display config fit'n'finish test day
15:33:51 <adamw> i suspect this may be a card-specific issue, as i booted to nouveau yesterday (to test it) and did not observe the same problem
15:34:04 <jlaska> yeah I suspect the same
15:34:06 <adamw> using the exact same package versions
15:34:16 <adamw> anyone else happen to have nvidia hardware with rawhide?
15:34:35 <notting> i have a really ancient card in a box that could be updated
15:34:50 <adamw> how ancient is ancient?
15:35:40 <notting> nv34?
15:35:58 <adamw> oh, that's fine. if you have a minute to test on that and add a comment it'd be helpful.
15:36:13 <adamw> if this is restricted to james' card it's hard to consider it a blocker
15:37:14 <jlaska> adamw: if it's specific to this card, that affects the severity as noted last week, right?
15:37:26 <jlaska> meaning, it can't be urgent then?
15:37:33 <adamw> jlaska: yeah, that's my working rule atm
15:37:49 <adamw> jlaska: if it only affects one specific card it's maximum high
15:37:57 <jlaska> right, yeah I think that's sound
15:38:08 <jlaska> I'm unclear yet how that affects it's blocker-ability though
15:38:18 <jlaska> esp in cases where it worked in the previous release
15:38:36 * jlaska isn't set on this bug ... but just like thinking through and documenting these dark hallways of bug logic
15:38:48 <adamw> i'd have a similar rule of thumb for blocker-ability, just on practical grounds...especially for a relatively immature driver like nouveau it's really hard to get to a point where there isn't a major bug in _some_ card or other
15:39:32 <jlaska> that brings up a good point
15:39:39 <jlaska> err well ... no you answered it already
15:39:40 <adamw> for e.g. we didn't take the issue affecting rather a lot of Mac models, where video doesn't work at all with the intel driver, as a blocker for f11
15:39:57 <jlaska> I'll check-in on smolt stats to see how many people have this
15:40:03 <jlaska> agreed
15:40:26 <adamw> to repeat my bugbear there, it would be really nice if smolt gave out pci ids via its web interface, and let you search on them.
15:40:38 <adamw> pci / usb ids are the _only_ really reliable way to uniquely identify hardware...
15:40:39 <jlaska> they're just hidden
15:40:55 <adamw> yeah, quite well hidden :) i don't think there's a way to search on them from the web interface, n'est-ce pas?
15:41:23 <jlaska> yeah
15:42:26 <adamw> ok, going through f12blocker
15:42:36 <adamw> i'll just pull out new bugs since last time, or ones that have had activity since last time
15:42:38 <adamw> so...
15:42:44 <adamw> #link https://bugzilla.redhat.com/show_bug.cgi?id=498156
15:42:46 <buggbot> Bug 498156: urgent, low, ---, sahartsu, NEW, gadmin-squid does not generate valid squid.conf
15:43:00 <adamw> the rationale for adding this to f12blocker is in the latest comment, i think it's probably a good one
15:43:16 <adamw> the package needs to be either fixed or dropped, we really shouldn't be carrying around a landmine like this for multiple releases
15:43:50 * jlaska loads bz
15:44:24 <jlaska> so a request for decommit
15:44:52 * jlaska searches for matching package guidline page
15:45:25 <notting> i'm all for removing it. but would like to see *some* comment one way or another from the maintainer
15:45:27 <adamw> the maintainer of the package does appear to be active
15:45:37 <adamw> see e.g. https://bugzilla.redhat.com/show_bug.cgi?id=512856 - he filed a bug four days ago
15:45:39 <buggbot> Bug 512856: medium, low, ---, nalin, NEW, sysstat still produces avc's
15:45:43 <adamw> so we could poke him directly to ask him to comment
15:45:51 <adamw> i'll do that
15:46:34 <adamw> #action adamw poke S.A. Hartsuiker re #498156
15:48:23 * jlaska updates the nouveau bug with a smolt link
15:49:43 <adamw> ok, i can find only one more new/changed bug in f12blocker:
15:49:44 <adamw> #link https://bugzilla.redhat.com/show_bug.cgi?id=513579
15:49:45 <buggbot> Bug 513579: medium, low, ---, lpoetter, NEW, GDM's PulseAudio doesn't die
15:50:24 <jlaska> gdm and pulseaudio ?  I didn't realize we ran a sound server there
15:50:37 <adamw> gdm can make noises, it runs pa to do so, aiui
15:50:44 <jlaska> gotcha
15:50:52 <jlaska> good summary from lennart
15:51:11 <jlaska> needs info from hadess
15:51:20 <adamw> well, this is quite a new one - i can accept it being on the blocker list as we can probably trust bastien's judgment, but lennart's requests for info all look reasonable too
15:51:29 <adamw> so i think this is a no-op for us, just keep an eye on it at the next meeting
15:51:55 <jlaska> #agreed no changes required on bug#513579 - await Bastien's feedback to Lennart's questions
15:51:56 <buggbot> Bug https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=513579 medium, low, ---, lpoetter, NEW, GDM's PulseAudio doesn't die
15:52:05 * jlaska playing too much w/ meetbot
15:52:12 <adamw> =)
15:52:29 <adamw> well, we're through all the blocker lists now...
15:52:39 <adamw> does anyone have any bugs they'd like to discuss for promotion to a blocker list?
15:52:50 * jlaska takes a look at another list briefly ...
15:53:35 <jlaska> looking through recently filed anaconda bugs
15:53:45 <jlaska> alindebe or denise: any that should be on the Alpha radar that you know of?
15:54:05 <denise> jlaska, nothing screams out at me
15:54:21 <jlaska> not sure on 513405
15:54:34 <jlaska> don't know if that affects *all* encrypted installs or not
15:54:59 <alindebe> jlaska: It doesn't
15:55:20 <alindebe> It's along the same lines as many of the lvm/md activate/deactivate errors
15:55:29 <alindebe> workaround is to wipe the disk before starting the install
15:55:30 <jlaska> so depends on what's on the disk to start with
15:56:32 <adamw> i just did a quick check of the 'urgent' severity bug list, nothing there that should be added
15:57:17 <jlaska> alindebe: are you able to post some information about the starting conditions that leads to that bz?
15:57:40 <jlaska> alindebe: understandable if not, I know the storage ones are hard to pinpoint the root cause
15:58:13 <alindebe> jlaska: I have no idea what was on the machine to begin with - I was following up on something clumens did
15:58:22 <jlaska> perhaps this is a case where we can link to the install test case being executed ... as we'll do for Liam's install testing
15:58:31 <jlaska> alindebe: okay
15:58:33 <alindebe> I can ask him next week, but I doubt he'll remember it by then
15:58:50 <jlaska> hehe, okay
15:59:20 <jlaska> bug#512651 ... another pvcreate failure ... similar to what alindebe mentioned earlier in that it's the previous disk contents
15:59:22 <buggbot> Bug https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=512651 medium, low, ---, anaconda-maint-list, NEW, Error during writing of partitiontable to disk
15:59:35 <adamw> so do we want to stick either of these on either blocker list?
16:00:33 <jlaska> I would think they fall under parts of https://fedoraproject.org/wiki/Anaconda/Features/StorageFiltering#Detailed_Description ... but I'd need to check in with dlehman for his thoughts as to whether thse share the same root cause
16:01:47 <jlaska> denise: should we run these bugs by dlehman to see if they line up with some of the storage cleanup areas listed in the feature?
16:02:40 <denise> jlaska, good idea, but he's on vacation today and much of next week
16:03:41 <jlaska> hmm, I suspect these would miss the feature freeze then
16:03:47 <denise> ;-)
16:04:09 <adamw> well, let's leave that to jlaska to deal with since he seems so keen ;)
16:04:27 <denise> jlaska, hes been working the list on the storage page and the common bugs list
16:04:57 <jlaska> #action jlaska talk to dlehman about 512651 and F12 storage cleanup feature
16:05:17 <adamw> call him in bermuda, i'm sure he'll like that
16:05:27 <jlaska> adamw: I'll leave that part for you :P
16:05:34 <adamw> hehe
16:05:38 <adamw> ok...any other business?
16:05:47 <denise> adamw: good luck, he's above the treeline by now ;-)
16:05:48 <jlaska> if he's not around, they have no chance to make feature freeze, so we'll just need to see if they're beta issues on that feature
16:05:59 <jlaska> gone walk'about
16:06:08 <f13> need to review the contengency plan
16:06:13 <f13> contingency even
16:07:01 <notting> i thought mo was still trying to figure out filtering UI
16:08:02 <denise> notting, yes
16:10:10 <adamw> ok then...meeting closing in...
16:10:17 <adamw> 3
16:10:30 <adamw> 2
16:10:42 <jlaska> go go go!
16:10:45 <adamw> 1
16:10:58 <adamw> #endmeeting