From: Claudius Heine <claudius.heine.ext@siemens.com>
To: "Maxim Yu. Osipov" <mosipov@ilbers.de>, isar-users@googlegroups.com
Subject: Re: [PATCH v2 2/3] Revert "image.bbclass: make KERNEL_IMAGE & INITRD_IMAGE variable fixed"
Date: Mon, 13 May 2019 09:31:47 +0200 [thread overview]
Message-ID: <13a1e1d6-4abb-cccb-95f2-f745be200c11@siemens.com> (raw)
In-Reply-To: <20190512193100.23709-3-mosipov@ilbers.de>
Hi Maxim,
On 12/05/2019 21.30, Maxim Yu. Osipov wrote:
> This reverts commit b92589c574596ac98f97cf14369cbf62872e6481.
>
> vmlinuz and initrd are getting overwritten for the same machine
> by other distros under deploy/images/${MACHINE}
NACK. I don't see a patch that addresses the issue described in the
commit message of that reverted patch in this patchset in a different
way, so this is a regression.
regards,
Claudius
>
> Closes: #56
> Signed-off-by: Maxim Yu. Osipov <mosipov@ilbers.de>
> ---
> meta/classes/image.bbclass | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
> index fb35a4c..8e6f2c9 100644
> --- a/meta/classes/image.bbclass
> +++ b/meta/classes/image.bbclass
> @@ -13,8 +13,8 @@ IMAGE_INSTALL += "${@ ("linux-image-" + d.getVar("KERNEL_NAME", True)) if d.getV
> IMAGE_FULLNAME = "${PF}"
>
> # These variables are used by wic and start_vm
> -KERNEL_IMAGE ?= "vmlinuz"
> -INITRD_IMAGE ?= "initrd.img"
> +KERNEL_IMAGE ?= "${@get_image_name(d, 'vmlinuz')[1]}"
> +INITRD_IMAGE ?= "${@get_image_name(d, 'initrd.img')[1]}"
>
> # Useful variables for imager implementations:
> PP = "/home/builder/${PN}"
> @@ -149,10 +149,12 @@ addtask rootfs_install before do_build after do_unpack
>
> do_copy_boot_files[dirs] = "${DEPLOY_DIR_IMAGE}"
> do_copy_boot_files() {
> + KERNEL_IMAGE=${@get_image_name(d, 'vmlinuz')[1]}
> if [ -n "${KERNEL_IMAGE}" ]; then
> cp -f ${IMAGE_ROOTFS}/boot/${@get_image_name(d, 'vmlinuz')[0]} ${DEPLOY_DIR_IMAGE}/${KERNEL_IMAGE}
> fi
>
> + INITRD_IMAGE=${@get_image_name(d, 'initrd.img')[1]}
> if [ -n "${INITRD_IMAGE}" ]; then
> sudo cp -f ${IMAGE_ROOTFS}/boot/${@get_image_name(d, 'initrd.img')[0]} ${DEPLOY_DIR_IMAGE}/${INITRD_IMAGE}
> fi
>
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de
next prev parent reply other threads:[~2019-05-13 7:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-12 19:30 [PATCH v2 0/3] vmlinuz/initrd for the same MACHINE are overwritten Maxim Yu. Osipov
2019-05-12 19:30 ` [PATCH v2 1/3] meta/classes/image: Call transform_template after rootfs_install Maxim Yu. Osipov
2019-05-12 19:30 ` [PATCH v2 2/3] Revert "image.bbclass: make KERNEL_IMAGE & INITRD_IMAGE variable fixed" Maxim Yu. Osipov
2019-05-13 7:31 ` Claudius Heine [this message]
2019-05-13 7:39 ` Maxim Yu. Osipov
2019-05-13 7:43 ` Maxim Yu. Osipov
2019-05-13 8:11 ` Claudius Heine
2019-05-13 9:01 ` Maxim Yu. Osipov
2019-05-13 11:05 ` Claudius Heine
2019-05-13 11:16 ` Maxim Yu. Osipov
2019-05-14 14:41 ` Maxim Yu. Osipov
2019-05-12 19:31 ` [PATCH v2 3/3] ci: Include qemuarm-buster into fast build/vm_smoke_test Maxim Yu. Osipov
2019-05-14 17:24 ` [PATCH v2 0/3] vmlinuz/initrd for the same MACHINE are overwritten 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=13a1e1d6-4abb-cccb-95f2-f745be200c11@siemens.com \
--to=claudius.heine.ext@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=mosipov@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