From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6517147827419742208 X-Received: by 10.28.237.21 with SMTP id l21mr3331995wmh.32.1517396129886; Wed, 31 Jan 2018 02:55:29 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 10.28.214.21 with SMTP id n21ls1011901wmg.0.canary-gmail; Wed, 31 Jan 2018 02:55:29 -0800 (PST) X-Google-Smtp-Source: AH8x2268r6/OxxIH2vdi69kk83Ecl+LPwcI7W5kncA/F3M8/IBK/GWPVgWlPHTKre5kVPk9YYLfY X-Received: by 10.28.1.2 with SMTP id 2mr493519wmb.5.1517396129306; Wed, 31 Jan 2018 02:55:29 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1517396129; cv=none; d=google.com; s=arc-20160816; b=uiKKU2datge8piawIC6sy2xxu8kdgh5yY1FIXw93BZfFxCmpVGlaoWz/O3gX8Af7Bt CHg91/7OfT9NxeCZV5faMDW4rrOutr/8veJz9n0G/Sj5NKnRjlhNNUc/kZcdJEMhAJso p8DiQmPHM9Z4cHVYhv4rvKFRcR9P7CSg4kazrWCjiBV33dC7t8IYHYB+S98VK8psPxBg 0ScpPDDUgpKZJ5ZMPQ7ia7TcxlmQniUEJNGIKAsvusO+RnFAp9fPSTxJFtI9NJh/+2D5 LaBrS/3pOj7NpCBTbm+sfk7s0iK/U4mTIw+erz+jqbNs21XW5ALugjjAVqET9man97va N+6A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:content-language:in-reply-to:mime-version :user-agent:date:message-id:from:references:to:subject :arc-authentication-results; bh=d264A8QM7VSH3fjA463echEPGe5ckAZANGs/YViRqaw=; b=xx5smkLq7mjkT75kcXMdhx2ccTpiqhlGC6vW+2MzZ6O92PYCx25/LeIoKHt4iwMEQn bl6YK+CcxI1ARrMtyGTtdpbkNE83X9EsQrbYnGtAUuGb1EYm83EO7iPMmC66SChuyJIt G1IU3QtPJ+DQNRCoAXr+m+eyWjaCmycEHNTHgSMam8Rv1w5n/+fQFTgAl0aZgB2CvwjH aJxtvE+7a+qeCXxLPuX0eJbtACCyxzH4ei+egyecHaz+kyU5VRHck0ovDY2dBsPC6WKK r48rmH4Ykz33q499NCjbY63fjx1unsZMSElaA9OwD9KxF5BJ1cYF2Npw8yxyMOieQVNM ROaw== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com Return-Path: Received: from david.siemens.de (david.siemens.de. [192.35.17.14]) by gmr-mx.google.com with ESMTPS id b10si1092756wmc.0.2018.01.31.02.55.29 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 31 Jan 2018 02:55:29 -0800 (PST) Received-SPF: pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.14 as permitted sender) client-ip=192.35.17.14; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by david.siemens.de (8.15.2/8.15.2) with ESMTPS id w0VAtSbW023650 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 31 Jan 2018 11:55:28 +0100 Received: from [167.87.41.49] ([167.87.41.49]) by mail1.siemens.de (8.15.2/8.15.2) with ESMTP id w0VAtRfY019669; Wed, 31 Jan 2018 11:55:28 +0100 Subject: Re: [PATCH 9/9] wic: now truly go for the wic version we claim to have To: Alexander Smirnov , Henning Schild , isar-users@googlegroups.com References: <540bb04ce24f67c121c83801288a3aea6f4cedac.1517390790.git.henning.schild@siemens.com> From: Jan Kiszka Message-ID: <9882db52-7c2e-d135-2ca5-13c5b9a722a7@siemens.com> Date: Wed, 31 Jan 2018 11:55:27 +0100 User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.8.1.12) Gecko/20080226 SUSE/2.0.0.12-1.1 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-TUID: vzf65R32wq3J On 2018-01-31 11:11, Alexander Smirnov wrote: > On 01/31/2018 12:42 PM, Henning Schild wrote: >> 2b164b18fd639c9 claims to introduce wic hash 131629ca6238ea05 >> This commit really carries that version of wic. >> >> Issue: >>   - the wic version in Isar was modified >>   - that causes: >>    - confusion, maintainability and updateability issues >>    - potential quality issues >> >> Impact: >>   This patch and the previous reverts get wic back to a state where all >>   these Issues are solved. We could now just update our wic without >> having >>   to worry about local patches. In case of a wic-update Isar and layers >>   on top would still have to review their plugins. > > Does upstream wic script rely on the content from lib/plugins? > > For example some recent commit updates both: > > https://github.com/openembedded/openembedded-core/commit/00420ec42140c1b752132bda190dede85756d157#diff-df4a70bc146d3159891d7a410f2521a1 > > > So due to customized plugins below we should worry and keep this in mind. Sure, we have to keep an eye on wic<->plugin API changes when updating wic to the next upstream version. Nothing new, though, when you write plugins for wic (like we do for firmware update mechanisms, also over Yocto). Jan -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux