From FedoraProject

Jump to: navigation, search

Fedora Release Engineering Meeting :: Monday 2008-01-07

IRC Transcript

-!- Irssi: #fedora-meeting: Total of 78 nicks [1 ops, 0 halfops, 0 voices, 77 normal] <a href="#t13:03" class="time">13:03</a>
poelcatf13: meeting today?<a href="#t13:03" class="time">13:03</a>
f13yeah<a href="#t13:05" class="time">13:05</a>
-!- f13 changed the topic of #fedora-meeting to: Fedora Release Engineering Meeting<a href="#t13:06" class="time">13:06</a>
f13ping notting jeremy jwb rdieter wwoods spot warren poelcat lmacken<a href="#t13:06" class="time">13:06</a>
jwbyo<a href="#t13:06" class="time">13:06</a>
warrenyo<a href="#t13:06" class="time">13:06</a>
* lmacken <a href="#t13:06" class="time">13:06</a>
* spot is heah.<a href="#t13:07" class="time">13:07</a>
rdieterword<a href="#t13:07" class="time">13:07</a>
-!- f13 changed the topic of #fedora-meeting to: Fedora Release Engineering - F9 Alpha!<a href="#t13:08" class="time">13:08</a>
f13yeah, freeze for Alpha is 8 days away.<a href="#t13:09" class="time">13:09</a>
warrenyet another secondary arch?<a href="#t13:09" class="time">13:09</a>
notting<klaxon starts sounding><a href="#t13:09" class="time">13:09</a>
f13my plan for today is to do a compose across the arches and see what pops as unresolvable deps<a href="#t13:10" class="time">13:10</a>
f13those we'll want to focus on getting fixed<a href="#t13:10" class="time">13:10</a>
nottingjwb: are you doing the ppc composes?<a href="#t13:10" class="time">13:10</a>
spoti'm going to do perl 5.10 soon.<a href="#t13:10" class="time">13:10</a>
warrenf13,  should we kick maintainers into fixing F8 > F9 issues?<a href="#t13:10" class="time">13:10</a>
spotsoon as in, today or tomorrow<a href="#t13:11" class="time">13:11</a>
jwbnotting, i believe that was the plan<a href="#t13:11" class="time">13:11</a>
f13warren: if you'd like.<a href="#t13:11" class="time">13:11</a>
warrenf13, I'm still on vacation<a href="#t13:11" class="time">13:11</a>
nottingbeyond unresolvable deps, do we have an idea as to what is completely hosed?<a href="#t13:11" class="time">13:11</a>
jwbhowever i wouldn't be opposed if f13 did some<a href="#t13:11" class="time">13:11</a>
jwbf13, do we have koji tags for this already?<a href="#t13:12" class="time">13:12</a>
f13no<a href="#t13:12" class="time">13:12</a>
f13we create the tag on Tuesday<a href="#t13:12" class="time">13:12</a>
nottingif we're not freezing, why do we need tags?<a href="#t13:12" class="time">13:12</a>
f13or more likely monday night.<a href="#t13:12" class="time">13:12</a>
jwbso you're just composing rawhide?<a href="#t13:12" class="time">13:12</a>
f13notting: we need a tag to compose from.<a href="#t13:12" class="time">13:12</a>
f13notting: it's a non-blocking freeze, we're not blocking rawhide from moving on<a href="#t13:12" class="time">13:12</a>
f13we're just taking a snapshot of it and updating as releng sees fit to get the alpha out<a href="#t13:13" class="time">13:13</a>
f13jwb: until tuesday yes.<a href="#t13:13" class="time">13:13</a>
nottingis it on releng to find new things that fix stuff, or people to ping releng?<a href="#t13:13" class="time">13:13</a>
f13notting: installer is pretty hosed right now.  url method dead, network on x86_64 dead (haven't tried ppc)<a href="#t13:13" class="time">13:13</a>
f13notting: both, and with QA involved.<a href="#t13:13" class="time">13:13</a>
jwbvideo is dead<a href="#t13:13" class="time">13:13</a>
f13yeah, X is not starting well during install<a href="#t13:13" class="time">13:13</a>
nottingaside from that, how was the play. mrs. lincoln?<a href="#t13:13" class="time">13:13</a>
f13and logging into X is pretty dead from GDM<a href="#t13:14" class="time">13:14</a>
f13at least logging into gnome<a href="#t13:14" class="time">13:14</a>
spotintel X is pretty much hosed up too<a href="#t13:14" class="time">13:14</a>
jwbgdm as a whole is dead<a href="#t13:14" class="time">13:14</a>
spotGL ops fail, and X won't restart cleanly<a href="#t13:14" class="time">13:14</a>
f13notting: so all in all we're in pretty good shape!<a href="#t13:14" class="time">13:14</a>
f13oh and we're missing a good chunk of firstboot due to things up in the air.<a href="#t13:15" class="time">13:15</a>
lmackenship it!<a href="#t13:15" class="time">13:15</a>
jwbf13, your compose configs are where again?<a href="#t13:16" class="time">13:16</a>
jwbpungi repo?<a href="#t13:16" class="time">13:16</a>
* jwb blames xmas for killing most of his braincells<a href="#t13:17" class="time">13:17</a>
f13jwb: yes, pungi repo.<a href="#t13:17" class="time">13:17</a>
f13conversely the live image configs are in the live repo<a href="#t13:18" class="time">13:18</a>
jwbaye<a href="#t13:18" class="time">13:18</a>
jwbf13, were you planning on using the quad to do composes or no?<a href="#t13:18" class="time">13:18</a>
f13so it's going to be a fun alpha.<a href="#t13:18" class="time">13:18</a>
f13jwb: if I'm going to do any ppc testing, sure.<a href="#t13:19" class="time">13:19</a>
jwbare you?<a href="#t13:19" class="time">13:19</a>
f13I wouldn't be opposed.<a href="#t13:19" class="time">13:19</a>
f13mostly I only have the ps3 left for ppc testing though<a href="#t13:19" class="time">13:19</a>
warrenwow<a href="#t13:19" class="time">13:19</a>
jwbunderstood.  if you make the isos available, i can give them to omar<a href="#t13:19" class="time">13:19</a>
f13yeah, I was hoping to upload isos in progress to koji.fp.o/releng/<a href="#t13:20" class="time">13:20</a>
jwbexcellent.  i'll also be doing some composes on my own, but you have about 2x the machine i do :)<a href="#t13:20" class="time">13:20</a>
f13heh<a href="#t13:20" class="time">13:20</a>
jwbat least until i get my new one<a href="#t13:20" class="time">13:20</a>
f13Seth also has a new createrepo for me to try out<a href="#t13:21" class="time">13:21</a>
f13so I'll be throwing that at the compose process too and trying to turn up any weirdness, which my useage set usually does<a href="#t13:21" class="time">13:21</a>
skvidaland it might be broken! :)<a href="#t13:21" class="time">13:21</a>
* skvidal goes back to lurking<a href="#t13:21" class="time">13:21</a>
f13lmacken will be handling the live image creations<a href="#t13:21" class="time">13:21</a>
lmackenindeed<a href="#t13:21" class="time">13:21</a>
jwblmacken, i assume you won't be doing ppc?<a href="#t13:22" class="time">13:22</a>
lmackenjwb: correct.. unless we want to do them, and I get access to a machine to do them on<a href="#t13:22" class="time">13:22</a>
jwbthat largely won't be a loss, as they were ppc32 IIRC<a href="#t13:22" class="time">13:22</a>
f13lmacken: you could have access to the quad<a href="#t13:23" class="time">13:23</a>
jwblmacken, as for access...  the quad or dwmw2 would gladly give you access :)<a href="#t13:23" class="time">13:23</a>
lmackencool, so if we want to spin them, I'd be happy to do so<a href="#t13:23" class="time">13:23</a>
f13the quad needs updating badly though.  I should do that soon<a href="#t13:23" class="time">13:23</a>
-!- f13 changed the topic of #fedora-meeting to: Fedora Release Engineering - FUDCon<a href="#t13:23" class="time">13:23</a>
f13I'll be at fudcon this weekend, willing to do either barcamp or hackfest stuff surrounding releng<a href="#t13:24" class="time">13:24</a>
f13I do want to have a bit of a hackfest to re-evaluate how we do rawhide and find some better ways of doing it<a href="#t13:24" class="time">13:24</a>
f13more robust, less hack-o-doom<a href="#t13:24" class="time">13:24</a>
f13also we have to really look at reversing the netapp stream and what that's going to mean for releng and associated groups like QA<a href="#t13:25" class="time">13:25</a>
jwbsomething like debian experimental, debian unstable, and debian stable?<a href="#t13:25" class="time">13:25</a>
f13jwb: no no, just the methodology we use to compose rawhide<a href="#t13:25" class="time">13:25</a>
jwboh good<a href="#t13:25" class="time">13:25</a>
f13jwb: it's all kinds of whacky<a href="#t13:25" class="time">13:25</a>
nottingthat's putting it mildly<a href="#t13:25" class="time">13:25</a>
f13but it "works" for now, which is why we haven't touched it much<a href="#t13:25" class="time">13:25</a>
nottingf13: although, is it really *that* different than how alpha/beta/final is composed, aside from being automated?<a href="#t13:26" class="time">13:26</a>
f13notting: there are some significant differences.<a href="#t13:26" class="time">13:26</a>
f13not that how we do the other composes is great mind you.<a href="#t13:26" class="time">13:26</a>
f13we really need koji run-root capability, but there are other things we can clean up in the mean time.<a href="#t13:26" class="time">13:26</a>
jwbfrom an outsider, the largest complication is that it does it all internally to the builder network<a href="#t13:27" class="time">13:27</a>
warrenrun-root meaning?<a href="#t13:27" class="time">13:27</a>
jwbwhich, of course, is the speedy part<a href="#t13:27" class="time">13:27</a>
nottingwarren: a way to run commands on another arch inside a mock-created chroot<a href="#t13:27" class="time">13:27</a>
f13warren: a koji process to run a specific command in a chroot created from a specific tag.<a href="#t13:27" class="time">13:27</a>
f13like say pungi<a href="#t13:28" class="time">13:28</a>
nottingbecause, wow, is pungify a horror<a href="#t13:28" class="time">13:28</a>
f13yes<a href="#t13:28" class="time">13:28</a>
f13notting: so perhaps we can sit down and clean up some of that this weekend.<a href="#t13:29" class="time">13:29</a>
f13you know, right before we freeze (:<a href="#t13:29" class="time">13:29</a>
nottingheh<a href="#t13:29" class="time">13:29</a>
-!- f13 changed the topic of #fedora-meeting to: Fedora Release Engineering - Open Discussion<a href="#t13:30" class="time">13:30</a>
f13Anything anybody would like to discuss?<a href="#t13:30" class="time">13:30</a>
jwbhow are we going to handle the alpha tagging?<a href="#t13:31" class="time">13:31</a>
jwbsend email to rel-eng saying "i tagged this"?<a href="#t13:31" class="time">13:31</a>
f13jwb: you mean releng people tagging things for the alpha?<a href="#t13:31" class="time">13:31</a>
jwbyes<a href="#t13:31" class="time">13:31</a>
f13We should use hte same methodology we did for previous freezes<a href="#t13:32" class="time">13:32</a>
f13if we do one ourselves that's not externally requested IRC would likely work OK too<a href="#t13:32" class="time">13:32</a>
nottingsubscribe rel-eng@fp.o to koji tag notifications :P<a href="#t13:32" class="time">13:32</a>
jwbi don't foresee a large problem.  just curious<a href="#t13:32" class="time">13:32</a>
f13notting: could do that.<a href="#t13:33" class="time">13:33</a>
f13at least for that tag<a href="#t13:33" class="time">13:33</a>
jwbexcept it doesn't tell you why<a href="#t13:33" class="time">13:33</a>
f13right<a href="#t13:34" class="time">13:34</a>
f13anything else?<a href="#t13:37" class="time">13:37</a>
wwoodsyeep. back<a href="#t13:37" class="time">13:37</a>
* wwoods reads scrollback quickly<a href="#t13:38" class="time">13:38</a>
f13wwoods: I'll wait.<a href="#t13:38" class="time">13:38</a>
wwoodsI don't think url installs are broken (I just did one, and other than the 'user' command in kickstart causing a traceback, it worked)<a href="#t13:39" class="time">13:39</a>
wwoods'course that means grubby didn't run, so it's not bootable...<a href="#t13:40" class="time">13:40</a>
wwoodsI'd really like to help straighten out the pungify / mash stuff. or at least help myself understand how we go from koji -> tree<a href="#t13:40" class="time">13:40</a>
wwoodsbut yeah, I'll be going into Release Testing Mode soon<a href="#t13:40" class="time">13:40</a>
wwoodsand bothering people about bugs that screw up the alpha release<a href="#t13:40" class="time">13:40</a>
f13wwoods: in boot.iso installs a sigsegv is thrown.<a href="#t13:42" class="time">13:42</a>
f13wwoods: it's a newt issue, that is already fixed upstream.<a href="#t13:43" class="time">13:43</a>
f13(upstream anaconda that is)<a href="#t13:43" class="time">13:43</a>
wwoodsgotcha<a href="#t13:44" class="time">13:44</a>
wwoodsthis was network (using already-existing grub)<a href="#t13:44" class="time">13:44</a>
wwoodsanyway, yeah. nothing amazingly important to say. standard "oh shit oh shit release time" drill<a href="#t13:44" class="time">13:44</a>
f13k<a href="#t13:45" class="time">13:45</a>
wwoodsI'll try to keep <a href=""></a> up to date<a href="#t13:45" class="time">13:45</a>
f13k<a href="#t13:45" class="time">13:45</a>
wwoodshopefully some of the hackfest time can go towards making that actually dynamic and automatic<a href="#t13:46" class="time">13:46</a>
wwoodsthat's all I got.<a href="#t13:47" class="time">13:47</a>
f13ok, if there's nothing else, ending in 30.<a href="#t13:47" class="time">13:47</a>

Generated by 2.3 by Marius Gedminas - find it at!