FWIW, I own a rpi b+ that I use to automate things in my house and it works just fine. I'm not aware of any specifics... Just get the meta-raspberrypi layer from [1] and follow the instructions in

>Hi, > >I have flipped the "current" and "latest" symlinks on the server that contains >the published YP docs such that "current" now points to the 1.7 release and >"latest" points to a new "tbd"

Hi, I have flipped the "current" and "latest" symlinks on the server that contains the published YP docs such that "current" now points to the 1.7 release and "latest" points to a new "tbd" area.

Hi, I am interested in using oe to crossbuild stuff for raspberry pi b+, and I wondered if someone already achieved to do this? From what I read there are some specifics to deal with, can

There isn't currently a roadmap. I'm currently just trying to get v0.3.0 out the door as it's dragged on a lot longer than I'd planned. I'm probably going to aim for shorter, smaller development

I've merged this to opkg-utils, many thanks! I'm about to send a patch for openembedded-core which updates the opkg-utils SRCREV to use this new commit. -- Paul Barker Email:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, The latest release of the Yocto Project 1.7 (dizzy-12.0.0) is now available for download

Insalling packages using update-alternatives will give the following error lines: sed: -e expression #1, char 41: unterminated address regex sed: -e expression #1, char 42: unterminated address

Thanks Ross, but no sticky bits :( It's actually the group of the patched files that gets changed to root and not the owner (sorry). michael#/opt/oe/build/tmp/work-shared/gcc-4.8.2-r0/gcc-4.8.2$

Check for sticky bits on directories such as /opt or /opt/oe. Ross

I will look into that, could be that the code in the fetcher is not catching opkg correctly, we are working on updating that code to do a better job. Thanks, saw your email earlier, thanks your hard

This mail was sent out by Package Report System. It will list all the recipes which can't check upstream version by script, and will show how long it is since their last mannual version check. You can

This mail was sent out by Package Report System. This message list those recipes which need to be upgraded. If maintainers believe some of them needn't to upgrade this time, they can fill in

I will take pinentry. - Armin

I'm getting a lot of warnings of copyfile: failed to chown/chmod

I don't see opkg, opkg-utils or libarchive in those emails or on http://packages.yoctoproject.org/upgradepkgname. Any particular reason they're missing? I'll send an upgrade to opkg v0.2.3 tomorrow,

I guess you can put me up for python3 recipes and all of toolchain related ones.

Folks, Just a reminder now that master is open again for patches, now is a great time to consider doing package Updates. Based on some rough estimates from 1.7 we did around 300 updates from 34

Hi Paul, I too wanted to express my thanks to you for this work! Is there a roadmap for opkg somewhere? Best regards, Trevor

I'm actively using meta-golang for development and continuing to add features as I find them necessary. If anyone has suggestions on what would be useful as a developer of embedded go applications,