Re: [meta-virtualization] [PATCH 1/2] docker-proxy: add recipe for docker-proxy

Hi Bruce > >> > >> As I hinted, I'm going to figure out how to integrate / fix this in > >> the main docker recipe. > >> > >> Having the various SRCREVs managed in multiple recipes is a > >> maintenance pain and recipe for runtime errors. > >> > >> I'll dig into what the go class is doing that is

Re: [meta-virtualization] [PATCH 1/2] docker-proxy: add recipe for docker-proxy

On Mon, Apr 9, 2018 at 11:34 AM, Bach, Pascal wrote: > Hi Bruce > >> >> >> >> As I hinted, I'm going to figure out how to integrate / fix this in >> >> the main docker recipe. >> >> >> >> Having the various SRCREVs managed in multiple recipes is a >> >> maintenance pain

Re: [meta-virtualization] [m-c-s][PATCH 01/12] python-websockify: uprev to v0.8.0

All outstanding m-c-s and openstack patches are now merged Bruce On 04/04/2018 04:02 PM, Mark Asselstine wrote: This version is required by the stable/pike version of python-nova. Signed-off-by: Mark Asselstine --- .../python/{python-websockify_0.6.0.bb =>

Re: [meta-virtualization] [PATCH v2 0/8] xen: Xen vTPM stubdomains

Kurt, I've reviewed the patches today and all the improvements look good. Unfortunately, in performing a build with the patches applied to rocko, I encountered a link error when attempting: bitbake xen-vtpm Details and output are below. A separate minor thing I saw in patch 1 was that

[meta-virtualization] [m-c-s][PATCH] README: update code submission line to include "m-c-s" and '-M'

The READMEs were lacking the "[m-c-s]" which we normally expect on the mailing list as well as the use of the "-M" option which makes reviewing patches, which include a move as seen when we uprev a recipe, easier to review. Signed-off-by: Mark Asselstine ---

Re: [meta-virtualization] [PATCH 1/2] docker-proxy: add recipe for docker-proxy

On Fri, Apr 6, 2018 at 10:23 AM, Bach, Pascal wrote: > Hi Bruce > >> -Original Message- >> From: Bruce Ashfield [mailto:bruce.ashfi...@gmail.com] >> Sent: Freitag, 6. April 2018 15:48 >> To: Bach, Pascal (BT CPS R ZG FW CCP) >> Cc:

Re: [meta-virtualization] RFT/FYI: docker/containerd/runc uprevs pushed to master

Hello Bruce, Moved to master branch of Yocto. When I build I am getting below error. What does this mean? Initialising tasks: 100% |##| Time:

Re: [meta-virtualization] RFT/FYI: docker/containerd/runc uprevs pushed to master

Sure, but none of them are docker. Bruce On Mon, Apr 9, 2018 at 9:46 AM, Shakthi Pradeep (tpradeep) wrote: > Hello Bruce, > > I see pkg_postinst_${PN}() are part of below recipes…. > > TPRADEEP-M-91HW:meta-virtualization tpradeep$ grep -r postinst * >

Re: [meta-virtualization] RFT/FYI: docker/containerd/runc uprevs pushed to master

On Mon, Apr 9, 2018 at 4:37 AM, Shakthi Pradeep (tpradeep) wrote: > Hello Bruce, > > Moved to master branch of Yocto. When I build I am getting below error. What > does this mean? There were changes made to the way that postinstall scripts were run in the January timeframe,