public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH v2 0/3] u-boot regression fix, cleanup restoration
Date: Mon, 26 Nov 2018 11:16:39 +0100	[thread overview]
Message-ID: <20181126111639.2a8ed6eb@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <18e2a91e-7117-2be1-973b-5002a0f2ee75@siemens.com>

Am Mon, 26 Nov 2018 10:49:53 +0100
schrieb Jan Kiszka <jan.kiszka@siemens.com>:

> 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 ....

Henning

> Jan
> 
> > 
> > Henning
> > 
> > Am Fri, 23 Nov 2018 20:09:44 +0100
> > schrieb Jan Kiszka <jan.kiszka@siemens.com>:
> >   
> >> See patches for details.
> >>
> >> Urgent for downstream layers with multiple custom u-boot recipes.
> >>
> >> Jan Kiszka (3):
> >>    Revert "u-boot-custom: Use bitbake variables instead of
> >> hardcoded values"
> >>    meta-isar: u-boot: Encode version in URL via PV
> >>    u-boot-custom: Add -dev package to PROVIDES
> >>
> >>   meta-isar/recipes-bsp/u-boot/u-boot_2018.09.bb | 2 +-
> >>   meta/recipes-bsp/u-boot/files/debian/control   | 6 +++---
> >>   meta/recipes-bsp/u-boot/u-boot-custom.inc      | 2 +-
> >>   3 files changed, 5 insertions(+), 5 deletions(-)
> >>  
> >   
> 


  reply	other threads:[~2018-11-26 10:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-23 19:09 Jan Kiszka
2018-11-23 19:09 ` [PATCH v2 1/3] Revert "u-boot-custom: Use bitbake variables instead of hardcoded values" Jan Kiszka
2018-11-23 19:09 ` [PATCH v2 2/3] meta-isar: u-boot: Encode version in URL via PV Jan Kiszka
2018-11-23 19:09 ` [PATCH v2 3/3] u-boot-custom: Add -dev package to PROVIDES Jan Kiszka
2018-11-26  9:47 ` [PATCH v2 0/3] u-boot regression fix, cleanup restoration Henning Schild
2018-11-26  9:49   ` Jan Kiszka
2018-11-26 10:16     ` Henning Schild [this message]
2018-11-26 11:08       ` Jan Kiszka
2018-11-26 16:51         ` Henning Schild
2018-11-27  9:55         ` Henning Schild
2018-11-26 13:15 ` Maxim Yu. Osipov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20181126111639.2a8ed6eb@md1za8fc.ad001.siemens.net \
    --to=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox