From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Subject: Re: [PATCH 2/2] Revert "meta/classes/image: Call transform_template after rootfs_install"
Date: Mon, 20 May 2019 21:47:10 +0200 [thread overview]
Message-ID: <20190520194710.GI21981@yssyq.m.ilbers.de> (raw)
In-Reply-To: <729803d9-2ce2-4de4-c121-a7d1d90842a7@siemens.com>
On Mon, May 20, 2019 at 09:19:41AM +0200, Claudius Heine wrote:
> Because this change just painted over the underlying issue with the
> non-deterministic and volatile value of the KERNEL_IMAGE and INITRD_IMAGE
> variables. So I would not consider that a permanent fix but a quick
> band-aid.
The function returns different values depending on whether the respective task
has finished. So, the implicit precondition is that the caller must depend on
the kernel deployment task. Given the precondition, the behavior is
deterministic and there could be other ways to fix them without sacrificing
user experience.
For my understanding, what was your user-level use case when you experienced
the get_image_name() issue?
To be clear, Maxim's patch only addresses CI and not this issue.
With kind regards,
Baurzhan.
next prev parent reply other threads:[~2019-05-20 19:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 12:50 [PATCH 0/2] Fix of #56 claudius.heine.ext
2019-05-16 12:50 ` [PATCH 1/2] image.bbclass: make KERNEL_IMAGE & INITRD_IMAGE variable fixed claudius.heine.ext
2019-05-16 13:32 ` Claudius Heine
2019-05-16 12:50 ` [PATCH 2/2] Revert "meta/classes/image: Call transform_template after rootfs_install" claudius.heine.ext
2019-05-17 10:58 ` Maxim Yu. Osipov
2019-05-20 7:19 ` Claudius Heine
2019-05-20 19:47 ` Baurzhan Ismagulov [this message]
2019-05-21 8:06 ` Claudius Heine
2019-05-18 11:35 ` [PATCH 0/2] Fix of #56 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=20190520194710.GI21981@yssyq.m.ilbers.de \
--to=ibr@radix50.net \
--cc=isar-users@googlegroups.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