ReleaseEngineering/Meetings/2007-oct-29

From FedoraProject

Jump to: navigation, search

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

IRC Transcript

-!- f13 changed the topic of #fedora-meeting to: Fedora Release Engineering - Fedora 8 release meeting<a href="#t13:06" class="time">13:06</a>
* wwoods on the scene.. like a test machine<a href="#t13:07" class="time">13:07</a>
jeremypoelcat: ping<a href="#t13:07" class="time">13:07</a>
f13wwoods: how do we stand qa wise?<a href="#t13:07" class="time">13:07</a>
poelcatpresent<a href="#t13:07" class="time">13:07</a>
* poelcat just found a bug in slocate<a href="#t13:07" class="time">13:07</a>
poelcatit crashes<a href="#t13:07" class="time">13:07</a>
poelcatjeremy: pong<a href="#t13:08" class="time">13:08</a>
f13(I'm going to try and make this quick since I"m fighting compose issues)<a href="#t13:08" class="time">13:08</a>
jwbmy limited QA is pretty good<a href="#t13:09" class="time">13:09</a>
jwbbut i rarely test installs<a href="#t13:09" class="time">13:09</a>
jeremyas far as NetworkManager -- I talked with dcbw about half an hour ago, and the conclusion we came to is that unless we find something horrific, sticking with the current NM seems like the best approach.  he's working on getting gconf migration working, but that kind of scares me<a href="#t13:09" class="time">13:09</a>
wwoodsf13: stuff is mostly solid<a href="#t13:09" class="time">13:09</a>
jeremytoo many cases to easily test, if something goes wrong, it's likely to be a crasher, etc<a href="#t13:09" class="time">13:09</a>
warrenjeremy, without gconf migration, what happens to a user upgrading from FC6 or F7?<a href="#t13:09" class="time">13:09</a>
wwoodsother than the fact that we don't have an installable tree ATM<a href="#t13:10" class="time">13:10</a>
jeremywarren: they have to enter the settings for their network again.  which isn't great, but I'd rather that than it crashes on them<a href="#t13:10" class="time">13:10</a>
nottingof course, if on install they have to enter their settings again, that sort of defeats the point of adding migration later<a href="#t13:10" class="time">13:10</a>
jeremynotting: I'm not following you....<a href="#t13:11" class="time">13:11</a>
nottingjeremy: well, if you're going to make everyone who uses NM re-enter their config, adding migration of their old settings later isn't really going to help anyone<a href="#t13:11" class="time">13:11</a>
jeremynotting: helps release skippers!   also anyone that respins with updates<a href="#t13:12" class="time">13:12</a>
jeremynotting: honestly, if we'd had it two weeks I'd be jumping all over it.  but it's going to be a not small amount of code with lots of string munging written in C. sooo :)<a href="#t13:13" class="time">13:13</a>
jwbew<a href="#t13:13" class="time">13:13</a>
wwoodsso yeah, scanning the blocker list real quick-like<a href="#t13:15" class="time">13:15</a>
wwoodsso there's this standing bug where Turkish installs die<a href="#t13:15" class="time">13:15</a>
jeremywwoods: I did a turkish install successfully yesterday<a href="#t13:15" class="time">13:15</a>
wwoodswhich totally sucks but I don't think we can fix that in time... unless<a href="#t13:16" class="time">13:16</a>
wwoodsunless jeremy pulls a miracle out of his ass, I was about to say<a href="#t13:16" class="time">13:16</a>
wwoodset voila<a href="#t13:16" class="time">13:16</a>
warrenIt seems that the change in -37 made a HUGE difference for my iwl3945 on x86_64<a href="#t13:16" class="time">13:16</a>
wwoodsif I'm reading it right, we might have a fix for the AGP boot blocker<a href="#t13:16" class="time">13:16</a>
jeremywwoods: yep, there's a patch there.  the other two kernel bugs have patches too... I was going to track down davej/cebbert after this<a href="#t13:17" class="time">13:17</a>
* davej is invoked<a href="#t13:17" class="time">13:17</a>
wwoodsSELinux stuff seems mostly sorted, except the ps3 thing that magically appeared today<a href="#t13:17" class="time">13:17</a>
jeremywwoods: crontab is still broken by selinux<a href="#t13:17" class="time">13:17</a>
jwbmy biggest REGRESSION that i've found is the backlight stuff.  but like i said last week, it's not a blocker<a href="#t13:17" class="time">13:17</a>
warrenjwb, bug #?<a href="#t13:17" class="time">13:17</a>
jeremywwoods: trying to track down dwalsh (he's not in the office today), and also getting other people to check<a href="#t13:18" class="time">13:18</a>
jwbwarren, no bug yet.  i'm actually trying things myself<a href="#t13:18" class="time">13:18</a>
nottingi'm attempting to fix ppp. *sigh*<a href="#t13:18" class="time">13:18</a>
wwoodsjeremy: really? I thought that was fixed. bah and humbug<a href="#t13:18" class="time">13:18</a>
jwbwarren, like building a kernel without jeremy's thinkpad patch to see if it magically fixes it<a href="#t13:18" class="time">13:18</a>
poelcatcrontab doesn't work<a href="#t13:18" class="time">13:18</a>
jeremynotting: *sigh*<a href="#t13:18" class="time">13:18</a>
nottingjeremy: hey, it's beem broken since the end of june.<a href="#t13:18" class="time">13:18</a>
wwoodsoh, and are we gonna build crc32c into the kernel so iSCSI works?<a href="#t13:18" class="time">13:18</a>
jeremywwoods: I agree :/<a href="#t13:18" class="time">13:18</a>
jeremywwoods: that's one of the kernel bugs<a href="#t13:18" class="time">13:18</a>
davejI'll build it in, jcm seems to be on the hook for fixing it in mod-init-tools later.<a href="#t13:19" class="time">13:19</a>
wwoodsit's a grotesque hack but as long as we have a plan for getting rid of it, I'm OK<a href="#t13:20" class="time">13:20</a>
jeremythe blocker list is looking shockingly good right now<a href="#t13:21" class="time">13:21</a>
wwoodsis there a plan for the qla2xxx thing?<a href="#t13:21" class="time">13:21</a>
wwoodsjeremy: yeah, I think a couple of those are actually closeable too<a href="#t13:21" class="time">13:21</a>
wwoodsgnokii, f'rinstance, and the Turkish installs<a href="#t13:21" class="time">13:21</a>
jeremywwoods: we have the firmware packaged now.  not really handled properly by anaconda, but it was way too late hwen we found out about it to be able to fix it sanely :(<a href="#t13:22" class="time">13:22</a>
jeremywwoods: yeah, a number are in MODIFIED because I figure me investigating, fixing and closing is a tad too much ;-)<a href="#t13:22" class="time">13:22</a>
wwoodslemme know which ones you think can be retested / closed and I'll do so<a href="#t13:22" class="time">13:22</a>
wwoodsand/or throw them into NEEDINFO reporter<a href="#t13:23" class="time">13:23</a>
jeremywwoods: ones in MODIFIED should be pretty testable.  I don't think I fixed anything that wasn't trivially testable<a href="#t13:23" class="time">13:23</a>
wwoodsgotcha<a href="#t13:23" class="time">13:23</a>
wwoodsI'll check 'em out. so crontab/selinux sounds like it's the big thing we're waiting for<a href="#t13:24" class="time">13:24</a>
wwoods(and fixing rawhide to have images again)<a href="#t13:24" class="time">13:24</a>
jeremyyep<a href="#t13:24" class="time">13:24</a>
jeremyso, fingers crossed, tomorrow's rawhide should hopefully be able to be it<a href="#t13:24" class="time">13:24</a>
wwoodsa couple of people are pissy about firewire not working, but.. not a regression from F7, small number of users, planned fix for F9 (maybe an F8 update), and available workarounds<a href="#t13:25" class="time">13:25</a>
wwoodserr, amend that: firewire not working with iso devices (cameras etc) and OHCI 1.0 controllers<a href="#t13:25" class="time">13:25</a>
jeremy*nod*<a href="#t13:25" class="time">13:25</a>
wwoodsrahul added the NV nosuspend change to the common bug page - we might want a whitelist or something in the future<a href="#t13:26" class="time">13:26</a>
wwoodsbut I assume we can push out future pm-utils updates to handle something along those lines once we figure out what works<a href="#t13:26" class="time">13:26</a>
jeremywell, I'd rather that we fix the driver and then just pull the hack rather than trying to do a whitelist ;)<a href="#t13:26" class="time">13:26</a>
wwoodsone thing that worries me is longstanding bugs with the updates to libata etc<a href="#t13:26" class="time">13:26</a>
wwoodspeople who were not updating to F7 because it didn't work on their hardware<a href="#t13:27" class="time">13:27</a>
wwoodsif it still doesn't work with F8, they're kind of in trouble<a href="#t13:27" class="time">13:27</a>
warrenhow widespread?<a href="#t13:27" class="time">13:27</a>
warrenwwoods, do we have any such boxes, or did somebody test it?<a href="#t13:28" class="time">13:28</a>
wwoodsspotty - mostly seems to affect subsets of people with old hardware + wonky drives<a href="#t13:28" class="time">13:28</a>
jeremywwoods: I suspect there's not much we can do there<a href="#t13:28" class="time">13:28</a>
wwoodsor things we don't have hardware to test (intel dmraid)<a href="#t13:28" class="time">13:28</a>
jeremypeter is looking at the dmraid one now<a href="#t13:28" class="time">13:28</a>
wwoodsI agree that there's not much we can do for the old hardware case but dmraid worries me more<a href="#t13:28" class="time">13:28</a>
jeremy(he wasn't able to reproduce when using intel dmraid last week, but is trying again)<a href="#t13:29" class="time">13:29</a>
warrendmraid bug #?<a href="#t13:29" class="time">13:29</a>
wwoodsalan pointed out some raid+libata bugs but those turned out to mostly be mdraid<a href="#t13:29" class="time">13:29</a>
jeremywarren: 349161<a href="#t13:29" class="time">13:29</a>
wwoodswarren: <a href="https://bugzilla.redhat.com/show_bug.cgi?id=349161">https://bugzilla.redhat.com/show_bug.cgi?id=349161</a> is the blocker one<a href="#t13:29" class="time">13:29</a>
wwoodsthere's some other similar things in need of investigation at the bottom of <a href="http://fedoraproject.org/wiki/Bugs/F8Common">http://fedoraproject.org/wiki/Bugs/F8Common</a><a href="#t13:30" class="time">13:30</a>
wwoodsoh, if there's anything on that page that's fixed now, lemme know<a href="#t13:30" class="time">13:30</a>
* wwoods eyes "NetworkManager Segmentation Faults" and "kernel does not boot on SK8V motherboards" suspiciously<a href="#t13:31" class="time">13:31</a>
nottingisn't sk8v the same agp bug?<a href="#t13:32" class="time">13:32</a>
jeremythe former I haven't seen in a long while... the latter is the agp kernel bug and davej says he's going to add the patch<a href="#t13:32" class="time">13:32</a>
wwoodsnotting: yes<a href="#t13:32" class="time">13:32</a>
wwoodsoh, I've been testing yum upgrades from f8t3 to rawhide (we said we'd provide help/docs for people to do that) and adding stuff to <a href="http://fedoraproject.org/wiki/Tools/yum/YumUpgradeFaq">http://fedoraproject.org/wiki/Tools/yum/YumUpgradeFaq</a><a href="#t13:33" class="time">13:33</a>
wwoodsso if anyone asks, that's where the information lives<a href="#t13:33" class="time">13:33</a>
* wwoods done<a href="#t13:34" class="time">13:34</a>
davejnotting: not entirely sure the sk8v bug is the same cause as the agp bug.<a href="#t13:34" class="time">13:34</a>
warrenSwitching from wired to wireless nm-applet crash was fixed?<a href="#t13:35" class="time">13:35</a>
jeremywwoods: I'll take a look at the raid/lvm bugs at the bottom of F8Common as soon as I get a livecd-tools with all the currnet configs built<a href="#t13:35" class="time">13:35</a>
jeremywarren: I can't reproduce a crash trying with today's rawhide<a href="#t13:35" class="time">13:35</a>
jeremyI switched back and forth and back and forth and ...<a href="#t13:35" class="time">13:35</a>
wwoodswarren: should be fixed, I'll be testing it in a sec<a href="#t13:35" class="time">13:35</a>
wwoods(waiting for powerbook to reboot)<a href="#t13:36" class="time">13:36</a>
jeremyanyway, do we have anything else?  or just keep trucking and fixing stuff<a href="#t13:37" class="time">13:37</a>
jeremyand when do we want to reconvene?<a href="#t13:37" class="time">13:37</a>
warrensame time tomorrow?<a href="#t13:38" class="time">13:38</a>
nottinggoing to conflict with board .maybe slightly later?<a href="#t13:38" class="time">13:38</a>
* jeremy is flexible...<a href="#t13:40" class="time">13:40</a>
wwoodsoh hey, I have a question / discussion topic: should we remove old test release torrents after a certain time?<a href="#t13:43" class="time">13:43</a>
wwoodsgetting tired of people installing f8t3 and reporting bugs against that<a href="#t13:43" class="time">13:43</a>
jeremywe should do some torrent cleanup after the release<a href="#t13:43" class="time">13:43</a>
wwoodsboth bugs in outdated packages and filing them against the version 'f8test3'<a href="#t13:43" class="time">13:43</a>
jeremyalthough also, we're going to start hopefully having people hit 'torrent.fedoraproject.org' directly a little less too<a href="#t13:43" class="time">13:43</a>
* mmcgrath agrees, possibly looking at a redesign of the torrent page would be good and finding a good home for the videos.<a href="#t13:44" class="time">13:44</a>
jeremymmcgrath: fedoraproject.org/Videos with nicer links ?<a href="#t13:44" class="time">13:44</a>
jeremybut neither here nor there<a href="#t13:44" class="time">13:44</a>
mmcgrath<nod> something.<a href="#t13:45" class="time">13:45</a>
warrenI do not like green eggs and ham.<a href="#t13:45" class="time">13:45</a>
nottingwould you like them with a mouse?<a href="#t13:46" class="time">13:46</a>
wwoodssomething to discuss in-depth at a later time, but yeah. really tired of people installing 4-week-old bits and telling me they're broken.<a href="#t13:46" class="time">13:46</a>
wwoodswell, yeah dude, we spent the past 4 weeks fixing those bits. except it's harder for you to get those bits. anyway. I'm flexible for meeting time tomorrow<a href="#t13:46" class="time">13:46</a>
warrenMeeting tomorrow at undisclosed time, at undisclosed location<a href="#t13:47" class="time">13:47</a>
jeremyhow about 2?<a href="#t13:47" class="time">13:47</a>
warrensounds good<a href="#t13:47" class="time">13:47</a>
nottingwfm<a href="#t13:47" class="time">13:47</a>
jeremy2 pm tomorrow it is<a href="#t13:48" class="time">13:48</a>
poelcatjeremy: what is ck-list ?<a href="#t13:50" class="time">13:50</a>
jeremypoelcat: lists sessions according to console kit<a href="#t13:51" class="time">13:51</a>
poelcatjeremy: and why severity "low" ? sound is completely broken<a href="#t13:51" class="time">13:51</a>
poelcatjeremy: i removed it!<a href="#t13:51" class="time">13:51</a>
poelcati don't want it :)<a href="#t13:51" class="time">13:51</a>
jeremyif you remove console kit, then you don't get console permissions!<a href="#t13:51" class="time">13:51</a>
jeremyduh!<a href="#t13:51" class="time">13:51</a>
wwoodswe ignore priority and severity on bug reports<a href="#t13:52" class="time">13:52</a>
wwoodsset them to whatever the fuck you like<a href="#t13:52" class="time">13:52</a>
poelcati thought consolekit was all about changing users?<a href="#t13:52" class="time">13:52</a>
poelcati'm the only user; I don't want it :)<a href="#t13:52" class="time">13:52</a>
jeremyno, it's not<a href="#t13:52" class="time">13:52</a>
f13oh wow, forgot this was still going :/<a href="#t13:52" class="time">13:52</a>
f13poelcat: there is root.<a href="#t13:53" class="time">13:53</a>
f13poelcat: that's another user.<a href="#t13:53" class="time">13:53</a>
* jeremy takes away poelcat's blocker filing privileges ;-)<a href="#t13:53" class="time">13:53</a>
poelcathey what about crontab ?<a href="#t13:54" class="time">13:54</a>
wwoodsyou wilfully removed random system packages that you didn't understand, and then filed a bug when stuff broke, and *then* added that bug to the blocker list?<a href="#t13:54" class="time">13:54</a>
wwoodsyou now owe me a beer<a href="#t13:54" class="time">13:54</a>
jeremypoelcat: crontab is still being looked into<a href="#t13:54" class="time">13:54</a>
poelcatwwoods: or you owe me a better page explaiing why I need consolekit<a href="#t13:54" class="time">13:54</a>
poelcati only disabled the service :)<a href="#t13:55" class="time">13:55</a>
wwoodsno<a href="#t13:55" class="time">13:55</a>
wwoodsheh<a href="#t13:55" class="time">13:55</a>
f13ConsoleKit is a system daemon for tracking what users are logged<a href="#t13:55" class="time">13:55</a>
f13into the system and how they interact with the computer (e.g.<a href="#t13:55" class="time">13:55</a>
f13which keyboard and mouse they use).<a href="#t13:55" class="time">13:55</a>
poelcatf13: okay :) it was advertised in our last release as a snazzy way to change users on the fly<a href="#t13:57" class="time">13:57</a>
poelcati thought that was its only benefit<a href="#t13:57" class="time">13:57</a>
f13no no, it just /supports/ the bits that allow you to choose users<a href="#t13:57" class="time">13:57</a>
wwoodsit handles the backend bits, like changing the owner of the console devices (sound, keyboard, mouse, etc) to the person who is currently logged in<a href="#t13:57" class="time">13:57</a>
f13without ConcoleKit you can't do fast user switching, but it doesn't do the switching for you thats fast user switcher.<a href="#t13:57" class="time">13:57</a>
f13ConsoleKit and PolicyKit just take care of assigning ACLs where they need to be for access to hardware.<a href="#t13:57" class="time">13:57</a>
jeremypoelcat: that's fast-user-switching.  not consolekit<a href="#t13:57" class="time">13:57</a>
* poelcat now understands why yum remove ConsoleKit looked so ugly (I didn't do it btw)<a href="#t13:57" class="time">13:57</a>
* poelcat stops being confused :)<a href="#t13:58" class="time">13:58</a>
poelcatso.... is updatedb failing a blocker?<a href="#t13:58" class="time">13:58</a>
* poelcat has caused enough trouble today... why not<a href="#t14:00" class="time">14:00</a>
mmcgrathpoelcat: is it selinux?<a href="#t14:00" class="time">14:00</a>
jeremypoelcat: updatedb just worked for me<a href="#t14:00" class="time">14:00</a>
poelcatjeremy: does it need ConsoleKit too? ;-)<a href="#t14:00" class="time">14:00</a>
poelcati'm trying to run a slimmed down system here... 1G of ram isn't what it used to be :)<a href="#t14:01" class="time">14:01</a>
* wwoods running on 640MB<a href="#t14:04" class="time">14:04</a>
jeremypoelcat: what's the bug #?<a href="#t14:09" class="time">14:09</a>
poelcatjeremy: bug 357061<a href="#t14:14" class="time">14:14</a>
jeremypoelcat: based on the strace, looks like something specific in your home directory (since that's where it's scanning at that point)<a href="#t14:21" class="time">14:21</a>
f13hrm.<a href="#t14:45" class="time">14:45</a>

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