Feb24th IRC LOG

<pidge> Hi everyone. We're going to start our scheduled bug scrub now. This should last for about 30 to 45 minutes but we can go over that if needed. This is our last bugscrug of the master stabilization cycle and is in preparation for our release candidate spin this weekend. First though, if you're here for the bugscrub could you please check in for my logs with a quick pong.
<lianhao> pong
<dongxiao> pong
<dcui-mobl> dcui(Dexuan): pong
<yuke> pong
<qhe> pong
<sgw> ping/pong
<pidge> sgw will be with us momentarily. As of a few minutes ago we have a total of 89 open defects targets for 1.0 http://tinyurl.com/483l86z
<pidge> ah, and there is sgw
<pidge> that is out of a total of 140 open defects
<Jefro> Hi all - glad to see that a nice game of ping pong is happening when there are bugs to be squished
<pidge> hi jefro!
<Jefro> hi! I'm only here for a few minutes to lend some moral support
<pidge> let's go down the list in priority: #649: edwin QEMU segfaults with nographic option. updates?
<sgw> pidge: edwin does not appear to be on
<sgw> correction, he is on, but not in
<sgw> gzhai: ping
<pidge> ah, you're right. qhe: 443, any updates?
<qhe> pidge: this should be related to bug 722 if not duplicated
<qhe> pidge: there is a mail sent out for disucussion for the zypper situation
<qhe> pidge: currently ppc zypper bugs are put a little on hold and am looking at the x86_64 ones

• RamD_ (7371ea2d@gateway/web/freenode/ip.115.113.234.45) has joined #yocto
• RamD_ (7371ea2d@gateway/web/freenode/ip.115.113.234.45) has left #yocto
• RamD_ (7371ea2d@gateway/web/freenode/ip.115.113.234.45) has joined #yocto

<pidge> ok, qhe. Could you send that email out to the yocto list. it has a limited distribution. Also, as a reminder for folks, with the upcoming release cycle, we are technically in feature freeze. Bugfixes can only go in until the 11th, unless they are show stoppers. Our code freeze date is March 18th.
<qhe> pidge: that mail is in the internal yocto list
<pidge> qhe: 735 is a new one. any status on it?
<qhe> pidge: no update
<pidge> ok, 709?
<pidge> qhe: and has 710 been verified as fixed?
<pidge> sgw: any updates on 712?
<qhe> pidge: patch for 710 is at my local tree
<qhe> pidge: 709 doesn't have problems any more, but the `fix' is better delayed to next upgrade cycle
<qhe> pidge: btw, 710 isn't triggered for now, the `fix' is to fix the underlying problem, not the symtons
<pidge> qhe: on 710 I think RP already patched this? http://git.pokylinux.org/cgit.cgi/poky/commit/?id=293b023361580cdf41cf8aa0d8e96fd9c380e424
<qhe> pidge: that patch hides the problem, the mirror bug is a separate one
<pidge> ah, ok. Could you update the bug to that effect?
<qhe> pidge: my patch is to fix the SRC_URI to the right one
<qhe> pidge: it _is_ the right one

• Jefro has quit (Quit: Leaving.)

<qhe> pidge: rather, RP's fix should have a new bug related to it
<qhe> pidge: I mean, the bug summary: "attr recipe points at wrong source tarball address" reflects exactly what's wrong
<qhe> pidge: although it's just exposed during the mirror bug
<pidge> ok, thank you, now I get it. That takes us out of all the High bugs for folks here. dongxiao: 442 any updates?
<pidge> whoops, sorry, dcui-mobl rather
<dcui-mobl> pidge: hi
<pidge> hi dcui-mobl: any updates on 442?
<dcui-mobl> pidge: sorry, I was not here for a while...
<pidge> that's ok.
<dcui-mobl> pidge: no actual update
<dcui-mobl> pidge: I'm still debugging...
<pidge> ok. now dongxiao: 660, any updates on this?
<dongxiao> pidge: the bug is root caused as stated in the comments. It is configuration related with poky-image-minimal. Need confirmation from RP or sgw.
<pidge> ok, could you sync up with RP__ or sgw and get confirmation then?
<dongxiao> pidge: sure
<pidge> ok, next one is mine: 680 and I have no updates I'm going to look at this next week.

• mckoan|away is now known as mckoan
• mckoan has quit (Changing host)
• mckoan (~marco@unaffiliated/mckoan) has joined #yocto

<pidge> is ke online?
<yuke> pidge: yes
<pidge> hi! 529: any updates on this?
<yuke> for bug 529, can not reproduce in 1.0, and look it is 0.9 bug.i am still trying to reproduce it in 0.9
<yuke> just one question, for such kind of bug, should we go further to fix for 0.9?
<sgw> yuke: if you can reproduce it for 0.9 but not for 1.0, then it's OK to say it's fixed in 1.0
<pidge> If you're not able to reproduce it for 1.0, I'd leave it open for now but put a note that says you were not able to reproduce it in 1.0
<pidge> or what sgw said :)
<sgw> as "worksforme" with the note that it works in 1.0!
<yuke> Ok, i will try it in 0.9, and update the note
<yuke> pidge: for the rest bugs, no updates yet
<pidge> yuke: I wouldn't bother with it right now. 1.0 code freeze is 2 weeks or so away.
<yuke> pidge: :) and i am comfortable to fix those bugs in 1.0 timeframe
<pidge> ok, thank you yuke. is liping around?
<yuke> liping is annual leave this afternoon

• sgw slinks off, good night all (pidge let's talk in the morning)

<pidge> yuke: :) ok. then we a whole bunch of zypper defects which we've already went over.
<pidge> which leaves us at lows. And as it's 11:45 here, I think that concludes our bugscrub unless anyone has anything else?
<yuke> pidge: nothing from me