public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: "Bezdeka, Florian (T CED SES-DE)" <florian.bezdeka@siemens.com>
Cc: "amikan@ilbers.de" <amikan@ilbers.de>,
	"ubely@ilbers.de" <ubely@ilbers.de>,
	"isar-users@googlegroups.com" <isar-users@googlegroups.com>,
	"Kiszka, Jan (T CED)" <jan.kiszka@siemens.com>
Subject: Re: [PATCH 0/1] Update bitbake to version 1.50.4
Date: Tue, 19 Apr 2022 14:51:45 +0200	[thread overview]
Message-ID: <20220419145145.3af8bbeb@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <1a0bca986c72be7c81ad53f30169eab7f3283568.camel@siemens.com>

Am Tue, 19 Apr 2022 14:41:14 +0200
schrieb "Bezdeka, Florian (T CED SES-DE)" <florian.bezdeka@siemens.com>:

> Hi all,
> 
> On Fri, 2022-03-25 at 09:31 +0300, Anton Mikanovich wrote:
> > 01.02.2022 14:42, Uladzimir Bely wrote:  
> > > Bitbake in Isar didn't get updates for almost 1.5 years. At the
> > > same time the version we use have at least one annoying bug, when
> > > messages in log files got duplicated if "--verbose" option is
> > > used and error happens.
> > > 
> > > This was fixed in upstream revision 69c622b744d9, few commits
> > > before the tag 1.50.4.
> > > 
> > > Also, there is 1.52 branch exists (latest tag 1.52.1), but it
> > > seems to be incompatible with Isar.  
> > 
> > Update to bitbake 1.50.4 applied to next, thanks.
> >   
> 
> this seems to trigger a build failure when trying to use debian
> bookworm as distro, there is no debian-bookworm-backports.list file.

I think you might be dealing with an issue in your layers. A layer you
might be basing on recently introduced backports for bullseye and does
not yet test for bookworm. Isar itself does not do anything about
backports and does not carry such list files.

regards,
Henning

> ERROR: ExpansionError during parsing
> /work/isar/meta/recipes-core/isar-bootstrap/isar-bootstrap-target.bb################################################
> | ETA: 0:00:00 Traceback (most recent call last): File
> "/work/isar/meta/recipes-core/isar-bootstrap/isar-bootstrap.inc",
> line 181, in
> get_distro_needs_https_support(d=<bb.data_smart.DataSmart object at
> 0x7fc5bf873908>): def get_distro_needs_https_support(d):
> > if get_distro_have_https_source(d):  
> return "https-support"
> File
> "/work/isar/meta/recipes-core/isar-bootstrap/isar-bootstrap.inc",
> line 172, in get_distro_have_https_source(d=<bb.data_smart.DataSmart
> object at 0x7fc5bf873908>): def get_distro_have_https_source(d):
> > return any(source[2].startswith("https://") for source in
> > generate_distro_sources(d))  
> 
> File
> "/work/isar/meta/recipes-core/isar-bootstrap/isar-bootstrap.inc",
> line 172, in <genexpr>(.0=<generator object generate_distro_sources
> at 0x7fc5bed36318>): def get_distro_have_https_source(d):
> > return any(source[2].startswith("https://") for source in
> > generate_distro_sources(d))  
> 
> File
> "/work/isar/meta/recipes-core/isar-bootstrap/isar-bootstrap.inc",
> line 157, in generate_distro_sources(d=<bb.data_smart.DataSmart
> object at 0x7fc5bf873908>): for entry in apt_sources_list:
> > entry_real = bb.parse.resolve_file(entry, d)  
> with open(entry_real, "r") as in_fd:
> File "/work/isar/bitbake/lib/bb/parse/__init__.py", line 125, in
> resolve_file(fn='conf/distro/debian-bookworm-backports.list',
> d=<bb.data_smart.DataSmart object at 0x7fc5bf873908>): if not newfn:
> > raise IOError(errno.ENOENT, "file %s not found in %s" % (fn,
> > bbpath))  
> fn = newfn
> bb.data_smart.ExpansionError: Failure expanding variable OVERRIDES,
> expression was
> amd64::qemuamd64:debian-bookworm:forcevariable:${@get_distro_needs_https_support(d)}
> which triggered exception FileNotFoundError: [Errno 2] file
> conf/distro/debian-bookworm-backports.list 
> 
> 
> My understanding for now is, that bb.parse.resolve_file() might throw
> an IOError when the file can not be found. That might be new, but I
> failed to get something from the bb changelog.
> 
> Seems we have to revisit all usages of bb.parse.resolve_file(). All of
> them are actually in the same file...
> 
> Any thoughts?
> 
> Regards,
> Florian


  reply	other threads:[~2022-04-19 12:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-01 11:42 Uladzimir Bely
2022-02-01 11:42 ` [PATCH 1/1] bitbake: Update to 1.50.4 release Uladzimir Bely
2022-02-02  6:25 ` [PATCH 0/1] Update bitbake to version 1.50.4 Schmidt, Adriaan
2022-02-02  6:52   ` Jan Kiszka
2022-03-28  8:44     ` Henning Schild
2022-03-25  6:31 ` Anton Mikanovich
2022-04-19 12:41   ` Bezdeka, Florian
2022-04-19 12:51     ` Henning Schild [this message]
2022-04-19 14:02       ` Bezdeka, Florian
2022-04-19 14:26         ` Baurzhan Ismagulov
2022-04-19 14:35         ` Henning Schild

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=20220419145145.3af8bbeb@md1za8fc.ad001.siemens.net \
    --to=henning.schild@siemens.com \
    --cc=amikan@ilbers.de \
    --cc=florian.bezdeka@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.com \
    --cc=ubely@ilbers.de \
    /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