Bruce, Thanks for the fast turn on these fixes, there are pulled into master and the 1.0 M2 branch. Sau!

Mark, go ahead and submit it, so that we can have it available, and can make the call, there is clearly going to be a rebuild of M2 due to the kernel failures, but I am not sure that I want to bring

fakeroot doesn't intercept or alter fopen(). It'd be better to test something that is actually affected by fakeroot for a comparison. :) fakeroot only traps things like stat and chmod, pseudo

Pending Patch is in distro Stage Phase one status was best effort on the the update list, and I will have a summary later this week. All recipes now have SRC_URI Checksums, the checking work is part

I'd second Scott's opinion here. I wasn't marking my bugs as verified, since as a submitter, I've never had to do this in 10+ years in the 'biz'. Cheers, Bruce

I have now verified all my bugs. However, the process doesn't seem right to me. As the person who fixed the bug, presumably I performed verification that my fix actually works, which is why I marked

I have the work done and tested. Is it too late to submit this? (There are no code changes, just recipe Description/Summary changes..) The write up is done, and outside of the tree.. I just have to

I believe that this is part of the fundamental differences between fakeroot and pseudo. Fakeroot only persists data on shutdown, while pseudo does persistence during the read/writes. What I'm

Yes, SDK is generated from the distro metadata, which however doesn't prevent SDK as a standalone component to have its own version variable. We can have: SDK_VERSION = ${DISTRO_VERSION} or,

Got it. I'm not an export on Bugzilla. Perhaps Kangkang can have some comment whether this is feasible. It looks a good thing though. :-) Thanks Kevin

I rebased the previous patch of adding package of environment files to be compatible with the new cross-canadian.bbclass Pull URL: git://git.pokylinux.org/poky-contrib.git Branch: llu/bug565

Of course, but I can only create a saved search for myself (and I now have that). However, I was assuming the bugzilla admin could create a search which would show the logged in user all of their

I disagree, I think it's definitely useful to know which distribution version your SDK is built against. In fact as the SDK components are generated from the distro metadata introducing an extra

I tried to CC all the owners in original mail, which however ended up to need moderation because too many recipients. (not sure why only Saul is kept. :-)) So please take a look on below list to make

You should be able to save that search under your account directly... :-) Thanks Kevin

Hi, owners, Since M2 code frozen happened last week and now M2 test has been started, could owners of each M2 sprint tasks update the latest status on the

I've just gone through and verified the bugs I've filed. I think we could make this process easier to remember if we had a shared saved search "bugs I need to verify"? Cheers, Joshua -- Joshua Lock

Added package of meta-environment-${TARGET_ARCH} for environment files. Signed-off-by: Lianhao Lu <lianhao.lu@...> --- meta/classes/toolchain-scripts.bbclass | 32 ++++++++++

Hi, I hate to raise this question, but there is still bunch of bugs that is fixed but not verified. According to the process, it is reporter's responsibility to verify the bug, so could I ask the

Hi distro team, Saul, Jessica and I have a triage bug meeting to scrub the bugs, and here is the bug list ahead of us. Let's spent some time to reduce the bug number. Thanks for the great