From Fedora Project Wiki

< ReleaseEngineering‎ | Meetings

Revision as of 18:01, 13 February 2015 by Holmja (talk | contribs) (IRC Transcript: Cleaned up table markup.)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Fedora Release Engineering Meeting :: Monday 2007-10-22

F8 Readiness Discussion

IRC Transcript

Idea.png f13 changed the topic of #fedora-meeting to: Release Engineering Meeting13:02
f13jwb: notting: jeremy: wwoods: warren: rdieter: poelcat: spot: ping13:03
* notting is here13:04
* spot is here13:04
* jeremy is around13:04
Idea.png f13 changed the topic of #fedora-meeting to: Release Engineering Meeting - Release Readiness13:05
f13so I invited a bunch of folks to crash the meeting today, to discuss release readiness.  Something I want to do on a nearly daily bases as we head toward Fedora 813:05
f13Do we have any guests out there?13:06
* poelcat here13:07
* wwoods almost here (need beverage)13:08
f13hrm, looks like nobody is joining us.13:08
f13jrb: cebbert davej ping13:08
f13We're planning for a Nov 8 release13:10
f13In my mind that means we have to have a Gold tree by Nov 1, maybe the 2nd if it's early in the day13:10
* jwb is late13:10
f13that means we have this week to really pound out bugs and validate install paths13:10
f13We have a slight issue with disk space in the colo and getting signed packages written out.  We need to do some garbage collection first13:11
wwoodspretty much, yeah13:11
f13so I don't plan on starting to write out signed packages until this weekend13:11
warrenf13, be sure to remind me when signing happens13:11
f13warren: I will13:11
f13I'm pretty confident in the compose tools so it really should be all about the bits.13:12
nottinghow slight is slight?13:12
f13we've got 250~ G free13:13
ljuwaidahis this the kde meeting?13:13
jwbljuwaidah, no13:13
f13ljuwaidah: no.13:13
ljuwaidahwhere is it then?13:13
f13ljuwaidah: you missed it.13:14
f13off by an hour perhaps13:14
ljuwaidahisn't it at 5PM utc?13:14
f13right now is 5pm UTC correct.13:15
jwbbut it's not the KDE meeting13:15
nottingljuwaidah: ... on tuesdays13:15
lmackenljuwaidah: tuesdays13:15
f13ljuwaidah: you're off by a day13:15
ljuwaidahsorry :D13:15
f13so anyway...13:16
f13that's where we're at from the compose side of things.13:16
ljuwaidahcan i stay?13:16
nottingf13: any insight into the errors from anaconda-devel-list?13:16
f13I'm going to drop fedora-release in today I think, provided that mdomsch hooked up the mirrorlist cgi to return f8 requests to rawhide for now.13:16
f13notting: no, and they didn't repeat last night13:16
f13I can start signing and importing if I have sufficient disk space ona  box somewhere, or else I"d have to abuse /mnt/koji for the signing even, not just writing out.13:17
f13ljuwaidah: you're welcome to stay.13:17
ljuwaidahf13: thanks :)13:18
f13wwoods: what do we have setup QA wise?13:18
poelcathas the, this is not available problem related to kde been fixed?13:19
poelcati still see it updating x86_6413:19
f13rdieter: ?13:20
wwoodsf13: the usual junk, mostly just KATE install tests. I've got some upgrade tests lined up for F7->F813:21
wwoodsthere's no automated testing for Live images yet, so those will need attention13:21
f13wwoods: do we have a tree testing page?  Going to send out the "OMG TEST IT NOW" emails?13:21
wwoodsI'll be doing that stuff today13:21
wwoodsBlocker list is still at 51 bugs, but quite a few of those are questionable13:22
wwoodsthings that will need attention: PulseAudio (esp. in KDE), NM, new compiz..13:23
cebbertf13: belated pong13:23
wwoodsoh. what's going on with GRUB menu entries? I keep seeing bugs about it failing to drop old entries on upgrade, or failing to add entries for Windows13:24
jeremywwoods: the latter was a bug in booty that I fixed just after test313:24
davejf13: ugh, little more warning than 30 mins next time please?13:24
jeremywwoods: the former still needs looking at (and is on the blocker list, as we should really fix it because it looks really bad)13:24
f13davej: sorry, it just occured to me that we could double book this meeting time.13:24
wwoodsthere's also no update on the traditional Post Freeze Boot Hang (bug 338551)13:24
davej(especially as my fetchmail only runs every 30 minutes..)13:25
f13davej: of course if I waited for people to give me feedback, we'd probably have our first meeting next year.13:25
f13wwoods: I think a kernel went in last night that fixes that.13:25
wwoodsjeremy: is that one gonna be a tricky fix? I hate messing with grub etc. this close to release13:25
f13- Disable polling before registering netdevice in e100.13:25
jwbi'd like to know what the hell is going on with my backlight buttons, but i don't consider it anywhere close to a release blocker13:26
jeremywwoods: shouldn't be tricky other than setting upgrades takes too damned long :)13:26
wwoodsoh, I noticed that we have a repo-edit button when pirut fails to start now.. that should make bug 315671 (pirut/pup demand DVD) non-blocker13:27
nottingjeremy: fwiw, on a FC6 upgrade i did, grubby created two new entries and did not remove the old one13:27
jeremywwoods: or even closed as the fix is "let you go in and disable the repo" :)13:28
jeremynotting: yeah, I reproduced it when I did an upgrade a week or so ago.  but I then didn't set up a second upgrade to test with13:28
wwoodsjeremy: oh, anaconda allowing x86_64 upgrades on i386 systems (222424) - any plan for that one?13:28
jeremywwoods: we _should_ be giving a warning now.  if we're not, then that's the fix13:28
poelcatf13: what package should I file a bug against for the problem?13:29
wwoodsjeremy: right, but you mention wanting a long-term solution, and I didn't know if you wanted to keep the bug open for that. If not, I'll retest and close13:29
f13poelcat: what is the full error output?13:29
wwoodsf13: do we have config files etc. for making RC images?13:29
jeremywwoods: nah13:29
wwoodsor, better yet, RC images?13:29
jeremywwoods: we can't do an RC until we have signed packages13:30
f13wwoods: I don't want to call them "RC" until packages are signed, but I don't envision changing the config files from as shipped in current pungi package (and fedora-release once I tag it)13:30
wwoodswell, not literal RC images/media, but just some DVD images I can test with (since we have media-based tests and bugs)13:31
wwoodskcool, I'll run with what's in pungi13:31
f13wwoods: the config in the pungi package is suitable.13:31
f13I was going to make a pile of them today but anaconda boomage13:31
jeremylivecd is still hovering a little too close for comfort to the size (and ended up going over with the build I did this morning), so probably going to end up taking something out and shooting it13:31
poelcatf13: ERROR with rpm_check_debug vs depsolve:13:31
poelcatPackage kdegraphics needs, this is not available.13:31
poelcatPackage kdebase needs, this is not available.13:31
poelcatupdating OpenEXR-libs so I'll file it there I guess13:32
f13poelcat: I don't see those broken deps in the rawhide report13:32
poelcathmm  I see it on my box :)13:32
f13poelcat: I bet new installs don't see this.  Would be interesting to see if F7 -> F8 sees it though13:32
jeremyf13: that's easy enough to test.  one sec13:33
f13davej: cebbert: how are we looking kernel side?13:36
jwbi've been running rawhide kernels for a while now.  seem pretty stable13:37
jwbacross i686, x86_64, ppc6413:37
f13there is an e100 crasher I've heard about13:37
jeremyf13: it looks like a lot of the kde packages now have split out -libs packages.  which means they're going to need upgrade munging13:37
nottingjeremy: ugh. that's going to break yum upgrades too13:38
jeremyrdieter: can you file a bug against anaconda with how things were split so that we can actually have upgrades work13:38
jeremynotting: yes, yes it is13:38
f13le sigh13:38
* jeremy notes that the fact that the x86_64 live image is multilib makes testing this incredibly easy...13:38
davejf13: I still haven't got confirmation that the e100 problem is fixed properly (though upstream ACKd the patch I did)13:38
davejf13: otherwise - not too shabby. I'm going to kick off a bunch of installs today and see if I can shake anything out.  On the whole though, we're in better shape than we were this time at F713:39
cebbertf13: e100 bug is 32152113:39
wwoodshow about the other stuff on the kernel blocker list? actually worth blocking over?13:39
jwbi know that ppc kernels stopped working on ppc32 CHRP recently13:40
jwbbut nobody cares13:40
jwbthey're broken in F7 update kernels anyway13:40
davejI seem to have gained a ppc imac, so I could give that a test later too. (or I could do something useful with my time)13:40
jwbdavej, that's not 32-bit CHRP13:41
cebbertwwoods: I think most of those can be solved by disabling DMA for libata devices, at least that will get the install working13:41
davejno, I know.13:41
* nirik notes that both his ppc32 and x86_64 rawhide test boxes have been just fine with current rawhide kernels. 13:41
jwbdavej, you're welcome to send that imac to me.  i'd make use of it13:41
jwbnirik, 32bit CHRP is like a 43p-150 RS/600013:41
f13Im' pretty sure we've made no claims to supporting that hardware13:41
cebbertwwoods: do we have a link to in the release notes?13:41
nirikjwb: yeah, I had a bebox that I think was a CHRP box... it's been a long time tho, so I might be misremembering.13:41
jwbf13, not true.  it was supported in FC-6 and F7 on release13:42
wwoodscebbert: no, but we definitely should13:42
davejjwb: noted for when I need that space :)13:42
f13jwb: but was that intentional or by accident?13:42
jwbf13, i know because i sent one to nasrat for it way back when13:42
jwbf13, intentional13:42
jwbf13, anyway, there's a bug open and dwmw2 is looking at it13:42
f13do we even setup the booting correct for chrp in the boot images?13:43
davejwwoods/cebbert: hmm, is it really release note material?   it may give an overly negative impression.. "here's a list of a dozen things that might go wrong"13:43
davejas opposed to the actual "common problems we know about in F8" link we already have13:43
wwoodserr, hmm13:43
jwbf13, you have to enter linux32 or something explicitly in yaboot but it worked13:43
nirikany chance the last of the ps3 blockers could get fixed so f8 works out of the box for installs? (I know there probibly aren't many ps3 installs, but it would be nice. ;)13:43
wwoodswell, we should.. yes. the Common Bugs link should mention the KernelCommonProblems page13:43
jwbf13, but in reality, there are very few people that even have these machines still.13:43
f13nirik: that reminds me to test that thing today13:44
cebbertwwoods: but maybe we should note that these aren't necessarily known to be present in F813:44
nirikf13: if you could also update the wiki page on exactly how to do the install that would be cool too. I have been meaning to try here, but haven't yet.13:45
* rdieter looks in...13:45
wwoodscebbert: right. hmm. probably it just needs to be mentioned as "if you're having problems that are't mentioned in this list, here are a few places you can look for de3bugging help"13:46
rdieterjeremy: fyi,
f13nirik: bah.  Still can't use the network device.13:47
nirikf13: is there a bug on that? just anaconda not using the right device name?13:47
f13nirik: I'm not sure if there is  abug.  If I don't find one I'll file one today13:47
f13jrb: ping; anything from you RE F8 release?13:48
davejwwoods: yeah, that sounds good13:48
jeremyrdieter: thanks; added to the blocker list13:48
wwoodswho's responsible for iscsi stuff? we've got 2 iscsi bugs on the blocker list13:49
f13thats probably pjones13:49
jrbf13: not really; I'm mostly just logging this today. )-;13:49
f13jrb: ok.13:49
f13Is there anything anybody else would like to talk about re the F8 release?13:49
f13(we should have our release notes soon)13:50
wwoodsf13: should we block for the three packages still apparently in need of rebuilding for ppc32 selinux junk?13:50
jwbwwoods, which 3 packages?13:50
f13wwoods: If they're in the default install path yes, otherwise probably not.13:51
wwoodsjwb: syslog-ng, redhat-lsb, perl-BerkeleyDB13:51
wwoodsredhat-lsb actually appears to be pulled in on default installs13:51
f13hrm, those seem somewhat important.13:52
jwbwwoods, do they simply not build at all, or are they just in need of a rebuild?13:52
f13well, syslog-ng isn't.13:52
f13jwb: they're in need.  They were built during a time that glibc on ppc32 was making everything need execmem13:52
* jrb reads13:52
f13so if you use those with selinux enabled you will get denials.13:52
wwoodsalthough, actually, running lsb_release on ppc64 doesn't throw errors13:52
* davej eyes the number of packages that haven't been rebuilt since fc613:52
jwbf13, ok.  so who owns then?13:52
jwber, them13:52
f13wwoods: it's not guarenteed that they'll fail.13:53
jeremyredhat-lsb got built iirc13:53
jeremyyeah, 3 oct13:53
f13herm, yeah13:53
f13that bug can be closed13:53
wwoodsconfirmed, just built it13:54
f13mclasen: hey, toss you to the fire, but do you have anything to comment on regarding the push to F8 final?13:56
mclasenno comments; dcbw built another nm snapshot last night13:57
lmackenf13: I'll be doing a bodhi upgrade shortly, which will then allow people to start adding F8 updates.13:57
f13lmacken: thanks.13:57
mclasenI don't know if stransky is still trying to get the "plugin installation sucks" bug in13:57
f13mclasen: yeah, we'll tag that one.13:57
davejnot sure just how good/bad the wireless drivers are this time around, could probably do with making a list of whats been tested/known working/broken13:58
jeremydavej: there's a reasonable-ish list in my laptop list :)13:58
davejjeremy: ah, good point.13:58
jwbjeremy, what laptop list?13:59
jwbhm... i should add my stuff there14:00
f13Is there anything else?14:00
f13ok, Meeting over.14:01
davejf13: do we have an ETA on when we can expect to see an rc tree ?14:01
f13davej: consider rawhide RC14:01
f13(minus signed packages)14:01
wwoodstomorrow's rawhide should be installable14:01
davejwwoods: todays isn't?14:01
wwoodstoday's needs an updates.img, but works otherwise14:01
f13davej: with today is installable.14:02

Generated by 2.3 by Marius Gedminas - find it at!