[yocto] Adding SSL support to RabbitMQ Server 3.2.4

Hi, rookie here. I'm trying to enable SSL for RabbitMQ Server 3.2.4 on pyro. Without modifying the build, I simply created /etc/rabbitmq/rabbitmq.config with the following entries: [ {rabbitmq_management, [ {listener, [{port, 15671}, {ip, "0.0.0.0"},

[yocto] Demos for the Yocto Project booth at ELCE in Edinburgh

Dear all, As usual, the Yocto Project will have a booth at the ELCE conference in Edinburgh next month. While the booth is a great opportunity for everyone to get a new sticker of your favorite project ;-) we are also very excited when developers from our community get a chance to show off the fun

[yocto] Yocto Project Status WW38’18

Current Dev Position: YP 2.6 M3. - This is feature freeze for YP 2.6! Next Deadline: YP 2.6 M3 Build Target is Aug. 27, 2018 SWAT Team Rotation: · SWAT lead is currently: Tracy · SWAT team rotation: Tracy-> Armin on Sept. 21, 2018 · SWAT team rotation: Armin -> Chen on

Re: [yocto] [meta-security][PATCH] keynote: depend on openssl10

On 09/12/2018 01:09 AM, Yi Zhao wrote: > Signed-off-by: Yi Zhao > --- > recipes-security/keynote/keynote_2.3.bb | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/recipes-security/keynote/keynote_2.3.bb > b/recipes-security/keynote/keynote_2.3.bb > index 0300894..6ec26b8

Re: [yocto] [meta-security][PATCH] keyutils: Fix build with usrmerge

On 09/16/2018 11:59 AM, Alex Kiernan wrote: > Update BINDIR and SBINDIR so keyutils builds with usrmerge > > ERROR: keyutils-1.5.10-r0 do_package: QA Issue: keyutils: Files/directories > were installed but not shipped in any package: > /sbin/key.dns_resolver > /sbin/request-key > /bin/key

Re: [yocto] Demos for the Yocto Project booth at ELCE in Edinburgh

On 09/18/2018 06:29 AM, Nicolas Dechesne wrote: > Dear all, > > As usual, the Yocto Project will have a booth at the ELCE conference > in Edinburgh next month. While the booth is a great opportunity for > everyone to get a new sticker of your favorite project ;-) we are also > very excited when

Re: [yocto] [pseudo] Pseudo 1.8+ xattr sqlite corruption

> > On Wed, 2018-08-22 at 14:54 +, jack.f...@dell.com wrote: > > > So failure mode is the target filesystem is devoid of SELinux file > > > contexts, all files are unlabeled_t, which pretty much breaks > > > everything in enforcing mode. So whatever the corruption > > > cause/effect in the

[yocto] Native yocto compile in docker container without cross compile

Hi,  I am wondering, there does not seem to be any information about native compile of projects in a Yocto docker container. It seems that most of the people use cross compile even though that imho is not necessary if your target is x86 too. So here is what I want to do: - Create a docker contain

Re: [yocto] [pseudo] Pseudo 1.8+ xattr sqlite corruption

On Tue, 18 Sep 2018 20:26:59 + wrote: > SO... any suggestions how to make the inodes in the database an > UNSIGNED value? We probably *can't* -- sqlite doesn't support that! They cap out at 8 byte integer values, and are always signed. I don't know of a way to fix this. We might be able to t

Re: [yocto] [pseudo] Pseudo 1.8+ xattr sqlite corruption

On Tue, Sep 18, 2018, 16:09 Seebs wrote: > On Tue, 18 Sep 2018 20:26:59 + > wrote: > > > SO... any suggestions how to make the inodes in the database an > > UNSIGNED value? > > We probably *can't* -- sqlite doesn't support that! They cap out at 8 > byte integer values, and are always signed.

Re: [yocto] [pseudo] Pseudo 1.8+ xattr sqlite corruption

On Tue, 18 Sep 2018 16:16:22 -0500 Joshua Watt wrote: > Are the databases supposed to be shareable between different build > machines? IIRC, the answer is no. Could you store the native inode > type as a sqlite BLOB? Not necessarily a good idea Just an idea. I think coercing the values into