From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6627135346509348864 X-Received: by 2002:a2e:505a:: with SMTP id v26-v6mr2324191ljd.5.1543312526211; Tue, 27 Nov 2018 01:55:26 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a2e:8910:: with SMTP id d16-v6ls2855851lji.14.gmail; Tue, 27 Nov 2018 01:55:25 -0800 (PST) X-Google-Smtp-Source: AFSGD/XOELDzgJeChCSpXCF1eKC8dCY20x4rJuuh4rOdhtIe0EeddIm80EflZ8ETNUVMcyjOS+cD X-Received: by 2002:a2e:9902:: with SMTP id v2-v6mr2318097lji.6.1543312525777; Tue, 27 Nov 2018 01:55:25 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1543312525; cv=none; d=google.com; s=arc-20160816; b=muSMyx79MWw/fJtLqG0Uxm0qrVegjotbOKebsTheDZhV7ZXRAGTk33GGnI32XX96lD p5ItKcaDW+47wvtAqtPeuyZlz3lssnILBFAix4sxmW8xffGLsvLxnAMtPqGcQWQnV3kw E35GwvgPAUr0hu7svqhcRcVeGwlb6qlftE2vx38kshRZlAzaKU+jQ1idDfu5XS6s3ZeA 19hMV2Wk85s0HcQsPArshXu5iiiPVI75frOMqXiQnQNjLHUI/s5GYVq/Tf32hys+JhvK 8BIRUK7diEJ8V6TjMQ8aShUJSf6OcLebBhgqzabO8kkhhqmTlmknpPME+kJJkuY6imCR bNuA== 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; bh=80bZrwhEwTT01ohhX5u4WD37mao3wXgQqCfh0d7T/P4=; b=XvqwO54al1UeRqSAHLwGhi4n9u5XOeo/fM3AfgYglb8fnxX+PBwZZb2FcyIjZQ7YP+ gKUBoZJy5PyvE5N4WHyku3mWwmM/hde9dbgC0e+/RoPvOv2OOmtxtoRUJfWZmFEmBdCx 1yJViscMMV1sLKV+vsBXVFvNpjD56GxSJPLYqp3pXeFfD/0NCuDGqFbzwL3ydUesTBPQ fYbh/0Nfc7w02RD9QBPRtCl6Sa+6l3A/YdR2Etbbfje+bkruKmM+tqDOD3nSJnaGn/eE iaIOaQuzLvjzHpbD+MZedziB8snaQkB5vBnjqr/oX3Wp0pJaiL2WJyTTlMeO8090LrWd aWrg== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.28 as permitted sender) smtp.mailfrom=henning.schild@siemens.com Return-Path: Received: from goliath.siemens.de (goliath.siemens.de. [192.35.17.28]) by gmr-mx.google.com with ESMTPS id y27si62171lfb.0.2018.11.27.01.55.25 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 27 Nov 2018 01:55:25 -0800 (PST) Received-SPF: pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.28 as permitted sender) client-ip=192.35.17.28; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.28 as permitted sender) smtp.mailfrom=henning.schild@siemens.com Received: from mail1.sbs.de (mail1.sbs.de [192.129.41.35]) by goliath.siemens.de (8.15.2/8.15.2) with ESMTPS id wAR9tOab010237 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Tue, 27 Nov 2018 10:55:24 +0100 Received: from md1za8fc.ad001.siemens.net ([139.25.68.176]) by mail1.sbs.de (8.15.2/8.15.2) with ESMTP id wAR9tOob020915; Tue, 27 Nov 2018 10:55:24 +0100 Date: Tue, 27 Nov 2018 10:55:22 +0100 From: Henning Schild To: Jan Kiszka Cc: isar-users Subject: Re: [PATCH v2 0/3] u-boot regression fix, cleanup restoration Message-ID: <20181127105522.0e850592@md1za8fc.ad001.siemens.net> In-Reply-To: References: <20181126104745.0f2c89be@md1za8fc.ad001.siemens.net> <18e2a91e-7117-2be1-973b-5002a0f2ee75@siemens.com> <20181126111639.2a8ed6eb@md1za8fc.ad001.siemens.net> X-Mailer: Claws Mail 3.15.0-dirty (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-TUID: 0Frv19tQve8W Am Mon, 26 Nov 2018 12:08:47 +0100 schrieb Jan Kiszka : > On 26.11.18 11:16, Henning Schild wrote: > > Am Mon, 26 Nov 2018 10:49:53 +0100 > > schrieb Jan Kiszka : > > > >> On 26.11.18 10:47, Henning Schild wrote: > >>> Did you try putting MACHINE into PV and pinning on that? It is > >>> always the same package and multiple versions are .... multiple > >>> versions. > >> > >> That won't fly. We want recipes to generate results that be be > >> exchanged (u-boot-myboard either from u-boot mainline or from some > >> vendor recipe). > > > > Could you explain the problem in more detail? I do not understand > > the issue yet. I know the pattern comes from multiconfig conflicts > > you have found in jailhouse-images ... but messing with PN at > > runtime just sounds like a very bad idea. I am not surprised that > > uncovered a bitbake bug .... > > This recipe is not messing with PN, neither before not after your > patch. It is just defining its output package names independently of > the PN. E.g., we have u-boot_xxx.bb as recipe to build packages from > upstream U-Boot sources. Those shall carry the same, stable names as > package built by some u-boot-downstream_xxx.bb which use a downstream > source repo. That allows to switch providers by just defining > PREFERRED_PROVIDER_u-boot-. Your patch would enforce to > change also all recipes that pull that target. That's not desirable > (and broke jailhouse-images as a pioneer user). Still one question left, because you reverted the PN in the control file. If you have u-boot-foo and u-boot-bar we are sure they can always share u-boot-dev again? I think we would need u-boot-(foo|bar)-dev and friends as well. Henning > Jan >