From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6517147827419742208 X-Received: by 10.223.176.235 with SMTP id j40mr2357109wra.27.1517406463194; Wed, 31 Jan 2018 05:47:43 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 10.28.116.12 with SMTP id p12ls1087934wmc.2.gmail; Wed, 31 Jan 2018 05:47:42 -0800 (PST) X-Google-Smtp-Source: AH8x225O5qEVY7WV+nP4SlC2Q5meWpxQaEuZE+I3yGJwy2p5lOPeTTX2bWbZmzDebwW8nC9YNQS/ X-Received: by 10.28.231.9 with SMTP id e9mr3354302wmh.12.1517406462771; Wed, 31 Jan 2018 05:47:42 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1517406462; cv=none; d=google.com; s=arc-20160816; b=MO6l3lgXtRUrkBfFCtDAYKsUog4E6bUaIon32+nXp7qqu3BzBvdJH5jFUEgRgw0f7/ ghAxVzlvcby6fJ8ddxfn+LCBnsgHfWjrlxHd6Af1gpw6XxqEwp3P6/fyER/4kHJzmPbT 1nRFZdmPJ1NsRUqZR6uuuZqBlti7UzaW2PWR3VBYI4j3zjzKVuFTpywaMMtY1C7rm9sB alcdJns04ofXFQ+enSpPFRWqvC8+dMNL+DItt8KZZ2o5MUpHabx5P+7heRuEUQT2EWRV U8KtfmOYWQMstbulK16te6+D4Zyju1M/+ijVV2i1zCLTfIHPFv1RwtlJwMCGyCL5uYOG R0bA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:arc-authentication-results; bh=RgXBoy0b4pi8O0HnKGvznvm8hm8ep9StOHH6NcaZ7Qs=; b=yrE/HUyG/igj3lhOtv9jNzkVPAxPr3nVOXRBPuDssuOZo86U6iN42LEfOJt4K69ylo RPbJOyXh5XwubUYeDLV5kNwN/CBdZdU0I+CzA6p9MXeaBVOkSbOStyJNxCoNGKaVj3Y0 h4G8dhS/uB8EEAHKr1bMwHiFs9i2pBwODpaZbhQAU1ZyUPqS8KLHEjn/mBvOarLYOz0F XK6TD6kLzbcN7FaTiZDg+M68gVV2/zgxEchIWw7Q18kGSiQFGALob5FmmrxHD+bqJEx7 0NVTOsw0GMoc2EPcU9sbSCY0kJPw9cgdQJ2YeZ3c79GKUB7FA1Byy2dgA/W3tDy+uweS uk4w== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=henning.schild@siemens.com Return-Path: Received: from david.siemens.de (david.siemens.de. [192.35.17.14]) by gmr-mx.google.com with ESMTPS id s81si1323997wmd.2.2018.01.31.05.47.42 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 31 Jan 2018 05:47:42 -0800 (PST) Received-SPF: pass (google.com: domain of henning.schild@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 henning.schild@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=henning.schild@siemens.com Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14]) by david.siemens.de (8.15.2/8.15.2) with ESMTPS id w0VDlgi1025275 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 31 Jan 2018 14:47:42 +0100 Received: from mmd1pvb1c.ad001.siemens.net (md1pvb1c.ad001.siemens.net [139.25.68.40] (may be forged)) by mail3.siemens.de (8.15.2/8.15.2) with ESMTP id w0VDlgEk026756; Wed, 31 Jan 2018 14:47:42 +0100 Date: Wed, 31 Jan 2018 14:47:41 +0100 From: Henning Schild To: Baurzhan Ismagulov Cc: Subject: Re: [PATCH 0/9] first wic integration Message-ID: <20180131144741.7a8aeb04@mmd1pvb1c.ad001.siemens.net> In-Reply-To: <20180131133511.GE6508@yssyq.radix50.net> References: <20180131111253.49011346@mmd1pvb1c.ad001.siemens.net> <20180131112421.GA6508@yssyq.radix50.net> <675eeef9-1e24-4784-b894-4ce665da26fb@siemens.com> <20180131120245.GC6508@yssyq.radix50.net> <1a55fba5-e089-5bbe-4f14-e1931dea38dd@siemens.com> <20180131133511.GE6508@yssyq.radix50.net> X-Mailer: Claws Mail 3.15.0-dirty (GTK+ 2.24.31; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-TUID: /AcUaV/l9Db1 Am Wed, 31 Jan 2018 14:35:11 +0100 schrieb Baurzhan Ismagulov : > On Wed, Jan 31, 2018 at 01:15:28PM +0100, Jan Kiszka wrote: > > > bf873d3 wic: Use sudo instead of pseudo > > > > This hacks in wic, and that has to go in order to keep > > maintainability. We need to solve that differently, for sure. > > That is a trade-off between breaking the user experience (which is > strategic) and temporary workaround that will go away anyway. > > Till we get our changes accepted upstream, we have to workaround them > locally. This series should remove the biggest hack, sysroot removal. > Other changes are one-liners that are easy to port to a new bitbake > version. > > That said, updating wic happens from time to time, but wic is used > every day. That is why I'd like to keep the workaround in master till > we see what happens with the upstream merge. > > I'd welcome any suggestions other than "sudo wic". sudo bash -c wic? Henning > > > > Regarding the PRoot PoC... > > > > I'm happy to discuss the effort you see in resolving that last > > issue and will re-prioritize. > > Ok, will come up with that after the current libhello work hits > master. > > > > >>> b1511ec wic: Work around mcopy error > > > > This issue is not understood yet, thus the commit not ready for > > upstream. Furthermore, the log does not describe how to reproduce > > the issue. So - how to clarify if we still need it? > > I'll check how to reproduce that. > > > > >>> 17f9196 wic: Introduce the `WicExecError` exception class > > > > Can you explain why fsck should return an error at all on a freshly > > built file system image? This seems to paper over some issue to > > me. > > At the time, it sounded like a bug somewhere in mkfs or fsck, but we > haven't digged deeper yet. So yes, that's a workaround. > > > > > Do you mean we should initiate upstreaming that to OE? If yes, I > > > agree with you. The only question is point of time. My idea was > > > to wait till Henning completes the lifecycle with his OE > > > contribution and learn from his experience. If you think we > > > should do that now, please let me know. > > > > Local hacks can save some time for a while but will shoot back with > > more effort eventually. > > It wasn't about saving time, it was about providing working code > first, upstreaming second. > > > > I think we are already at that point, so let's move forward. > > Ok, let me analyze the issues and come with a proposal. > > > With kind regards, > Baurzhan. >