From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6667603680306397184 X-Received: by 2002:a7b:c38e:: with SMTP id s14mr95940wmj.3.1552563084355; Thu, 14 Mar 2019 04:31:24 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a1c:4083:: with SMTP id n125ls646946wma.4.canary-gmail; Thu, 14 Mar 2019 04:31:23 -0700 (PDT) X-Google-Smtp-Source: APXvYqw3IXoN8iRnJhKhUk+XK37yNm7zR+yAjB8N4RFPtw10fg4kjA3G1aV/3NsC8bWT2f5SytHY X-Received: by 2002:a1c:9689:: with SMTP id y131mr195642wmd.6.1552563083832; Thu, 14 Mar 2019 04:31:23 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1552563083; cv=none; d=google.com; s=arc-20160816; b=plVCmJPrmJBnldgPYkt4noo42gqXdwRn5UnLMDmRxpsVpVcZjwlc3CNXejJDn7nd+2 1KoKiZa7OUa0JwMCUKIUBc6GqF0XBdprodxbXvTJyR/OACbLeTvLTRjbp49EdJwRhXk5 qzd+8OjURsEcYlq3zQi9VJ84x/kiEcMOTTOlF6jiu9574zljiE7EhnTdk9IR3phG5Nro l8mf5co2rc8okBFOc13DD4UR/dJf0RpbSMEZGdP1/gQXxf8clR5dKKn0MhIAtk60KAgQ 3COQBs1FakKJr1YckgSxGsv/n7FbOHPQaBkrVSs63rU+PS66U7k7Eiy6NS4RqbraJb8Z utbA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=user-agent:in-reply-to:content-disposition:mime-version:references :mail-followup-to:message-id:subject:to:from:date; bh=HqUTqxphudODZXTv0GJdIlD/+UTDepy8YWjQ6e3u+4I=; b=FNfgL0wro4r/0Wn2dycrxlpECkeIsnWX9zD/hen88BRyMgBdyF7NANwbvCSgyh/DTk t56+uQL2CvRLl3c59i1w06RGnneldonQBreLW1Rq7HEJahnVbVsqd9VxsZEHqOJZ3xVU mCn+/ULquF1P9JacCTOMDrh6KXuxeYyMQVA2vG+SkNvrl70b1r4xzSNjxeJiJU4NODUv UNaIRKT1Jw+VxoZvcrEp+BTE07I200CSVxSeWpjS5W3QO6GS8zfn6GLbgRib0MGnDPQc NBp8+/1DCiokxZlYZRlviTRmyxnw1DB/y34AtE56D94vAAn3HpEd6t3idL4I99YhN81E uPJQ== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=neutral (google.com: 85.214.156.166 is neither permitted nor denied by best guess record for domain of ibr@radix50.net) smtp.mailfrom=ibr@radix50.net Return-Path: Received: from shymkent.ilbers.de (shymkent.ilbers.de. [85.214.156.166]) by gmr-mx.google.com with ESMTPS id r15si56738wmc.4.2019.03.14.04.31.23 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 14 Mar 2019 04:31:23 -0700 (PDT) Received-SPF: neutral (google.com: 85.214.156.166 is neither permitted nor denied by best guess record for domain of ibr@radix50.net) client-ip=85.214.156.166; Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: 85.214.156.166 is neither permitted nor denied by best guess record for domain of ibr@radix50.net) smtp.mailfrom=ibr@radix50.net Received: from yssyq.m.ilbers.de (host-80-81-17-52.static.customer.m-online.net [80.81.17.52]) (authenticated bits=0) by shymkent.ilbers.de (8.15.2/8.15.2/Debian-8) with ESMTPSA id x2EBVLHV025909 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Thu, 14 Mar 2019 12:31:22 +0100 Date: Thu, 14 Mar 2019 12:31:21 +0100 From: Baurzhan Ismagulov To: isar-users@googlegroups.com Subject: Re: [PATCH 2/2] doc/user_manual: Update after images per machine separation Message-ID: <20190314113121.GD16465@yssyq.m.ilbers.de> Mail-Followup-To: isar-users@googlegroups.com References: <20190312202713.18792-1-mosipov@ilbers.de> <20190312202713.18792-2-mosipov@ilbers.de> <9d284bca-29a0-92d6-5711-0ee1689e0a3c@siemens.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9d284bca-29a0-92d6-5711-0ee1689e0a3c@siemens.com> User-Agent: Mutt/1.10.1 (2018-07-13) X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on shymkent.ilbers.de X-TUID: teUfHByrO83Y On Thu, Mar 14, 2019 at 08:14:34AM +0100, Jan Kiszka wrote: > > diff --git a/RECIPE-API-CHANGELOG.md b/RECIPE-API-CHANGELOG.md ... > > -`IMAGE-DISTRO-MACHINE.TYPE`. This scheme was already used for ext4/wic images > > +`IMAGE-MACHINE-DISTRO-MACHINE.TYPE`. This scheme was already used for ext4/wic images > > Reading this again: Where does the first MACHINE in this file name come > from? Maybe it can be avoided, now that we officially name image recipes > after the machine. I also don't like changing the UX in this version of the patch. Since we are going to update tmp/work w.r.t. ${MACHINE} anyway, I suggest that we merge and document the original workaround [1] that unbreaks the stuff and quickly move forward with the critical patches and the right fix. 1. https://groups.google.com/d/msg/isar-users/9CJ1QmMbKYU/Sy8A6q6FBgAJ With kind regards, Baurzhan.