From Fedora Project Wiki
m (1 revision(s))
(→‎IRC Transcript: Removed some HTML markup.)
Line 13: Line 13:
== IRC Transcript ==
== IRC Transcript ==


<pre>#!html
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<title>2008-03-17-16:45-meeting-snapshot</title>
<link rel="stylesheet" href="irclog.css" />
<meta name="generator" content="irclog2html.py 2.3 by Marius Gedminas" />
<meta name="version" content="2.3 - 2005-03-28" />
</head>
<body>
<body>
<table class="irclog">
<table class="irclog">
Line 175: Line 163:


<div class="generatedby">
<div class="generatedby">
<p>Generated by irclog2html.py 2.3 by <a href="mailto:marius@pov.lt">Marius Gedminas</a>
<p>Generated by irclog2html.py 2.3 by [mailto:marius@pov.lt Marius Gedminas]
- find it at <a href="http://mg.pov.lt/irclog2html/">mg.pov.lt</a>!</p>
- find it at [http://mg.pov.lt/irclog2html/ mg.pov.lt]!</p>
</div>
</div>
</body>
</html>
</pre>

Revision as of 17:14, 18 February 2014

Fedora Release Engineering Meeting :: Monday 2008-03-17

F9 Beta Status

  • anaconda regressions over the weekend
  • url method is broken--traceback when getting bugurl fixed with updates.img
  • pushing hard for a Thursday release
  • space issues with PPC compose fitting on media
  • if we have to slip beta, we slip for anaconda issues and let rawhide move on
  • http://fedoraproject.org/wiki/QA/ReleaseCriteria


IRC Transcript

<body>

-!- f13 changed the topic of #fedora-meeting to: Fedora Release Engineering Meeting - Roll Call<a href="#t14:07" class="time">14:07</a>
* jwb is 1/2 here<a href="#t14:07" class="time">14:07</a>
* poelcat here<a href="#t14:08" class="time">14:08</a>
f13ping: jeremy notting jwb spot wwoods rdieter lmacken poelcat warren<a href="#t14:08" class="time">14:08</a>
* jwb is 1/2 here<a href="#t14:08" class="time">14:08</a>
jwb:)<a href="#t14:08" class="time">14:08</a>
f13jeremy is in class, spot is MIA<a href="#t14:08" class="time">14:08</a>
* wwoods here<a href="#t14:09" class="time">14:09</a>
rdieterhiya<a href="#t14:11" class="time">14:11</a>
* warren here, although might lose my laptop <a href="#t14:11" class="time">14:11</a>
* jwb adjourns meeting<a href="#t14:14" class="time">14:14</a>
wwoodsheh!<a href="#t14:15" class="time">14:15</a>
jwbseriously, i think we have lots of stuff to do.  summary:<a href="#t14:16" class="time">14:16</a>
jwb1) anaconda has issues<a href="#t14:16" class="time">14:16</a>
jwb2) we have space issues on ppc that aren't really ppc related growth<a href="#t14:16" class="time">14:16</a>
wwoodsthere's an updates.img for that, I think<a href="#t14:16" class="time">14:16</a>
jwbwwoods, sure<a href="#t14:16" class="time">14:16</a>
jwb3) OOMs during install<a href="#t14:16" class="time">14:16</a>
wwoodsf13: do you have a URL for the updates.img? or a bug number that contains that image/URL?<a href="#t14:17" class="time">14:17</a>
warrenthere are remaining mkinitrd on software raid issues<a href="#t14:17" class="time">14:17</a>
warrenI'm trying to track that one down, but managed to crash anaconda in the process<a href="#t14:17" class="time">14:17</a>
f13wwoods: <a href="http://reducto.boston.redhat.com/pungi/bleed/updates.img">http://reducto.boston.redhat.com/pungi/bleed/updates.img</a><a href="#t14:17" class="time">14:17</a>
wwoodsnote to self: actually write code for 'grabupdates' anaconda flag<a href="#t14:18" class="time">14:18</a>
* jwb gets 404<a href="#t14:19" class="time">14:19</a>
f13jwb: yeah, it's an internal host<a href="#t14:20" class="time">14:20</a>
* f13 wonders why fedorapeople.org is not letting me log in<a href="#t14:21" class="time">14:21</a>
f13oh well<a href="#t14:21" class="time">14:21</a>
-!- f13 changed the topic of #fedora-meeting to: Fedora Release Engineering Meeting - Beta Status<a href="#t14:21" class="time">14:21</a>
f13today, not so good.  We've had some anaconda regressions over the weekend<a href="#t14:22" class="time">14:22</a>
f13url method, busted.  traceback when getting bugurl (see updates.img discussion above)<a href="#t14:22" class="time">14:22</a>
f13Trying to get an install to finish so that we can see if encrypted stuff works with the new mkinitrd, but running into OOM issues.<a href="#t14:22" class="time">14:22</a>
f13but I'm still going to push hard for a Thursday release<a href="#t14:23" class="time">14:23</a>
warrenany idea what exactly is using all memory?<a href="#t14:23" class="time">14:23</a>
f13Today I'm oging to pre-stage some content on the netapp for beta, basically the exploaded trees and some isos from today.  They won't be available to the mirrors, but it'll save us tonns of time once we actually have gold content<a href="#t14:24" class="time">14:24</a>
f13warren: no, it happened while I was gone at lunch.  I suspect either a runaway %post or bad yum caching or something else.<a href="#t14:24" class="time">14:24</a>
wwoodsf13: installing from media? or using the updates.img?<a href="#t14:25" class="time">14:25</a>
f13media<a href="#t14:26" class="time">14:26</a>
f13with updates.img<a href="#t14:26" class="time">14:26</a>
f13media needs updates.img too<a href="#t14:26" class="time">14:26</a>
f13hrm, this is strange<a href="#t14:27" class="time">14:27</a>
f13free shows 1052216 for swap, but 490548 for mem<a href="#t14:27" class="time">14:27</a>
f13I thought this machine had a gig, not 512 meg<a href="#t14:27" class="time">14:27</a>
jwbstill OOM with 512MiB is evil as well<a href="#t14:27" class="time">14:27</a>
warrenf13, AGP grabbed 512MB aperture?<a href="#t14:27" class="time">14:27</a>
f13warren: 512 would be a /big/ grab<a href="#t14:28" class="time">14:28</a>
jwbf13, also didn't you say you installed the PS3 over the weekend?<a href="#t14:28" class="time">14:28</a>
f13jwb: yes, I did, text install<a href="#t14:28" class="time">14:28</a>
jwband this is not a text install?<a href="#t14:28" class="time">14:28</a>
wwoodsmirrored updates.img as <a href="http://wwoods.fedorapeople.org/updates/20080317.img">http://wwoods.fedorapeople.org/updates/20080317.img</a><a href="#t14:28" class="time">14:28</a>
f13thanks.<a href="#t14:29" class="time">14:29</a>
f13I couldn't ssh to fedorapeople.org for some reason<a href="#t14:29" class="time">14:29</a>
f13so anyway, I'm going to keep banging on that, while uploading content to the netapp hidden away<a href="#t14:30" class="time">14:30</a>
f13ideally we'd have the golden package set as tomorrow's rawhide, or else we slip<a href="#t14:30" class="time">14:30</a>
f13and I will be sad panda<a href="#t14:30" class="time">14:30</a>
wwoods(someday we'll have code in anaconda to optionally autofetch <a href="http://anaconda.fedoraproject.org/updates/$TIMESTAMP.img">http://anaconda.fedoraproject.org/updates/$TIMESTAMP.img</a>)<a href="#t14:30" class="time">14:30</a>
wwoodsyeah, my parents decided to come visit this week<a href="#t14:31" class="time">14:31</a>
wwoodsso if we have to extend the freeze another week.. bluh<a href="#t14:31" class="time">14:31</a>
f13yeah<a href="#t14:31" class="time">14:31</a>
f13well, I think if we have to slip, we're going to be slipping for anaconda stuff, and we can let rawhide move on<a href="#t14:32" class="time">14:32</a>
f13we'll just pull anaconda builds for beta testing<a href="#t14:32" class="time">14:32</a>
wwoodsright<a href="#t14:32" class="time">14:32</a>
jwbf13, i'm not seeing tons of stuff that we can drop when looking at the livecd configs.  but i'm a kickstart idiot<a href="#t14:33" class="time">14:33</a>
warrenf13, anaconda and mkinitrd possibly<a href="#t14:33" class="time">14:33</a>
f13warren: yes, and booty from peter for EFI grub hotness<a href="#t14:35" class="time">14:35</a>
f13Still haven't been able to do a full media install, or nfs iso install<a href="#t14:36" class="time">14:36</a>
warrenf13, are we backing ourselves into a corner where beta is delayed for another 2 weeks while rawhide is well past it? =)<a href="#t14:36" class="time">14:36</a>
f13want to try that later today<a href="#t14:36" class="time">14:36</a>
f13warren: we're already in that position<a href="#t14:36" class="time">14:36</a>
jwbf13, skvidal is awesome and added a --size option to repodiff for me.  showing nothing hugely significant for individual packages<a href="#t14:39" class="time">14:39</a>
f13crap<a href="#t14:39" class="time">14:39</a>
f13so maybe we just have to drop something<a href="#t14:39" class="time">14:39</a>
jwbrdieter, what is kipi-plugins?<a href="#t14:39" class="time">14:39</a>
jwbf13, yeah maybe :(<a href="#t14:40" class="time">14:40</a>
f13maybe drop some of the games?<a href="#t14:40" class="time">14:40</a>
jwbf13, was thinking something like that.  let me run this again on my compose from today and i'll email rel-eng with some results/suggestions<a href="#t14:40" class="time">14:40</a>
f13k<a href="#t14:40" class="time">14:40</a>
rdieterjwb: addons to kipi-aware apps, graphic/photo managers mostly, like digikam, kphotoalbum<a href="#t14:40" class="time">14:40</a>
jwbit grew lots<a href="#t14:41" class="time">14:41</a>
rdieterjwb: since, when?<a href="#t14:41" class="time">14:41</a>
jwbalpha<a href="#t14:41" class="time">14:41</a>
rdieterhrm.<a href="#t14:41" class="time">14:41</a>
jwb243K/144K ppc64/ppc<a href="#t14:41" class="time">14:41</a>
jwb"lots" is a relative term at the moment<a href="#t14:41" class="time">14:41</a>
rdieterkipi-plugins are definitely optional functionality, so could be a good candidate for chopping block<a href="#t14:42" class="time">14:42</a>
jwbrdieter, ok.  other than that, most of the additional space is coming from l10n packages for KDE<a href="#t14:43" class="time">14:43</a>
jwbabout 75MiB worth<a href="#t14:43" class="time">14:43</a>
jwbat least so far anyway<a href="#t14:43" class="time">14:43</a>
rdieterthose be huge, kdelibs-apidocs is a monster too (but hopefully not landing on any media)<a href="#t14:43" class="time">14:43</a>
f13ok, so other than ppc size issues, where we may have to trim some packages out of hte manifest, is there anything else beta releated to talk about?<a href="#t14:45" class="time">14:45</a>
jwbneed to test installs on multilib machines<a href="#t14:45" class="time">14:45</a>
jwbyum policy was updated<a href="#t14:45" class="time">14:45</a>
jwbwwoods, f13: how often have you done x86_64 installs?<a href="#t14:46" class="time">14:46</a>
f13I'm trying them every day<a href="#t14:46" class="time">14:46</a>
f13I have one rebooting right now<a href="#t14:46" class="time">14:46</a>
f13but it was software raid install so it might fail<a href="#t14:47" class="time">14:47</a>
f13or not...<a href="#t14:47" class="time">14:47</a>
jwbok, was just curious since that's the only other arch that the policy would impact<a href="#t14:47" class="time">14:47</a>
wwoodsall the time, yeah<a href="#t14:47" class="time">14:47</a>
f13hrm<a href="#t14:48" class="time">14:48</a>
f13for a default install, my x86_64 still has 65 i386 packages on it<a href="#t14:48" class="time">14:48</a>
f13I thought we wouldn't get that with the new yum default.<a href="#t14:48" class="time">14:48</a>
jwbskvidal, ?<a href="#t14:48" class="time">14:48</a>
skvidalf13: dependencies still pull in somethings<a href="#t14:48" class="time">14:48</a>
skvidalmultilib_policy only impacts what will be selected during an 'install'<a href="#t14:49" class="time">14:49</a>
skvidalit does impact what gets pulled in due to deps<a href="#t14:49" class="time">14:49</a>
f13skvidal: this is a clean install...<a href="#t14:49" class="time">14:49</a>
f13theoretically nothing should depend on i386 content...<a href="#t14:49" class="time">14:49</a>
skvidalthat first word is what matters<a href="#t14:49" class="time">14:49</a>
f13yep<a href="#t14:49" class="time">14:49</a>
f13oh fun..<a href="#t14:50" class="time">14:50</a>
skvidaldo you have the depsolve output?<a href="#t14:50" class="time">14:50</a>
f13removeing \*.i386 does bring stuff out<a href="#t14:50" class="time">14:50</a>
f13skvidal: anaconda doesn't save depsolve output anywhere<a href="#t14:50" class="time">14:50</a>
skvidalit brings out x86_64 stuff?<a href="#t14:50" class="time">14:50</a>
skvidalf13: then do it in an installroot<a href="#t14:50" class="time">14:50</a>
skvidalbut I'll wager dollars to donuts it's getting pulled in as a dep<a href="#t14:50" class="time">14:50</a>
f13looks like PyOpenGL.noarch, gnome-games.x86_64, pygtkglext.x86_64, totem*.x86_64, xorg-x11-drivers.x86-64<a href="#t14:50" class="time">14:50</a>
f13will debug farther<a href="#t14:51" class="time">14:51</a>
skvidalthanks<a href="#t14:51" class="time">14:51</a>
f13skvidal: I blame YOU!<a href="#t14:52" class="time">14:52</a>
f13lets kick this over to #fedora-devel<a href="#t14:52" class="time">14:52</a>
skvidalf13: excellent<a href="#t14:52" class="time">14:52</a>
skvidalokay<a href="#t14:52" class="time">14:52</a>
jwb?<a href="#t14:53" class="time">14:53</a>
* poelcat fills the silence<a href="#t14:56" class="time">14:56</a>
poelcat<a href="http://fedoraproject.org/wiki/QA/ReleaseCriteria">http://fedoraproject.org/wiki/QA/ReleaseCriteria</a><a href="#t14:56" class="time">14:56</a>
poelcatused to determine ship/noship of beta?<a href="#t14:57" class="time">14:57</a>
wwoodsused for all releases.<a href="#t14:57" class="time">14:57</a>
wwoodsbeta being non-final, "SHOULD" items can be ignored<a href="#t14:57" class="time">14:57</a>
* poelcat saw 2007-nov last change... wanted to make sure<a href="#t14:57" class="time">14:57</a>
wwoodssuggested updates are welcome<a href="#t14:58" class="time">14:58</a>
wwoodsbut nobody's suggested anything to me<a href="#t14:58" class="time">14:58</a>
poelcatlooks good to me... i just don't see how we can do it all to be ready on thurs<a href="#t14:59" class="time">14:59</a>
poelcatin light of current situation<a href="#t15:00" class="time">15:00</a>
wwoodswhy?<a href="#t15:00" class="time">15:00</a>
poelcatwwoods: as i understand it, we can't even start testing yet.  Am I missing something?<a href="#t15:03" class="time">15:03</a>
poelcattesting == verify to release critiera<a href="#t15:04" class="time">15:04</a>
wwoodswe have an updates.img<a href="#t15:05" class="time">15:05</a>
wwoodsand we've tested half of the stuff on there already<a href="#t15:05" class="time">15:05</a>
wwoodschanges in mkinitrd are not going to affect VNC<a href="#t15:05" class="time">15:05</a>
wwoodsso that testing is still valid<a href="#t15:05" class="time">15:05</a>
f13poelcat: we have to test, to see what's broken<a href="#t15:11" class="time">15:11</a>
f13we can't very well wait until nothing is broken to ... test<a href="#t15:11" class="time">15:11</a>
f13ok, ending the meeting so that work can continue.<a href="#t15:17" class="time">15:17</a>
-!- f13 changed the topic of #fedora-meeting to: Channel is used by various Fedora groups and committees for their regular meetings | Note that meetings often get logged | For questions about using Fedora please ask in #fedora | See <a href="http://fedoraproject.org/wiki/Communicate/FedoraMeetingChannel">http://fedoraproject.org/wiki/Communicate/FedoraMeetingChannel</a> for meeting schedule<a href="#t15:17" class="time">15:17</a>

Generated by irclog2html.py 2.3 by Marius Gedminas - find it at mg.pov.lt!